Tuesday 11 November 2008 5:54:12 am
If money is not a issue then I would recommend a SAN setup, scales a lot better then NAS because eZ Publish uses the files system quite heavy(4.1 will improve the situation a bit, but SAN is still superior to NAS).
I have seen numbers from 80- 140 (local disk) 120 - 180 (SAN) req/second pr server, so this should be possible. But since a webpage contains more then just the html (images, javascript, css, video), you should use a reverse proxy like Varnish in front independent on how you choos to setup eZ Publish to lighten the load on the backend server(s) and be able to have a decent headroom to scale on.
eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom
|