2 ms·
I think I disagree about the observability -- vtune is a lot easier to use when just tuning straight C++ rather than java
by x0x0 11y ago
I think I disagree about the observability -- vtune is a lot easier to use when just tuning straight C++ rather than java
- pron 11y agoAre you familiar with JMH's perfasm? http://psy-lob-saw.blogspot.com/2015/07/jmh-perfasm.html http://psy-lob-saw.blogspot.com/2015/07/jmh-perfasm.html And for profiling apps on production, I've yet to encounter a more thorough, low-overhead profiler than Java Flight Recorder.
- x0x0 11y agono but i'll check it out this afternoon. Thanks!
- threeseed 11y agoVTune is not too dissimilar to JProfiler. And as pron mentioned plenty of tools exist for lower level access.
- vitalyd 11y agoVtune gives access to PMU counters as well as attributing them to assembly. JProfiler is a purely java level profiler (it won't even tell you Hotspots in the JVM itself, nevermind assembly). They're not really comparable.
- x0x0 11y agojprofiler, at least for my use cases, isn't really similar to vtune at all. I know what my hot spots are: it's the inner bits of algorithms that run a few billion to a few trillion times. What I need to do is understand, as granularly as possible, the exact instructions and how the various caches and memory are operating. Convex and tree optimizers are generally memory speed limited and my goal is to have this code run at eg 0.9+ of memory b/w speed.