Opened 5 years ago
Closed 5 years ago
#2188 closed enhancement (fixed)
log request processing time in rasserver log
Reported by: | Dimitar Misev | Owned by: | apercov |
---|---|---|---|
Priority: | major | Milestone: | 10.0 |
Component: | servercomm | Version: | 9.8 |
Keywords: | Cc: | Bang Pham Huu, Peter Baumann, Vlad Merticariu | |
Complexity: | Medium |
Description
Currently in rasserver log lines for each request look like this:
[INFO] - 2019-10-10 11:29:06,786: Request: 'SELECT c FROM test_rgb AS c'... parsing... checking semantics... evaluating... result type 'set <marray <char, [0:78]>>', 1 element(s)... ok, transferred 151 bytes.
It will be good to log also here how long it took to evaluate the query, e.g.
[INFO] - 2019-10-10 11:29:06,786: Request: 'SELECT c FROM test_rgb AS c'... parsing... checking semantics... evaluating... result type 'set <marray <char, [0:78]>>', 1 element(s)... ok, execution time X ms, result size 151 bytes.
This should be done in servercomm.cc whereever the "transferred .. bytes" is currently logged. Use common/util/timer.hh for measuring elapsed time since starting the query evaluation to when the result is returned.
Change History (2)
comment:1 by , 5 years ago
Status: | new → accepted |
---|
comment:2 by , 5 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Note:
See TracTickets
for help on using tickets.