4 ms·
This could be a game changing blog post for self taught devs like me who are just getting into profiling code for improving it and such. I’m still reading it bu
by gigatexal 4y ago
This could be a game changing blog post for self taught devs like me who are just getting into profiling code for improving it and such. I’m still reading it but I’ve already bookmarked it for further study.
- genericlemon24 4y agoGlad to hear that :D One of my main goals was to show the entire progression of how I approached the problem, instead of just saying "here's the final result". I have another article that covers profiling in more detail, you might find it useful: https://death.andgravity.com/fast-conway-cubes#intro-to-profiling https://death.andgravity.com/fast-conway-cubes#intro-to-prof... Note that besides the cProfile text output, there are better, graphical tools for profiling; I've personally used pyflame+flamegraph.pl, and tuna.
- SleepyMyroslav 4y agoI wish that community would put a warning sign or something. The article is a collection of things that should never be done. People who want to learn software performance work need to start from a solid foundation. Mentioning that algorithms exist at the end is not good enough.