On 02/18/2013 06:14 PM, Stas Malyshev wrote: > Hi! > >> Yeah, but NFS, especially without the realpath cache, which you lose if >> you turn on open_basedir, is deathly slow because of all the stats. >> >> Typically PHP scripts are not actually "writable files" and the way to >> keep them in synch across multiple machines is to use a deploy >> mechanism/rsynch to deploy them. You may very well have some writable > > rsync may be way too slow if you need the change appear more or less > "immediately" on all servers. Unless you run rsync each second if which > case you're probably better off with NFS :) > >> files that need to be shared at the app-level, but then we wouldn't be >> talking about PHP stat calls and the realpath cache. And most people > > You would still if the data is stored as php file. Which last time I > tested - given APC or something like - was the fastest way to get a > bunch of data into PHP (it was faster than loading and unserializing, > even with APC/memcache). > >> have moved to something like memcache for sharing writable data across >> machines. > > memcache is non-persistent. It's a cache, not a storage solution, so you > can not use it for anything that actually needs to be stored permanently.
Sure, but then you can go with something like Redis. But, again, if you go back to the original question, this has nothing to do with often-changing data in a couple of PHP include files: We have several Apache 2.2 / PHP 5.4 / APC 3.1.13 servers all serving mostly PHP over NFS (we have separate servers for static content)." So they are serving up all their PHP over NFS for some reason. -Rasmus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
