>> That's quite a number, when running in 24x7 mode! Although due to the >> example above, it seems you do explicit transaction management. So, >> either you still use automcommit somewhere, which results in a new >> transaction for every piece of work, our you have a lot of connections >> and work to be done by explicit transactions. >> >> I really think that you are using autocommit as well. The least >> expensive transactions are READ COMMIT READ ONLY, so basically make use >> of at least read-only transactions, when you are selecting stuff from >> the database and don't write. >> > > not really autocommit, but i don't let any transaction open. > when the code need some data, he call a global procedure that will gave > him the data he need. the procedure will open (and close) an transaction > each time and query the fb server. > > now i can open a transaction when each thead start and close it when each > thead end but i always hear that transaction must be short as possible :(
Long running read committed read-only transactions aren't a problem at all. If you are using Firebird 2.5, I wonder what the Trace API returns in respect to transaction tracing. -- With regards, Thomas Steinmaurer (^TS^) Firebird Technology Evangelist http://www.upscene.com/ http://www.firebirdsql.org/en/firebird-foundation/
