Messages in this thread | | | Date | Tue, 13 Jul 2004 19:40:20 -0700 | From | William Lee Irwin III <> | Subject | Re: VM Problems in 2.6.7 (Too active OOM Killer) |
| |
On Tue, Jul 13, 2004 at 07:23:44PM -0700, Peter Zaitsev wrote: > To be honest I was truly surprised seeing OOM killer killing MySQL > without any good reason during highly IO intensive test: > Out of Memory: Killed process 19301 (mysqld). > Out of Memory: Killed process 19302 (mysqld). > Out of Memory: Killed process 19303 (mysqld). > Out of Memory: Killed process 19304 (mysqld). > Out of Memory: Killed process 19305 (mysqld). > Out of Memory: Killed process 19306 (mysqld). > Out of Memory: Killed process 19309 (mysqld). > Out of Memory: Killed process 19310 (mysqld). > Out of Memory: Killed process 19311 (mysqld). > Out of Memory: Killed process 19312 (mysqld). > Out of Memory: Killed process 19737 (mysqld). > Out of Memory: Killed process 19739 (mysqld). > Out of Memory: Killed process 19821 (mysqld). > This box has 4G memory and running without swap (what I would need it > for If I can only use up to 3GB address space in the application anyway)
Is this a regression from earlier 2.6 versions? Do you have an isolated testcase (obviously I should be able to install mysql easily) I can use to trigger this?
-- wli - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |