filprofiler
filprofiler copied to clipboard
A Python memory profiler for data processing and scientific computing applications
Bumps [inferno](https://github.com/jonhoo/inferno) from 0.11.13 to 0.11.15. Changelog Sourced from inferno's changelog. [0.11.15] - 2023-02-11 Changed Updated to clap v4, which bumped MSRV to 1.64.0. #267 Updated to env_logger 0.10. #281...
Once #492 is fixed, macOS won't have OOM detection. It should eventually be re-enabled with a more robust check, e.g. `vm_pressure_monitor()` (http://newosxbook.com/articles/MemoryPressure.html)
Use-Case: Run fil as part of a test to verify that memory usage doesnt (drastically) increase from one commit to another I read https://pythonspeed.com/fil/docs/how-it-works.html, and it does mention that, >...
* [ ] Add `--ext filprofiler` or something to the json file * [ ] Update the docs to remove that requirement
A common pattern (in BLAS libraries, numexpr, blosc2, Polars) is to have a thread pool that runs tasks on behalf of the Python thread. Allocations can happen in this thread...
Specifically in `interpreter` test, `debug_assert!(self.check_threshold_bytes < current_threshold);` in `too_big_allocation()`.
Could you please provide wheels for Python 3.12 on pypi ? Thanks