RE: [Zope-dev] Why not ZODB 3.1.3 with Zope 2.6.2?
[Paul Winkler] I downloaded the hidden 2.6.2b6 release (from http://zope.org/Products/Zope/2.6.2b6/Zope/view) and had a look in lib/python/ZODB/__init__.py, which gives its version as ZODB 3.1.2. Is there any reason it's not ZODB 3.1.3? Because 3.1.3 hasn't yet been tested with that particular version of Zope. Maybe just an oversight? No, but it's becoming one wink. I could easily check any ZODB-3.1.3 changes to the Zope-2.6 branch, unless somebody knows a reason not to do so. The changes are delicate, ZODB3 3.1.4 is probably coming soon, and all these changes need also to be ported to the ZODB3 HEAD, ZODB3-3_2-branch, ZODB4, the experimental ZODB3 3.3 branch, and God only knows how many Zope branches at this point. If you want to take all those on, cool, else it's probably better to wait for Jeremy and me to do them in a controlled way. Also, why doesn't ZODB/Tools come with zope? There's some really handy stuff in there, some of which gets mentioned on the zope list from time to time; it would be nice if newbies could get hold of it easily. Leaving that to someone else. On a related note, NEWS.txt in ZODB 3.1.3 mentions that there is a new Tools/README.txt ... but it's not actually in the tarball :-) Oops! A last-second addition that didn't get added to MANIFEST. That's repaired on ZODB3-3_1-branch now. Thanks for pointing it out. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] upgrading and getting rid of SearchIndex
I've got a couple of ZODBs here that's been gradually upgraded over time from Zope version to Zope version (I think they were initially started on Zope 1.x!) I'm sick of the SearchIndex deprecation warnings, so I've gone and re-created all of the catalog indexes. This fixed it for the indexes, but it's still showing up - any ideas how I can determine which objects are still referencing SearchIndex? Is it worth making a little script that Does The Right Thing when upgrading? It's a pretty trivial script to open a Data.fs and hunt for indexes, then re-create them - is this something that could/should be included with Zope? Anthony -- Anthony Baxter [EMAIL PROTECTED] It's never too late to have a happy childhood. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.7 Timeline
Hi! WRT the Zope 2.7 timeline: Couldn't we just get a new beta that includes the most critical bug fixes very soon? If 2.7 doesn't get deployed on almost production systems there will not be too much further testing I guess. And currently most non-experts will not even be able to get a Zope 2.7b1 system up and running with additional Products. The main issues that come to my mind are: - Fixing the zope.conf so you don't need to manually add a path to the Products directory - Some simple example in zope.conf to help with ZEO setups. - The fixes to the VirtualHostMonster, so that the tab for configuring mappings is displayed again (fixed in the CVS) I am willing to help with that. I'll just have to get my CVS checkin SSH certificates fixed first ... And of course we could have a Zope 2.7 bug day, too. Cheers Joachim ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.7 Timeline
2.7.0b2 was released yesterday with both of these bugs fixed. Is that soon enough? ;-) On Wed, 2003-08-27 at 05:42, Joachim Werner wrote: Hi! WRT the Zope 2.7 timeline: Couldn't we just get a new beta that includes the most critical bug fixes very soon? If 2.7 doesn't get deployed on almost production systems there will not be too much further testing I guess. And currently most non-experts will not even be able to get a Zope 2.7b1 system up and running with additional Products. The main issues that come to my mind are: - Fixing the zope.conf so you don't need to manually add a path to the Products directory - Some simple example in zope.conf to help with ZEO setups. - The fixes to the VirtualHostMonster, so that the tab for configuring mappings is displayed again (fixed in the CVS) I am willing to help with that. I'll just have to get my CVS checkin SSH certificates fixed first ... And of course we could have a Zope 2.7 bug day, too. Cheers Joachim ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.7 Timeline
Chris McDonough wrote: 2.7.0b2 was released yesterday with both of these bugs fixed. Is that soon enough? ;-) Yes it is ;-) Sorry, I didn't check before ... ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Very severe memory leak
On Mon, 2003-08-25 at 23:35, Shane Hathaway wrote: On 08/25/2003 05:12 PM, Leonardo Rochael Almeida wrote: Let me restate something important, because I forget about it myself sometimes when I'm thinking about this problem: *upgrading to 2.6.1 made the situation definetly worse*. The site became lot faster, but the memory situation became intolerable, so I believe there is something introduced between 2.5.1 and 2.6.1 that is causing our problems. Is there a fix in 2.6.2 for some leak introduced *in* the 2.6 series? I think there are, actually, but AFAIK they were obscure and rare. That would make the likelyhood of our problems being caused by them very small. Is there any way to know if we're hitting them? Let's assume we're not hitting a 2.6 bug. we could be hitting a 2.6 feature :-) I've read Casey's article about optimizing ZCatalog and I know there has been a lot of ZCatalog optimization work. Has there been any changes in 2.6 (in ZCatalog or thread cache or anywhere else) that was a tradeoff of memory for speed? If there was such a change, it would explain why we had a slow site that did fit into memory while now we have a fast one that doesn't. Another thing, we have already estabilished that clearing the caches resets the DateTime refcount, so the DateTime must be anchored to the caches somehow. So, if the DateTime refcounts are constantly in the 50k-100k range, how come the cache object count for all threads is below 5k? If the DateTimes are in catalog metadata or indexes, this would make sense. If they're indirectly attached, it means that a lot of DateTimes are anchored in just a few objects, so no matter how much I reduce the target cache size, it might never be enough to throw out the DateTimes... They are probably in the ZCatalog. You mean that one ZCatalog object is in the cache, and (indirectly) attached to it are thousands of DateTimes? Then we have a huge problem. I was counting on the objects in cache parameter to put an upper bound in Zope memory consumption, even if this upper bound was a little fuzzy. Remove all metadata fields you can. If you have index dates, use DateTimeIndexes rather than the standard indexes. Well, this is a classic ZCatalog+ZClass site. Almost all ZClasses are CatalogAware and they're all cataloged in the monster ZCatalog named Catalog in the folder that represents the root of the site (as served by Apache) because that's how CatalogAware ZClasses work out of the box (I know the catalog name can be changed). It has a huge amount of Indexes and Metadata. The client grew the site organically, creating ZClasses and hanging them in the same ZCatalog as he was needing them. It's gonna take a lot of time to untangle it all and we're working on it, but for now we need to deal with the emergency that is the fact tha migrating to 2.6.1 put us in the very hot spot of not having a way to put an upper bound to Zope memory consumption. I find it helpful to simply visit the information ZCatalog is storing for just one cataloged object. In the catalog contents view, click one object. Look at each field and consider how ZCatalog might misuse that field for other objects. What kind of misuse you have in mind? hmm, any chance of this remote console showing up somewhere? :-) I've attached what I threw together. Thanks! I might use it to navigate the thread object cache. It's unfortunate you have to go so deep, but that sounds like a good plan. Anyone know off the top of their head how do I get to the object caches? Cheers, Leo -- Ideas don't stay in some minds very long because they don't like solitary confinement. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )