bawr_hszm

5 ms·

1. 1.▲
   by bawr_hszm 5y ago

   Loading data before you fork works pretty well, but the overall effectiveness heavily depends on the type of data involved. If it's something like numpy arrays or similar large, indivisible objects, you're golden. If you want to
2. 2.▲
   by bawr_hszm 7y ago

   I like it, and I appreciate that you changed your mind - I'm still staunchly in the flamgraph camp of capturing and displaying whole stacks, but now I could see using this for small code samples, especially with the memory usage inform
3. 3.▲
   by bawr_hszm 7y ago

   I can understand this approach, but I fundamentally disagree with it - the first duty of a profiling tool is not to mislead the user . In this example, the program spends a third of the time just sleeping / blocked, a third of the tim
4. 4.▲
   by bawr_hszm 7y ago

   Sadly, relying on Python's signal handling is not enough to get robust profiling information the moment your code is spending a significant chunk of time outside of simple Python calls. This is because signals don't get delivered