mikemccand commented on issue #15926: URL: https://github.com/apache/lucene/issues/15926#issuecomment-4226430309
Thanks @rmuir. I think we should start with just supporting `CPUTime` profiler (fixing `isIntersting()` to accept `jdk.CPUTimeSample` too)? After that, we can switch Lucene's tests profiler (`CodeProfilingPlugin.java`) to use `CPUTime` profiler instead of wall-clock sampling? (And remove that gradle thread check hack also, thanks for the pointer...). I'd like to see if it's working well/correctly on Lucene nightly benchy first (it's not, so far, because of this issue). Also, one big limitation is it only runs on Linux ... not sure if that's a showstopper for Lucene test profiler to swtich... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
