This is the 'batch' or 'distribute' pattern that crops up in many
fields.
The best path is normally to understand what the conflicts are, and
where the time is spent.
If in, this case, much time is spent in the preamble, and the actual
inserts are quick, then diving down one time through the security
layers and stuffing in 10 items is clearly better than 10 preambles,
one for each insert.
The other truism is that all optimisation is for a single case.
There may be different answers for different cases. Ideally a single
parameter would be enough to tune the system for different cases.
Good luck Roche, with the outcome, I'm excited to see some figures.
--r.
On 2 Nov 2007, at 15:24, David Binger wrote:
On Nov 2, 2007, at 10:58 AM, Lennart Regebro wrote:
It seems to me having one thread doing a background consolidation one
transaction at a time seems a better way to go,
Maybe, but maybe that just causes big buckets to get invalidated
in all of the clients over and over again, when we could accomplish
the same objective in one invalidation by waiting longer and executing
a bigger consolidation.
although certainly the
best thing would be to test all kinds of solutions and see.
No doubt about that.
_______________________________________________
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zodb-dev
Russ Ferriday
[EMAIL PROTECTED]
office: +44 118 3217026
mobile: +44 7789 338868
skype: ferriday
_______________________________________________
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zodb-dev
