|
|
|
|
|
|
by jpgvm
1175 days ago
|
|
|
Such a task is usually thankless work so, thank you. :) I don't doubt my favorite profiler, YourKit also uses your code. Profilers are probably the class of tool that most drastically improved the code I write so if anyone reading hasn't really felt the need to use one, you should. Just a cursory glance can quickly verify assumptions about runtime performance. Even if the code is currently acceptable it helps to be mindful of where cycles are being spent (and lock contention, network blocking, etc) so if you end up doing some refactoring anyway that additional context and knowledge can guide improvements that aren't strictly "performance work". |
|
|
It's just a game of whack-a-mole, finding new segmentation faults and other bugs is quite easy when you know how to write good test code. Fixing the actual bugs less so. But it's fun and I do this for a living in the SapMachine team at SAP SE.
> I don't doubt my favorite profiler, YourKit also uses your code.
They surely do profit by work improving the profiling APIs.
> Just a cursory glance can quickly verify assumptions about runtime performance.
Yes. But there aren't enough people educating people on profilers. So I started blogging and talking (https://youtu.be/Fglxqjcq4h0) on this topic. Besides fixing all the bugs and implementing my own profile viewer based on FirefoxProfiler (https://plugins.jetbrains.com/plugin/20937-java-jfr-profiler).