[ZODB-Dev] [ZEO] Dealing with long startup times with out-dated index files/Index snapshots?

[Andreas Jung]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jim Fulton wrote:
>
>>> Another issue is that, as things are now, while an index is being
>>> saved, no transactions can be committed.  This is less serious now
>>> that saving indexes is much faster, however, saving a large index
>>> may still take several seconds, and that might be a problem for
>>> some applications.
>>>
>>> I'd be happy to add an option to save indexes after every N
>>> records written, where N would be given by the option.
>> So what is the difference between such a new option and fixing the
>> "flawed"
>> algorithm as mentioned above?
>
> There would be explicit control. You's be able to say how often (in
> terms of records written) you'd save indexes.

Assuming we could get this feature with ZODB 3.10 (perhaps with a
funding)..
could ZODB 3.8 clients (Zope 2.11) safely talk with a ZODB 3.10 ZEO
server?

Andreas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAktqu/sACgkQCJIWIbr9KYzQhwCdFvlwf60TovhujXkchwAFp/Up
lfoAoLbHUp1BI/3l/GogvG7PH5FpJFPh
=7XhT
-----END PGP SIGNATURE-----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: lists.vcf
Type: text/x-vcard
Size: 316 bytes
Desc: not available
Url : http://mail.zope.org/pipermail/zodb-dev/attachments/20100204/3a2d94bc/attachment.vcf