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. 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. Our Zope/Plone setup with 20+ instances falls over 4-5 times a day. We have these really handy scripts which start it up again, within 5 minutes. But I'm interested if there's a better solution in the works than this band-aid approach. (NB: Rsync'ing data.fs is unappealing when it routinely goes over 2GB, and users are constantly making changes to their sites, which is, after all, the point of having a CMS.) Thanks for your attention, *************** * Adam Getchell, M.S. * Director of Information Technology * College of Agricultural & Environmental Sciences, UC Davis * [EMAIL PROTECTED] (530)752-8008 *************** "Invincibility is in oneself, vulnerability in the opponent." -- Sun Tzu _______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
