Performance degradation through wstats

I want to be able to use onstat -g wts and onstat -g qts. So, i added to my onconfig in my test environment: WSTATS 1 QSTATS 1 I tested some typical queries, statements and transactions and measured the execution times. The resulta are, that with WSTATS and QSTATS activated the execution times rose around 8-9%. (With QSTATS only 1-2%, and with WSTATS only 6-7%.) Are these typical values for performance degradation from WSTATS/QSTATS activated? (If yes, i would activate WSTATS and QSTATS on the production box, because 8-9% are no an issue.) Or are there special "areas" (type of statements etc ...) where the performance degradation is much bigger? Thanks.

Michael Schmid wrote: ... > I tested some typical queries, statements and transactions > and measured > the execution times. > The resulta are, that with WSTATS and QSTATS activated the execution > times rose around 8-9%. > (With QSTATS only 1-2%, and with WSTATS only 6-7%.) > > Are these typical values for performance degradation from > WSTATS/QSTATS > activated? > > (If yes, i would activate WSTATS and QSTATS on the production box, > because 8-9% are no an issue.) > Or are there special "areas" (type of statements etc ...) where the > performance degradation is much bigger? I am astonished that you observed such a big difference with WSTATS turned on.I'd rather expected lower values. In my opinion it is a good idea to have it turned on. Regards Tilman

Yes, i agree with you, that it's a good idea to turn this statistics on. I asked, because i heard (in older constributions to c.d.informix) that it's a very bad idea (performance wise) to use this statistics in a production environment.