usage of ramdisk in ispconfig

Hello forum.

Some feedback on this would be nice:
I am playing with the thought of using tmpfs for web folder and using a mysql replication setup where on mysql instance is fully running om tmpfs filesystem once replication is complete, replication is reversed. I know this setup has drawback, but i believe also benefits. I will be doing this on a test environment only to experience all the benefits and drawbacks

My actual question:
Why is it that no matter what i try i am not able to rename the web folder of a site. It keeps giving me "Operation not permitted"
I would like to mount my tmfs disk on web, while having the possibility to keep the former disk web up 2 date
What is the best way to get this done?

Thank you in advance for your answers

 

found my answer:
chattr -i /var/www/clients/client0/web1
mv /var/www/clients/client0/web1/web /var/www/clients/client0/web1/web-old
chattr +i /var/www/clients/client0/web1

Make sure you use full paths

 

Have you done measurements to see if the setup is useful?
If there is extra RAM, would that setup be better than just let system cache disk stuff to RAM?

 

That whole idea does not sound like a good one for production use. Running mysql on tmpfs is a bad idea for production. The kernel page cache already keeps hot database pages in RAM and InnoDB itself aggressively caches data in its buffer pool. Adding a third very fragile layer with tmpfs is a really bad approach for mysql performance tuning.

Static files are mostly heavily cached by the kernel anyway and linux already uses free RAM aggressively for filesystem caching, so your actual performance gain may be much smaller than you expect here.

It could still be an interesting experiment in a test environment, but I would not consider it a sensible production design concept.