Discussion
An API from another team we rely on suddenly got slow. like >2s/request. When asked why, the response was: we use a new model for our calculations and it's slower.
I insisted that it should be faster and offered to show how to use a profiler. The person from the other team thought the math part was slow and not the trivial looking stuff around it. Profiler showed the math is fast and the stuff around it is 97% of the time.
Got a 8-9x speedup in the first hour
Learn how to use a profiler!
Also it would be great to have a web(gl) based version of qcachegrind for visual analysis of profiles converted to the cachegrind format.
Hmm I would like to make a cheatsheet for how to profile in the most common languages - or ideally some kind of community effort similar to https://rosettacode.org/wiki/99_bottles_of_beer#Elixir where users can submit their examples for their favorite language so there is zero excuse 😊
Hmmm hmmm need to think about how that could be done. I can definitely seed with 3-4 examples. Just need to find a decent / generic example to illustrate the benefit clearly.
If you have an idea how to do something like this, lemme know :)
@hukl This sounds like an awesome idea!
@hukl Xcode’s Instruments is very powerful but woefully underdocumented.
Golang pprof flamegraphs are nice.
Install bonfire.cafe
Get the full app experience
