|
|||||||||||
|
Re: MySQL and writing RAMFS for tmp question
From: Vladimir Shebordaev <vladimir.shebordaev(at)gmail.com>
Date: Wed Jul 25 2007 - 19:15:34 EDT
Would you please elaborate in what a way did you mount ramfs on /tmp? Probably, your mysqld has literally got low credentials on it. Either your ramdisk has already been choked. Also ramfs is not so widely used for user space applications and primarily intended for kernel boot-up purposes. It is almost obsoleted by now. I'd suggest to try tmpfs instead. I get any problem with neither mysql-5.0.27 from Fedora Core 6 nor stock mysql-5.0.48 starting up having tmpdir on it if I mount -t tmpfs -orw,size=700M,mode=1777 /tmp /tmp If you are inclined to also try it, please notice that "size=<instance_size>" mount option. The default is to use not more than a half of your physical memory, i.e. not including the swap. It can appear too small for real life mysqld instance. But tmpfs can swap unlikely to ramfs. So, you can use some swap space for it. But not too much though. It can eat up all your swap, so that even OOM killer will not be able to reclaim the memory and the system will deadlock. As for me I've set size=700M with my 2,5G RAM and run into lockups if I let it expand above this amount. In the hope it helps.
Regards,
Mariella Petrini пиÑеÑ:
-- MySQL Internals Mailing List For list archives: http://lists.mysql.com/internals To unsubscribe: http://lists.mysql.com/internals?unsub=lists@pantek.comReceived on Wed Jul 25 19:18:07 2007 This archive was generated by hypermail 2.1.8 : Thu Aug 09 2007 - 19:06:20 EDT |
||||||||||
|
|||||||||||