pablogsal

7 ms·

1. 1.▲
   by pablogsal 3y ago

   Have you tried aggregated capture files? https://bloomberg.github.io/memray/run.html#aggregated-captu... With that option the files are much much smaller and much easier to analyse
2. 2.▲
   Intent to approve PEP 703: making the GIL optional(discuss.python.org)

   478 points by pablogsal 3y ago|499 comments
3. 3.▲
   by pablogsal 4y ago

   One thing to note is that we support tracking forked/child processes as well! >> - Much lower overhead, sounds like. I actually think Fil has the potential to be faster in some situations because it seems that aggregates the flam
4. 4.▲
   by pablogsal 4y ago

   Yeah, please hook me in! You know my email :)
5. 5.▲
   by pablogsal 4y ago

   Nice! Fil looks like an awesome profiler and is fantastic that works in other platforms. I am super excited to see more cool features and https://pythonspeed.com/sciagraph/ looks fantastic :)
6. 6.▲
   by pablogsal 4y ago

   It does much more than that! It tracks every single allocation and dumps it to a file that can later be analysed in many ways. Currently our reporters report peak memory (and leaked memory at the end of the execution) but technically any