Replies: 1 comment 2 replies
-
I doubt that this would lead to any substantial improvements: Compute-heavy tasks in beets (converting, replaygain, etc) should all be performed by external programs/libraries which should usually be written in compiled languages. In many other cases, beets is in fact IO-bound due to waiting for web services to fetch data. Another long-standing bottleneck is inefficient database access patterns, but solving that requires architectural changes (in fact, see #4362, which I should really come back to review), and another interpreter is probably not going to cut it. That being said, I don't know GraalVM at all, so by all means, feel free to try this! (Another reason not to do this would be that GraalVM is certainly not going to be as ubiquitous as CPython.) |
Beta Was this translation helpful? Give feedback.
-
Beets is still fantastic, but I would love for it to improve in terms of speed. Would it be worth looking into compiling using GraalVM?
I'm not savvy enough with compiler stuff to judge this properly. Would this be a nice thing to look into?
Beta Was this translation helpful? Give feedback.
All reactions