Path format performance

[RollingStar]

I did some non scientific tests. Path formats indeed ate up performance.

Time to rethink path formats?

I tested it and feel good. Need to do more tests. I have a few hundred imports coming eventually™ and it should be a good chance to torture test this concept. After this initial test, I feel better about Python/some other system and worse about the current setup. However, forcing users to do it manually is a no-go, if my experience is an indication. pros incredibly readable: I can set up my paths like a regular python script and loosely follow PEP8 Python engineering is available. I can autofo…

I have a very precise renaming scheme that relied heavily on regex. Moving it over to python made it “conservatively, 2x faster” on my machine. You can see the code before and after at the link.

i’ve moved all my album fields to a single python inline call. is there something about inline that might cause poor performance invoking 10ish functions? 8ish of them are very basic 5 line string manipulation functions. is compile_inline the culprit? Edit: Or maybe commenting out aunique does it? Or the regex in the path formats?

Related (can also search github/here for ‘performance’, ‘path format’ etc)

Beets as a use case for (master) thesis

Hi, I’m in the process of choosing a project for my masters thesis (computer science + engineering). I have been using beets for a while and now I’m playing with the idea of beets as a use case for my thesis. The motivation being to contribute to beets in some way. I have some ideas as to what I could do. However, before I get too carried away, I would love to get some feedback from those involved: do you find beets as a suitable use case (research-able)? With the open nature of the project, …