Getchell, Adam wrote:
So, as a follow-on to a (hard to answer, apparently) question earlier
about Zope/Plone spinning, does anyone know of efforts to make Zope
(and Plone) more scalable?
I'm aware of ZEO, it shows up in Google, we run ZEO already. We'll
look at Cache-fu + Squid, etc.
But ZEO only allows you to scale the front end; it does nothing for
the back-end, which is still just one box.
ZEO allows you to scale the application server including all the logic.
The database (the ZEO server) typically remains a single node (though
there are ways to cluster those too), but the load on this is likely low
compared to the load on the clients.
And now that we've learned that Plone products live in the filesystem
(of the front ends) as well as the database (on the backend), I'm
curious if there's any work being done to scale out the back end too.
Only data lives in the database. "Data" includes settings and content,
and can include templates, but whilst they are loaded from a ZEO DB
server, they are executed by the ZEO client handling the request.
Our Zope/Plone setup with 20+ instances falls over 4-5 times a day.
I would caution against having 20+ instances in in a single Zope setup.
We have these really handy scripts which start it up again, within 5
minutes.
Look at www.supervisord.org, but you shouldn't need to restart. You need
to identify why it falls over, not try to plaster over the symptom.
Start by looking at your logs to understand why it's falling over.
Martin
--
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book
_______________________________________________
Setup mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/setup
