[ https://forge.continuent.org/jira/browse/SEQUOIA-1117?page=all ]
Emmanuel Cecchet resolved SEQUOIA-1117:
---------------------------------------
Resolution: Fixed
Fix Version: (was: sequoia 2.10.11)
Implemented in CVS HEAD
No backport scheduled yet for 2.10 branch
> Add a logger to profile request execution time
> ----------------------------------------------
>
> Key: SEQUOIA-1117
> URL: https://forge.continuent.org/jira/browse/SEQUOIA-1117
> Project: Sequoia
> Type: New Feature
> Components: Core
> Reporter: Emmanuel Cecchet
> Assignee: Emmanuel Cecchet
> Fix For: Sequoia 4.0
>
> Original Estimate: 2 hours
> Remaining: 2 hours
>
> Right now the only way to get query execution time is to use the monitoring
> feature that uses only in-memory stats and can lead to memory outages in the
> long run.
> This new feature would add a new logger similar to the request logger that
> would log timing information about query execution (unlike the current query
> arrival time logged in request.log).
> I suggest to have a profiling.log file that contains that information and can
> also report time for begin/commit/rollback operations. Note that it could
> also be interesting to expand the profiling to metadata calls (things like
> getTables and so on) but this is currently out of the scope of this feature
> request.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
