Mutaz Qasem a écrit : > Hi All, > > I'd like to ask if it is possible to use one ez publish installation > to build many web sites. I'm aim of that is to get all content > centralized and available to all sites. This is doable and actually done by quite a few clients. You just need to take care of all the settings, such as the node id of the homepage, languages, access permissions etc... > What do you think of it in terms of efficiency and performance? Do > clustering techniques overcome the performance issues? and what if the > sites I'm going to build have high traffic? > I really need to know to what extent ez publish is scalable. It is hard to say "yes" or "no" to such a vague question. There are a lot of best-practices for achieving scalability with ezpublish, but you should start out with some rough estimates of the expected traffic.
Generally speaking you will get best results with: a reverse proxy (eg. varnish or squid) a pool of webservers dedicated to serving the frontend interface one server dedicated to editing (serving the admin interface) and running php scripts / cronjobs one server dedicated to searching (solr part of ezfind or other indexing engine) a big fat db server a san storage that uses a shared filesystem (ocfs2, gfs) for all the ezpublish servers a fast network connection between all of the above bye Gaetano -- Sdk-public mailing list [email protected] http://lists.ez.no/mailman/listinfo/sdk-public
