You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pedalboard is a Python library for working with audio. It has been active for ~3 years currently has roughly 100,000 downloads per month across various operating systems and Python versions.
How large is each release?
Each release is currently roughly 275MiB. The project is nearly entirely one blob of compiled C++, and is released for a huge matrix of Python versions, operating systems, and CPU architectures.
There is a plan to reduce the size of each Pedalboard release:
Reducing the frequency of releases to once a month (at most frequent)
Removing some pre-computed data tables (~2MB/wheel, or ~140MB per release) that could instead be instantiated lazily
Pruning unused binary data and unused C++ classes from the release via bloaty
Pruning the build matrix to only support one Python version for less-commonly-used platforms (i.e.: only support Python 3.10 for musllinux aarch64)
Releasing arm64 and x86 wheels for macOS, but removing the universal wheels
The goal is to get each release down to <50MB in total size, which would allow ~8 more years of releases with the proposed 5GB limit increase.
However, even with this plan in place, new releases will not be possible without an increase in the limit.
How frequently do you make a release?
Roughly 2-3x a month.
Code of Conduct
I agree to follow the PSF Code of Conduct
The text was updated successfully, but these errors were encountered:
Project URL
https://pypi.org/project/pedalboard/
Does this project already exist?
New limit
15
Update issue title
Which indexes
PyPI
About the project
pedalboard
is a Python library for working with audio. It has been active for ~3 years currently has roughly 100,000 downloads per month across various operating systems and Python versions.How large is each release?
Each release is currently roughly 275MiB. The project is nearly entirely one blob of compiled C++, and is released for a huge matrix of Python versions, operating systems, and CPU architectures.
There is a plan to reduce the size of each Pedalboard release:
The goal is to get each release down to <50MB in total size, which would allow ~8 more years of releases with the proposed 5GB limit increase.
However, even with this plan in place, new releases will not be possible without an increase in the limit.
How frequently do you make a release?
Roughly 2-3x a month.
Code of Conduct
The text was updated successfully, but these errors were encountered: