Title: Jython runtime instrumentation
Type: rfe Severity: normal
Components: Versions: Jython 2.7
Status: open Resolution: accepted
Dependencies: Use Java logging framework
View: 2778
Assigned To: Nosy List: jeff.allen, pekka.klarck, zyasoft
Priority: normal Keywords:

Created on 2015-03-03.23:39:17 by zyasoft, last changed 2019-08-04.16:12:18 by jeff.allen.

msg9579 (view) Author: Jim Baker (zyasoft) Date: 2015-03-03.23:39:16
Jython logs to stderr, up to a verbosity level of -vvv, a variety of runtime events, most notably in import resolution. The logging code is simple:

It would be helpful to get more detailed runtime output by expanding what is logged; choice of output log; and especially with timestamps. Such instrumentation could help diagnose problems in say excessively long import times.

We should look at integrating with some widely used instrumentation package in doing so.
msg12618 (view) Author: Jeff Allen (jeff.allen) Date: 2019-08-04.16:12:18
I noticed I'd somewhat duplicated this in #2778. I didn't spot it as a duplicate because of the title majoring on "runtime instrumentation", whereas richer logging is what's really on my mind in #2778.

I'm not sure what "runtime instrumentation" means, but I'm working on the assumption that if we get the logging in place (with timestamps, the instrumentation needed is a thing that consumes it.

Logging is not the right mechanism if investigation needs micro-benchmarks, but it is good for finding what phases of start-up, or an application, are costly.
Date User Action Args
2019-08-04 16:12:18jeff.allensetresolution: accepted
dependencies: + Use Java logging framework
messages: + msg12618
nosy: + jeff.allen
2015-03-03 23:39:17zyasoftcreate