John Reiser a écrit : >> When I start MySQL, InnoDB engine allocate his buffer pool without any >> issue. It's not the same when I launch it with Valgrind :( >> What can I do to resolve this issue ? >> > > Post a copy of the error message(s). It is necessary first to identify > _which_ error(s). Include the machine architecture (i686, x86_64, etc.) > and the operating system. In other words, give a decent bug report. > > Speculating that you may be running Linux on i686, then _sometimes_ > it is possible to obtain an extra 0.8GB of address space by running > the i686 version of the application and valgrind on a x86_64 machine. > > I understand. Here are the information you asked for :
Linux host01 2.6.24.2 #1 SMP Wed Feb 20 15:40:12 CET 2008 i686 GNU/Linux the error message is the following : 100407 10:11:45 InnoDB: Error: cannot allocate 1610629120 bytes of InnoDB: memory with malloc! Total allocated memory InnoDB: by InnoDB 23965696 bytes. Operating system errno: 0 InnoDB: Check if you should increase the swap file or InnoDB: ulimits of your operating system. InnoDB: On FreeBSD check you have compiled the OS with InnoDB: a big enough maximum process size. InnoDB: Note that in most 32-bit computers the process Outch ! you think the process is trying to allocate 1.6GB+~0.8GB+(more memory for mysql) and that's over the max memory per process on x86 ? Regards -- Cyril SCETBON ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
