Quoting dan...@zoltak.com:
Great points Brendon!
We have a similar architectural to your setup running NetApp filers,
Apache/PHP web servers performing shared hosting for over 40,000+
websites.
We pull over 35k IOPS and 80% are from PHP stats and getattr's.
Someone earlier mentioned that people now use GlusterFS as an
alternative. GlusterFS native client runs like absolute crap with
Apache/PHP applications in order to get reasonable performance you
must use the GlusterFS NFS implementation and mount the GlusterFS
using NFS.
You end up in the same performance issues using GlusterFS and PHP.
More and more clustered PHP applications are using GlusterFS via
NFS. Due to the getattr and stat issues in PHP it doesn't scale well
in these sorts of deployments.
I would also like to add that newer Cloud concentric application are
developed so that they do not persistent data to local storage. This
then negates the use of NFS i.e. we can deploy code via git to the
nodes running on local storage. All dynamically generated user data is
persisted to object storage and sessions are persisted using the
memcache session handler.
However in order to support legacy applications that are not Cloud
centric then a network file system is the only viable option in shared
hosting environments.
Regards,
Dan Zoltak
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
