News for hackers. Stuff that matters.
Re:Hunting Performance in Python Code: Measuring Memory Cons... by mattmanser on Thursday June 01, 2017 @11:35AM (#14461152)
I admit they take time up front to learn to use and interpret the results, but it's a valuable skill and worth doing every year or so even on smaller projects to see if there are any easy wins.
Re:Hunting Performance in Python Code: Measuring Memory Cons... by mherrmann on Thursday June 01, 2017 @11:50AM (#14461321)
Omg, cProfile just let me shave 900ms off the startup-time of my PyQt-based file manager [1]. I would not have found this that quickly without your hint. Thank you!

[1]: https://fman.io

Re:Hunting Performance in Python Code: Measuring Memory Cons... by mattmanser on Thursday June 01, 2017 @12:19PM (#14461621)
No problem!

This was on the front page today, but flagged as a dupe, also an interesting read as it explains about flame graphs too:

https://news.ycombinator.com/item?id=14384370

Re:Hunting Performance in Python Code: Measuring Memory Cons... by mherrmann on Thursday June 01, 2017 @11:38AM (#14461201)
Yes, you're right. Mine is just the simplest and probably least powerful solution. cProfile is definitely more powerful.
Re:Hunting Performance in Python Code: Measuring Memory Cons... by rrauenza on Friday June 02, 2017 @01:59AM (#14467798)
I think yours still has a valid use in production logging...