On 05/11/2011 16:04, Сергей wrote: > Hello everybody, > > I think some people in here are familiar with the idea of creating > temporary filesystems in RAM, that gives a huge performance boost at > some workloads (e.g. MySQL). However, those setups never got widely > used because of one problem: the whole thing crashes if you run out of > space in the ramdisk. One guy (Yves Trudeau) said "Let's use a union > filesystem and the problem will be solved! It will write to ramdisk > while it has free space, and use the HDD when the ramdisk is full" > (www.bigdbahead.com/?p=137). However, that guy never published any > code. >
Apologies for the very late reply, but wouldn't you get the same or better results from simply disabling fsync in mysql and using a normal disk, ie basically implementing a large writeback cache? Practical ways exist to do this, the most robust being to add a battery backed controller with writeback caching, also I think mysql has some tunables to allow unwritten writes to be considered committed? Perhaps your point is that it's no issue if the whole thing gets blown away when the machine reboots? If so then yes I see your point... Cheers Ed W ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d
