py-pal 0.2.2

Estimate Asymptotic Runtime Complexity from Bytecode executions

Python Performance Analysis Library or py-pal is a bytecode profiling toolkit.

Installation

This project requires CPython to run. Install Python >= 3.7, then install py-pal by running:

pip install py-pal

Documentation

TBA

Overview

Calling py-pal as module with

python -m py_pal file.py

or

pypal file.py

Measure specific functions using the decorator:

from py_pal.core import profile

@profile
def test():
    pass

Using the context manager:

from py_pal.estimator import AllArgumentEstimator
from py_pal.tracer import Tracer

with Tracer() as t:
    pass

estimator = AllArgumentEstimator(t)
res = estimator.export()

# Do something with the resulting DataFrame
print(res)

Using the API:

from py_pal.estimator import AllArgumentEstimator
from py_pal.tracer import Tracer


t = Tracer()
t.trace()

# Your function
pass

t.stop()
estimator = AllArgumentEstimator(t)
res = estimator.export()

# Do something with the resulting DataFrame
print(res)

Modes

Profiling and Performance Testing

Restrictions

The Tracing process does not work for multi-threaded code.

Tracing processes

Development

To run the all tests run:

pip install -r dev-requirements.txt

pytest tests tests_cython

FAQ

Why not use a standard profiler?

Using absolute timing data vs synthetic timing data using opcodes.

What’s New in Py-PAL 0.2.1

Refactoring

The estimator module was refactored which introduces a slight change to the API. Classes inheriting from Estimator now only specify how to transform the collected data with respect to the arguments of the function.

Instead of ComplexityEstimator you should use the AllArgumentEstimator class. Additionally there is the SeparateArgumentEstimator which is experimental.

What’s New in Py-PAL 0.1.6

More accurate Data Collection

The Tracer is enhanced by measuring builtin function calls with AdvancedOpcodeMetric.

Opcodes resembling a function call .e.g FUNCTION_CALL are filtered for built in function calls. If the called function is found in the complexity mapping a synthetic Opcode weight gets assigned. A builtin function call is evaluated using its argument and a pre-defined runtime complexity e.g. O(n log n) for sort().

• The feature is enabled by default

• The calculation produces a performance overhead and can be disabled by providing a OpcodeMetric instance to the Tracer

• The AdvancedOpcodeMetric instance assigned to the Tracer provides statistics about how many builtin function calls were observed and how many were found in the complexity map

Bugfixes

• Cleaning data after normalization introduced wrong data points