Slow startup and indexing compared to Clementine
-
Hey there,
I love this player and for years I've been trying to find an alternative but 'nothing compares'.
Now for my issue. I've been checking in with this project last couple of years but on different computers running different flavors of Linux, using SMB or NFS, Strawberry is noticeably slower.
It takes much longer for Strawberry to start up. It takes a bit longer to index, or at least it takes more time before I start seeing the percentage stage of the indexing.
I've tried setting big cache sizes and tinkering with other settings to no avail. Feels like I might be missing something?
Strawberry 1.2.13
Linux 6.12.49 #1-NixOS
~13k FLAC files on local network SSD raid -
I was looking at some profiling outputs and Strawberry does so much more on startup. (click to see interactive svg)
I tried making callgrind profiles but couldn't get it working. Clementine starts up instant where strawberry takes seconds.
-
@henk
The startup could be slower because of the way Strawberry initializes objects earlier at startup, I fixed bugs and even rewrote many parts of the code where Clementine did things unsafe thread-wise, ie.: reading and modifying GUI things from a another thread than the main thread, which will be faster, but it's broken code, and just a coincidence that it doesn't crash.
One thing you can try is to turn off "Grey out unavailable songs in playlist on startup" in Settings / Playlist, this feature will lag the startup significantly.Strawberry has a little delay at the beginning of the scan, it's because it iterates through the directories to find the number of files for the progress % status.
Clementine calculates the progress only based on the number of directories, which makes the progress inaccurate, and often stuck on 97-99% for a long time.
Other than that, then scan speed should be pretty much identical.
