I am currently running Logitech Media Server (v7.7.3, 1336728576) on a
Debian/Unstable box, and starting the server, or rescanning the library
takes just over 2 hours. I have ~20k tracks, and a bunch of erland's
plugins installed.

The slow part seems to be when cache/persist.db gets (very slowly)
copied into cache/persist.db-wal. My persist.db is 187M, and it copies
around 20KB/sec. During this entire time one CPU is pegged at 100%.

strace shows kazillions of lines like:
lseek(21, 61262992, SEEK_SET)           = 61262992
read(21, 
"\n\0\0\0\25\0\315\0\3=\3d\3\213\3\262\3\331\0\315\0\364\1\33\1B\1i\1\220\1\267"...,
 1024) = 1024
lseek(20, 176803840, SEEK_SET)          = 176803840
read(20, 
"\2\0\0\0\2\2y\0\0\2\177\360\3C\2y\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024) = 
1024
lseek(21, 35200280, SEEK_SET)           = 35200280
read(21, 
"\2\0\0\0\4\0\233\0\0\2\177\357\0\233\2C\1Y\3\26\0x\0\0\0\0\0\0\0\0\0\0"..., 
1024) = 1024
lseek(20, 155569152, SEEK_SET)          = 155569152
read(20, "\2\0\0\0\4\0X\0\0\2K;\0X\1B\2,\3\26\2\206\0\0\0\0\0\0\0\0\0\0"..., 
1024) = 1024
lseek(21, 62461880, SEEK_SET)           = 62461880
write(21, 
"\0\1\355\224\0\0\0\0iP\327\35\3634\304\357$\270\221\301\213\372\30\262", 24) = 
24
lseek(21, 62461904, SEEK_SET)           = 62461904
write(21, 
"\n\0\0\0\6\0\232\0\1+\1\274\2M\2\336\3o\0\232\3\223\0\0\0\0\0\0\0\0\0\0"..., 
1024) = 1024
lseek(21, 56047096, SEEK_SET)           = 56047096
read(21, 
"\2\0\0\0\3\1B\0\0\2>\200\1B\2,\3\26\3\26\0\340\0\0\0\0\0\0\0\0\0\0"..., 1024) 
= 1024

file id 20 is /var/tmp/squeezeboxserver/cache/persist.db, and 21 is
/var/tmp/squeezeboxserver/cache/persist.db-wal. This mirrors what an ls
of cache/persist* shows.

I tried moving the cache directory into a RAM disk to eliminate disk
issues, and it did not speed it up at all. Once it is up and running
performance is good, but the startup and rescan is a killer.

Anyone have any idea how to speed this up? Is MySQL still a viable
option given I rely on erland's plugins? I was thinking of tweaking
/usr/share/perl5/Slim/Utils/SQLiteHelper.pm to seriously increase
cache_size, or maybe just set page_size to a larger value (like 16k).

Anyone else see anything like this?

Thanks,
   Omen

-- 
Confidence is the feeling you have before you understand the situation.
_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/discuss

Reply via email to