On Sat, 31 Jan 2009, Jacob Coby wrote: > Yes, neat. And totally worthless on a Linux server. Linux already > uses excess ram to cache commonly accessed files. You're just taking > ram away from processes that could actually use it. A good portion of > it will be kept empty since you have to allocate more space than you > actually use. I imagine the same applies to *BSD and probably Windows > as well. > > Ramdisks were a great idea around MS DOS 5 when you wanted to get rid > of diskette seek times. They're worthless now. Use a php opcode > cache instead. You'll get a 10000x better ROI on that 64mb than > adding a ramdisk.
Nowhere did I mention that a ramdisk is the only solution you might consider. Absolutely you should look at opcode caching and things like memcache. BUT, I would like to point out that the cache folder gets very deep, every file access results in a disk operation, every directory leading to a cached file results in a stat() system call to check permission bits and ownership. Frankly, your network connections are a bigger bottleneck. -- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
