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

[Hanno Schlichting]

When we introduced this cache, it was based on benchmarking against
small and large sites. As the request itself is short-lived the memory
is just used for a short period of time.

This is the same sort of request cache that's often found in Plone via
plone.memoize. The main difference is that plone.memoize makes the
assumption that the request object is annotatable (in the
zope.annotation sense) and thus stores its cached values in annotations.
Zope itself doesn't make this assumption, so direct Zope code cannot use
this approach. Storing cached values in request.other was therefor the
least invasive approach.

Unless someone can produce benchmarks which show an adverse effect of
this cache, I'd consider the current approach to be reasonable.

** Changed in: zope2
       Status: New => Incomplete

-- 
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