One could use a profiler, but why not just halt the program? [closed]

On Java servers it’s always been a neat trick to do 2-3 quick CtrlBreakss in a row and get 2-3 threaddumps of all running threads. Simply looking at where all the threads “are” may extremely quickly pinpoint where your performance problems are.

This technique can reveal more performance problems in 2 minutes than any other technique I know of.

Leave a Comment