base on Scalene: a high-performance, high-precision CPU, GPU, and memory profiler for Python with AI-powered optimization proposals  # Scalene: a Python CPU+GPU+memory profiler with AI-powered optimization proposals by [Emery Berger](https://emeryberger.com), [Sam Stern](https://samstern.me/), and [Juan Altmayer Pizzorno](https://github.com/jaltmayerpizzorno). [](https://join.slack.com/t/scaleneprofil-jge3234/shared_invite/zt-110vzrdck-xJh5d4gHnp5vKXIjYD3Uwg)[Scalene community Slack](https://join.slack.com/t/scaleneprofil-jge3234/shared_invite/zt-110vzrdck-xJh5d4gHnp5vKXIjYD3Uwg) [](https://pypi.org/project/scalene/)[](https://anaconda.org/conda-forge/scalene) [](https://pepy.tech/project/scalene)[](https://anaconda.org/conda-forge/scalene) [](https://pepy.tech/project/scalene) [](https://marketplace.visualstudio.com/items?itemName=EmeryBerger.scalene)   (tweet from Ian Ozsvald, author of [_High Performance Python_](https://smile.amazon.com/High-Performance-Python-Performant-Programming/dp/1492055026/ref=sr_1_1?crid=texbooks))  ***Scalene web-based user interface:*** [http://plasma-umass.org/scalene-gui/](http://plasma-umass.org/scalene-gui/) ## About Scalene Scalene is a high-performance CPU, GPU *and* memory profiler for Python that does a number of things that other Python profilers do not and cannot do. It runs orders of magnitude faster than many other profilers while delivering far more detailed information. It is also the first profiler ever to incorporate AI-powered proposed optimizations. ### AI-powered optimization suggestions > **Note** > > To enable AI-powered optimization suggestions, you need to enter an [OpenAI key](https://openai.com/api/) in the box under "Advanced options". _Your account will need to have a positive balance for this to work_ (check your balance at https://platform.openai.com/account/usage). > > <img width="487" alt="Scalene advanced options" src="https://user-images.githubusercontent.com/1612723/211639253-ec926b38-3efe-4a20-8514-e10dde94ec01.png"> Once you've entered your OpenAI key (see above), click on the lightning bolt (⚡) beside any line or the explosion (💥) for an entire region of code to generate a proposed optimization. Click on a proposed optimization to copy it to the clipboard. <img width="571" alt="example proposed optimization" src="https://user-images.githubusercontent.com/1612723/211639968-37cf793f-3290-43d1-9282-79e579558388.png"> You can click as many times as you like on the lightning bolt or explosion, and it will generate different suggested optimizations. Your mileage may vary, but in some cases, the suggestions are quite impressive (e.g., order-of-magnitude improvements). ### Quick Start #### Installing Scalene: ```console python3 -m pip install -U scalene ``` or ```console conda install -c conda-forge scalene ``` #### Using Scalene: After installing Scalene, you can use Scalene at the command line, or as a Visual Studio Code extension. <details> <summary> Using the Scalene VS Code Extension: </summary> First, install <a href="https://marketplace.visualstudio.com/items?itemName=EmeryBerger.scalene">the Scalene extension from the VS Code Marketplace</a> or by searching for it within VS Code by typing Command-Shift-X (Mac) or Ctrl-Shift-X (Windows). Once that's installed, click Command-Shift-P or Ctrl-Shift-P to open the <a href="https://code.visualstudio.com/docs/getstarted/userinterface">Command Palette</a>. Then select <b>"Scalene: AI-powered profiling..."</b> (you can start typing Scalene and it will pop up if it's installed). Run that and, assuming your code runs for at least a second, a Scalene profile will appear in a webview. <img width="734" alt="Screenshot 2023-09-20 at 7 09 06 PM" src="https://github.com/plasma-umass/scalene/assets/1612723/7e78e3d2-e649-4f02-86fd-0da2a259a1a4"> </details> <details> <summary> Commonly used command-line options: </summary> ```console scalene your_prog.py # full profile (outputs to web interface) python3 -m scalene your_prog.py # equivalent alternative scalene --cli your_prog.py # use the command-line only (no web interface) scalene --cpu your_prog.py # only profile CPU scalene --cpu --gpu your_prog.py # only profile CPU and GPU scalene --cpu --gpu --memory your_prog.py # profile everything (same as no options) scalene --reduced-profile your_prog.py # only profile lines with significant usage scalene --profile-interval 5.0 your_prog.py # output a new profile every five seconds scalene (Scalene options) --- your_prog.py (...) # use --- to tell Scalene to ignore options after that point scalene --help # lists all options ``` </details> <details> <summary> Using Scalene programmatically in your code: </summary> Invoke using `scalene` as above and then: ```Python from scalene import scalene_profiler # Turn profiling on scalene_profiler.start() # your code # Turn profiling off scalene_profiler.stop() ``` ```Python from scalene.scalene_profiler import enable_profiling with enable_profiling(): # do something ``` </details> <details> <summary> Using Scalene to profile only specific functions via <code>@profile</code>: </summary> Just preface any functions you want to profile with the `@profile` decorator and run it with Scalene: ```Python # do not import profile! @profile def slow_function(): import time time.sleep(3) ``` </details> #### Web-based GUI Scalene has both a CLI and a web-based GUI [(demo here)](http://plasma-umass.org/scalene-gui/). By default, once Scalene has profiled your program, it will open a tab in a web browser with an interactive user interface (all processing is done locally). Hover over bars to see breakdowns of CPU and memory consumption, and click on underlined column headers to sort the columns. The generated file `profile.html` is self-contained and can be saved for later use. [](https://raw.githubusercontent.com/plasma-umass/scalene/master/docs/scalene-gui-example-full.png) ## Scalene Overview ### Scalene talk (PyCon US 2021) [This talk](https://youtu.be/5iEf-_7mM1k) presented at PyCon 2021 walks through Scalene's advantages and how to use it to debug the performance of an application (and provides some technical details on its internals). We highly recommend watching this video! [](https://youtu.be/5iEf-_7mM1k "Scalene presentation at PyCon 2021") ### Fast and Accurate - Scalene is **_fast_**. It uses sampling instead of instrumentation or relying on Python's tracing facilities. Its overhead is typically no more than 10-20% (and often less). - Scalene is **accurate**. We tested CPU profiler accuracy and found that Scalene is among the most accurate profilers, correctly measuring time taken.  - Scalene performs profiling **_at the line level_** _and_ **_per function_**, pointing to the functions and the specific lines of code responsible for the execution time in your program. ### CPU profiling - Scalene **separates out time spent in Python from time in native code** (including libraries). Most Python programmers aren't going to optimize the performance of native code (which is usually either in the Python implementation or external libraries), so this helps developers focus their optimization efforts on the code they can actually improve. - Scalene **highlights hotspots** (code accounting for significant percentages of CPU time or memory allocation) in red, making them even easier to spot. - Scalene also separates out **system time**, making it easy to find I/O bottlenecks. ### GPU profiling - Scalene reports **GPU time** (currently limited to NVIDIA-based systems). ### Memory profiling - Scalene **profiles memory usage**. In addition to tracking CPU usage, Scalene also points to the specific lines of code responsible for memory growth. It accomplishes this via an included specialized memory allocator. - Scalene separates out the percentage of **memory consumed by Python code vs. native code**. - Scalene produces **_per-line_ memory profiles**. - Scalene **identifies lines with likely memory leaks**. - Scalene **profiles _copying volume_**, making it easy to spot inadvertent copying, especially due to crossing Python/library boundaries (e.g., accidentally converting `numpy` arrays into Python arrays, and vice versa). ### Other features - Scalene can produce **reduced profiles** (via `--reduced-profile`) that only report lines that consume more than 1% of CPU or perform at least 100 allocations. - Scalene supports `@profile` decorators to profile only specific functions. - When Scalene is profiling a program launched in the background (via `&`), you can **suspend and resume profiling**. # Comparison to Other Profilers ## Performance and Features Below is a table comparing the **performance and features** of various profilers to Scalene.  - **Slowdown**: the slowdown when running a benchmark from the Pyperformance suite. Green means less than 2x overhead. Scalene's overhead is just a 35% slowdown. Scalene has all of the following features, many of which only Scalene supports: - **Lines or functions**: does the profiler report information only for entire functions, or for every line -- Scalene does both. - **Unmodified Code**: works on unmodified code. - **Threads**: supports Python threads. - **Multiprocessing**: supports use of the `multiprocessing` library -- _Scalene only_ - **Python vs. C time**: breaks out time spent in Python vs. native code (e.g., libraries) -- _Scalene only_ - **System time**: breaks out system time (e.g., sleeping or performing I/O) -- _Scalene only_ - **Profiles memory**: reports memory consumption per line / function - **GPU**: reports time spent on an NVIDIA GPU (if present) -- _Scalene only_ - **Memory trends**: reports memory use over time per line / function -- _Scalene only_ - **Copy volume**: reports megabytes being copied per second -- _Scalene only_ - **Detects leaks**: automatically pinpoints lines responsible for likely memory leaks -- _Scalene only_ ## Output If you include the `--cli` option, Scalene prints annotated source code for the program being profiled (as text, JSON (`--json`), or HTML (`--html`)) and any modules it uses in the same directory or subdirectories (you can optionally have it `--profile-all` and only include files with at least a `--cpu-percent-threshold` of time). Here is a snippet from `pystone.py`.  * **Memory usage at the top**: Visualized by "sparklines", memory consumption over the runtime of the profiled code. * **"Time Python"**: How much time was spent in Python code. * **"native"**: How much time was spent in non-Python code (e.g., libraries written in C/C++). * **"system"**: How much time was spent in the system (e.g., I/O). * **"GPU"**: (not shown here) How much time spent on the GPU, if your system has an NVIDIA GPU installed. * **"Memory Python"**: How much of the memory allocation happened on the Python side of the code, as opposed to in non-Python code (e.g., libraries written in C/C++). * **"net"**: Positive net memory numbers indicate total memory allocation in megabytes; negative net memory numbers indicate memory reclamation. * **"timeline / %"**: Visualized by "sparklines", memory consumption generated by this line over the program runtime, and the percentages of total memory activity this line represents. * **"Copy (MB/s)"**: The amount of megabytes being copied per second (see "About Scalene"). ## Scalene The following command runs Scalene on a provided example program. ```console scalene test/testme.py ``` <details> <summary> Click to see all Scalene's options (available by running with <code>--help</code>) </summary> ```console % scalene --help usage: scalene [-h] [--outfile OUTFILE] [--html] [--reduced-profile] [--profile-interval PROFILE_INTERVAL] [--cpu-only] [--profile-all] [--profile-only PROFILE_ONLY] [--use-virtual-time] [--cpu-percent-threshold CPU_PERCENT_THRESHOLD] [--cpu-sampling-rate CPU_SAMPLING_RATE] [--malloc-threshold MALLOC_THRESHOLD] Scalene: a high-precision CPU and memory profiler. https://github.com/plasma-umass/scalene command-line: % scalene [options] yourprogram.py or % python3 -m scalene [options] yourprogram.py in Jupyter, line mode: %scrun [options] statement in Jupyter, cell mode: %%scalene [options] code... code... optional arguments: -h, --help show this help message and exit --outfile OUTFILE file to hold profiler output (default: stdout) --html output as HTML (default: text) --reduced-profile generate a reduced profile, with non-zero lines only (default: False) --profile-interval PROFILE_INTERVAL output profiles every so many seconds (default: inf) --cpu-only only profile CPU time (default: profile CPU, memory, and copying) --profile-all profile all executed code, not just the target program (default: only the target program) --profile-only PROFILE_ONLY profile only code in filenames that contain the given strings, separated by commas (default: no restrictions) --use-virtual-time measure only CPU time, not time spent in I/O or blocking (default: False) --cpu-percent-threshold CPU_PERCENT_THRESHOLD only report profiles with at least this percent of CPU time (default: 1%) --cpu-sampling-rate CPU_SAMPLING_RATE CPU sampling rate (default: every 0.01s) --malloc-threshold MALLOC_THRESHOLD only report profiles with at least this many allocations (default: 100) When running Scalene in the background, you can suspend/resume profiling for the process ID that Scalene reports. For example: % python3 -m scalene [options] yourprogram.py & Scalene now profiling process 12345 to suspend profiling: python3 -m scalene.profile --off --pid 12345 to resume profiling: python3 -m scalene.profile --on --pid 12345 ``` </details> ### Scalene with Jupyter <details> <summary> Instructions for installing and using Scalene with Jupyter notebooks </summary> [This notebook](https://nbviewer.jupyter.org/github/plasma-umass/scalene/blob/master/docs/scalene-demo.ipynb) illustrates the use of Scalene in Jupyter. Installation: ```console !pip install scalene %load_ext scalene ``` Line mode: ```console %scrun [options] statement ``` Cell mode: ```console %%scalene [options] code... code... ``` </details> ## Installation <details open> <summary>Using <code>pip</code> (Mac OS X, Linux, Windows, and WSL2)</summary> Scalene is distributed as a `pip` package and works on Mac OS X, Linux (including Ubuntu in [Windows WSL2](https://docs.microsoft.com/en-us/windows/wsl/wsl2-index)) and (with limitations) Windows platforms. > **Note** > > The Windows version currently only supports CPU and GPU profiling, but not memory or copy profiling. > You can install it as follows: ```console % pip install -U scalene ``` or ```console % python3 -m pip install -U scalene ``` You may need to install some packages first. See https://stackoverflow.com/a/19344978/4954434 for full instructions for all Linux flavors. For Ubuntu/Debian: ```console % sudo apt install git python3-all-dev ``` </details> <details> <summary>Using <code>conda</code> (Mac OS X, Linux, Windows, and WSL2)</summary> ```console % conda install -c conda-forge scalene ``` Scalene is distributed as a `conda` package and works on Mac OS X, Linux (including Ubuntu in [Windows WSL2](https://docs.microsoft.com/en-us/windows/wsl/wsl2-index)) and (with limitations) Windows platforms. > **Note** > > The Windows version currently only supports CPU and GPU profiling, but not memory or copy profiling. > </details> <details> <summary>On ArchLinux</summary> You can install Scalene on Arch Linux via the [AUR package](https://aur.archlinux.org/packages/python-scalene-git/). Use your favorite AUR helper, or manually download the `PKGBUILD` and run `makepkg -cirs` to build. Note that this will place `libscalene.so` in `/usr/lib`; modify the below usage instructions accordingly. </details> # Frequently Asked Questions <details> <summary> Can I use Scalene with PyTest? </summary> **A:** Yes! You can run it as follows (for example): `python3 -m scalene --- -m pytest your_test.py` </details> <details> <summary> Is there any way to get shorter profiles or do more targeted profiling? </summary> **A:** Yes! There are several options: 1. Use `--reduced-profile` to include only lines and files with memory/CPU/GPU activity. 2. Use `--profile-only` to include only filenames containing specific strings (as in, `--profile-only foo,bar,baz`). 3. Decorate functions of interest with `@profile` to have Scalene report _only_ those functions. 4. Turn profiling on and off programmatically by importing Scalene profiler (`from scalene import scalene_profiler`) and then turning profiling on and off via `scalene_profiler.start()` and `scalene_profiler.stop()`. By default, Scalene runs with profiling on, so to delay profiling until desired, use the `--off` command-line option (`python3 -m scalene --off yourprogram.py`). </details> <details> <summary> How do I run Scalene in PyCharm? </summary> **A:** In PyCharm, you can run Scalene at the command line by opening the terminal at the bottom of the IDE and running a Scalene command (e.g., `python -m scalene <your program>`). Use the options `--cli`, `--html`, and `--outfile <your output.html>` to generate an HTML file that you can then view in the IDE. </details> <details> <summary> How do I use Scalene with Django? </summary> **A:** Pass in the `--noreload` option (see https://github.com/plasma-umass/scalene/issues/178). </details> <details> <summary> Does Scalene work with gevent/Greenlets? </summary> **A:** Yes! Put the following code in the beginning of your program, or modify the call to `monkey.patch_all` as below: ```python from gevent import monkey monkey.patch_all(thread=False) ``` </details> <details> <summary> How do I use Scalene with PyTorch on the Mac? </summary> **A:** Scalene works with PyTorch version 1.5.1 on Mac OS X. There's a bug in newer versions of PyTorch (https://github.com/pytorch/pytorch/issues/57185) that interferes with Scalene (discussion here: https://github.com/plasma-umass/scalene/issues/110), but only on Macs. </details> # Technical Information For details about how Scalene works, please see the following paper, which won the Jay Lepreau Best Paper Award at [OSDI 2023](https://www.usenix.org/conference/osdi23/presentation/berger): [Triangulating Python Performance Issues with Scalene](https://arxiv.org/pdf/2212.07597). (Note that this paper does not include information about the AI-driven proposed optimizations.) <details> <summary> To cite Scalene in an academic paper, please use the following: </summary> ```latex @inproceedings{288540, author = {Emery D. Berger and Sam Stern and Juan Altmayer Pizzorno}, title = {Triangulating Python Performance Issues with {S}calene}, booktitle = {{17th USENIX Symposium on Operating Systems Design and Implementation (OSDI 23)}}, year = {2023}, isbn = {978-1-939133-34-2}, address = {Boston, MA}, pages = {51--64}, url = {https://www.usenix.org/conference/osdi23/presentation/berger}, publisher = {USENIX Association}, month = jul } ``` </details> # Success Stories If you use Scalene to successfully debug a performance problem, please [add a comment to this issue](https://github.com/plasma-umass/scalene/issues/58)! # Acknowledgements Logo created by [Sophia Berger](https://www.linkedin.com/in/sophia-berger/). This material is based upon work supported by the National Science Foundation under Grant No. 1955610. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation. ", Assign "at most 3 tags" to the expected json: {"id":"2215","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"