Proposal: Expand Filesystem JFR Events
Mike Hearn
mike at hydraulic.software
Fri Mar 24 10:29:04 UTC 2023
Hi Marius,
We'd support this proposal, although our use case is a bit different. We'd
really like to track file open/close pairs. We also support a desktop app
on Windows and unfortunately occasionally we've allowed file handle leaks
through because we mostly develop on UNIX. Being able to get stack traces
for file opens and closes in jfr logs would allow the creation of a tool
that processes these logs to find the source of handle leaks.
Do you still plan to add more events to the FS layer? If so, could you add
file open/close too?
These events don't have to be enabled all the time in production to be
useful. We can use them in CI runs to detect leaks right after they get
committed, but before they reach prod. I didn't quite follow the argument
that unless events can be thresholded nobody will use them, as by default
the JVM doesn't make JFR logs anyway. It's always opt in.
thanks,
-mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/hotspot-jfr-dev/attachments/20230324/e57194b5/attachment.htm>
More information about the hotspot-jfr-dev
mailing list