Heiko wrote:

> One thing I notice when several clients try to generate new counter
> values at the same time is that obviously counters are given back to
> the client in kind of "chunks". That is to say one client generates
> for example 15 new counter values in a row very quickly while the
> others are waiting. I would have expected a more balanced generation
> of counter values across the clients.

Sounds like getting those 15 counter values may happen within the same
transaction. No other transaction will be allowed to update that
record until the transaction that did the update commits. Neither will
those other transactions be allowed to update the record until they
can see the most recent version (depending on transaction isolation).

Set