Created on 2015-03-03.23:39:17 by zyasoft, last changed 2019-08-04.16:12:18 by jeff.allen.
||Author: Jim Baker (zyasoft)
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: https://github.com/jythontools/jython/blob/master/src/org/python/core/Py.java#L1992
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.
||Author: Jeff Allen (jeff.allen)
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.
|2019-08-04 16:12:18||jeff.allen||set||resolution: accepted|
+ Use Java logging framework