Subject Oldest transaction
Author Nico Callewaert
Hi list !,

A while ago I mentioned some customers have poor performance, especially when > 20 connections. I'm aware of the fact that there is a design problem, I just can't figure out what exactly.
I checked with gstat and saw the following (probably disturbing numbers) :

Oldest transaction : 91891
Oldest active : 2956068
Oldest snapshot : 2956068
Next transaction : 2956086

I guess the gap between Oldest en Next transaction is way too big ? Am I right ? After doing a sweep, the Oldest and Next become equal.
I've read some articles on IBPhoenix, but I don't quite understand it. And I don't know what is causing that giant gap between Oldest and Next. All queries are set to AutoCommit, so when a record is inserted/updated, the transaction is committed. Or am I missing something ?

Many thanks in advance,

[Non-text portions of this message have been removed]