Add timing statistics to the monitoring tables
----------------------------------------------
Key: CORE-4402
URL: http://tracker.firebirdsql.org/browse/CORE-4402
Project: Firebird Core
Issue Type: Improvement
Components: Engine
Reporter: Dmitry Yemanov
It would be useful to track timing for different operations and aggregate these
values at request / transaction / connection / database levels as other runtime
statsitics is maintained. In particular, I was thinking about total time spent,
CPU time (maybe separated for user / kernel) and various waiting time -
database I/O waits, lock manager waits, cache latch waits, etc. This opens wide
possibilities for tracking down the performance issues. Note that I don't
suggest tracking time for particular sub-operations (retrievals, sorts, joins,
etc), so it's not about profiling the algorithms. It's more about finding
bottlenecks in I/O or contention.
As time tracking is likely to be a costly operation, it should be disabled by
default and enabled explicitly by the DBA, probably for either particular
connections or globally for a database.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
