News for hackers. Stuff that matters.
Re:Why performance optimization is hard work by AaronAPU on Tuesday April 29, 2025 @03:18PM (#43836849)
I spent 10 years straight doing C++ and assembly optimization. My work is still fun these days but that was probably the most enjoyable work of my career in terms of the actual day to day coding.

Code cleanup in general is the same for me, but it’s really hard to justify putting much time into that when running your own company solo.

Re:Why performance optimization is hard work by jasonthorsness on Tuesday April 29, 2025 @03:23PM (#43836903)
What tools did you use to assess the results of your changes?
Re:Why performance optimization is hard work by AaronAPU on Tuesday April 29, 2025 @04:35PM (#43837737)
The routines were individually benchmarked using some custom tools (iterate repeatedly and use statistical analysis to converge on an estimate). Always compared against a plain C reference implementation.

Then there was a system for benchmarking the software as a whole on a wide variety of architectures, including NUMA. With lots of plots and statistics.

Usually you’d eventually end up at a point where the improvements are below the noise floor or they help on some systems and cause regression on others. The rule was usually “no regressions”

VTune for multithreading optimization. Built a fibers and lockfree system for efficient scheduling.

Re:Why performance optimization is hard work by ecshafer on Tuesday April 29, 2025 @08:58PM (#43840001)
That sounds like a pretty good set up with a lot of investment, HFT shop?
Re:Why performance optimization is hard work by AaronAPU on Wednesday April 30, 2025 @02:00PM (#43848722)
Codecs