Summary
Currently, autobpm processes tracks sequentially, which can be slow for large libraries. See implementation here.
Motivation
The current sequential approach does not fully utilize modern multi-core CPUs or high-throughput storage. By adding concurrency, autobpm could process multiple tracks simultaneously, reducing overall runtime for large libraries.
References
Additional Notes
This seems like a straightforward optimization and could significantly improve processing time for users with large libraries.
Summary
Currently,
autobpmprocesses tracks sequentially, which can be slow for large libraries. See implementation here.Motivation
The current sequential approach does not fully utilize modern multi-core CPUs or high-throughput storage. By adding concurrency,
autobpmcould process multiple tracks simultaneously, reducing overall runtime for large libraries.References
Additional Notes
This seems like a straightforward optimization and could significantly improve processing time for users with large libraries.