Down for maintenance
I wish I had more interesting stuff to blog about, than the status of this blog itself... Here's just to inform you, that in my ongoing attempt to wrangle the performance problems I'm still experiencing on this host I've decied to temporarily deactivate tomster.org for a day or two. All requests (except for the atom and RSS-feed) are currently detoured to a static "down-for-maintenance" page.
I then want to compare the cpu-usage of, say 48 hours during normal business days with the same period of the week before.
The good news is, that meanwhile I've seriously streamlined the setup on this machine, so that currently every other site hosted here exceot for my own is enjoying increased performance thanks to CacheFu and Apache's mod_diskcache ;-)
Next up: putting Squid instead of Apache in front of Zope.
some statistics
since we use several zope/plone instances on our server, maybe this helps a bit on determining a component (or not) CPU time python zope plone in 12 hours 16:38.31 python2.3 Zope285 2.1.2 0:35.23 python2.3 Zope285 2.1.2 4:02.30 python2.4 Zope292 2.1.3 (svn/unreleased) 2:09.85 python2.3 Zope286 2.1.3 (svn/unreleased) 0:19.18 python2.3 Zope287 2.5
still working on a python2.4 Zope292 2.5 instance. But up to now you can't really determine a bad component from here. The first site with the most CPU time used is a site mainly consisting of Image galleries. So sending out the pics will have a major impact on that. the 2.4/292 instance is a file serving instance, but not open for public and quite low traffic. So this MIGHT indicate a problem with python2.4 and Zope 2.9.2