Hello, For reasons I can't seem to grasp, my Zope has gone real slow on me ... I switched from using Localizer + TranslationService to using the collective's PlacelessTranslationService (PTS) 1.0fork-rc7 ... And since then this occurs. On the good side, this seems to have fixed my leakage problem however! I've tried increasing the number of threads but it doesn't really seem to help, as well as the connection pool. CPU usage seems to be ~25-30% which isn't bad. (It's 4 PIII 700Mhz) I've tweaked the interval check as per some docs found on zope.org ... There's 4GB of RAM, which is plenty. I've set zeo-client-name, but that didn't seem to do much, so now I've set the "client" parameter in the zodb_db -> zeostorage section, and now the cache file DOES appear (Is this a bug? Shouldn't have zeo-client-name done the job?). Also is there anyway to pre-fetch/fill the caches in the threads? I'm wondering if the act of filling those caches might be what's slowing things down? In which case maybe I should try with less threads?? Of course a lot fo this started when I started using PTS ... Could it be the culprit somehow? I use Apache with mod_proxy ... Apparently the requests pile up faster than Zope can take them ... Sometimes I can stop Apache and watch Zope keep working for minutes after that (Sometimes longer than I'm willing to wait, at which point I shut it down!). Any thoughts/ideas/potential solutins would be most welcome! Thanks, Jean-François Doyon Internet Service Development and Systems Support / Spécialiste de dèveloppements internet et soutien technique Canada Centre for Remote Sensing / Centre Canadien de télédétection Natural Resources Canada / Ressources naturelles Canada http://atlas.gc.ca Tel./Tél. : (613) 992-4902 Fax: (613) 947-2410