G
George Potemkin
Guest
Gus, > the “per tx” numbers in promon are somewhat inaccurate but i would not characterize them as meaningless. Our customers are splitting the table space used by their application into a few databases (for example, one of the customers stores data in 16 databases). When the code inisde transaction block reads data in one of these databases Progress opens a transaction here even if the code will not update the database. With data speaded between many databases it's highly likely that the most tranactions will never become ACTIVE. IMHO, the 'Commits' counter does not have too much sense when it by 90% consists of transactions in BEGIN status. Of course, when all data are stored in one database then the ratio between BEGIN and ACTIVE transactions can be opposite. But yes, I said about the meaningless of the “per tx” numbers stronger than I should. Sorry.
Continue reading...
Continue reading...