[zope2-tracker] [Bug 1194811] [NEW] ZCatalog DateRangeIndex caching makes REQUEST large

khink keeshink at gmail.com
Wed Jun 26 11:41:40 CEST 2013


Public bug reported:

DateRangeIndex's _apply_index() [1] stores its result on the REQUEST [2]
for re-use in the same REQUEST. This is also the case for the query for
"active content" (effective date in the past), which is very common in
Plone. For large databases, this will be a huge result.

It's hard to say if that is a bad thing per se, i think it should be
benchmarked.

One thing is sure: It makes the DebugPanel a lot less usable for sure,
because that prints REQUEST.other, resulting in a large HTML page (6Mb
for about 450,000 record ids in the result cache ).

An alternative would be to cache the _apply_index() result someplace
other than on the request.

This report follows from a discussion on plone-users [3].

This probably applies to other indexes as well.

[1] Products.PluginIndexes.DateRangeIndex.DateRangeIndex.DateRangeIndex._apply_index() 
[2] REQUEST in capitals, to discern it from 'request' in the _apply_index() code, where it just means the catalog query
[3] http://plone.293351.n2.nabble.com/request-other-has-large-portal-catalog-X-key-td7566058.html

** Affects: zope2
     Importance: Undecided
         Status: New


** Tags: indexes zcatalog

-- 
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.
https://bugs.launchpad.net/bugs/1194811

Title:
  ZCatalog DateRangeIndex caching makes REQUEST large

To manage notifications about this bug go to:
https://bugs.launchpad.net/zope2/+bug/1194811/+subscriptions


More information about the zope2-tracker mailing list