On Tue, Apr 12, 2011 at 8:19 AM, Doug Chamberlin
<chamberlin.doug@...> wrote:

> This whole question is making much ado about nothing. Transactions are
> very, very inexpensive in Firebird if no data from records is accessed
> and no data from records is changed. Since you need a round trip from
> the client to the server to get the generator value you cannot avoid
> that communication expense. The rest is lost in the shuffle.

Each transaction start and end dirties a page. In superserver that
doesn't matter but in classic and superclassic, it does because those
are hot pages - the header page and the most recent transaction
inventory page, and the page have to go to disk (at least in classic)
before they go to another process. If you've got a dozen clients
using generators as a polling alternative to events, you'll use a lot
of disk bandwidth. That's the problem events were created to
solve.

Best regards,

Ann