Heads-up(/RFC) plan to remove full-cache invalidation from ZEO
Jim Fulton <[email protected]>
| Newsgroups | gmane.comp.web.zope.zodb |
|---|---|
| Message-ID | <CAPDm-FiEzGHmcYnrbDRs5XciNT5jTzcfnUJrq6dBdOpHWyLLVQ@mail.gmail.com> |
By default, if there were more than a configurable number (100 by default) of changes on a server while a ZEO client has been disconnected, the client verifies its cache by sending all of the serials for the objects in its cache to the server for verification. This is a behavior that has existed from ZEO's beginning and has turned out to be a very bad idea as it's expensive for both the client and server. I intend to remove this feature (cache verification) and drop the client cache if there have been too many changes on the server. This behavior can be configured now using the ClientStorage drop-cache-rather-verify option. This option will remain, but will default to true and will error if set to false. Jim -- Jim Fulton http://jimfulton.info -- You received this message because you are subscribed to the Google Groups "zodb" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.