Re: instrumenting the driver
От | John R Pierce |
---|---|
Тема | Re: instrumenting the driver |
Дата | |
Msg-id | 42B2D743.6080604@hogranch.com обсуждение исходный текст |
Ответ на | instrumenting the driver (Dave Cramer <pg@fastcrypt.com>) |
Список | pgsql-jdbc |
Dave Cramer wrote: > There has been a request to instrument the driver for measuring timing. > > One mechanism that comes to mind is to allow one listener in execute, > etc. Or to simply measure it ourselves. I rather like the `dtrace` approach in Solaris 10.. It provides instrument hooks for all kinds of stuff but the hooks do nothing if nothing has hooked them (presumably implemented with an inline macro of some kind). The dtrace utility has a wide range of timing, counting, classification, etc statistics gathering capabilities. Solaris 10 has hooks on virtually every system routine entry and exit, as well as many other things. Now, obviously, thats a lot more sophisticated than we'd want to bite off in a jdbc driver, but the idea of a generalized hook on entry and exit of each major method is a good one, the user routine that hooks these could classify the statement being executed if it wanted to (at its own expense, naturally)
В списке pgsql-jdbc по дате отправления: