One thing I've noticed is that subsequent scans with SQLite, even if they're clear/rescans, are much faster than the first scan. I'm guessing that this may be because when a 'clear' is done, the SQLite database file remains the same size (actually, MySQL InnoDB databases operate the same way), so the SQLite library file itself doesn't need to grow when rebuilding the database.
If that's the case, I wonder if within SqueezeCenter you can tell the SQLite routines to expand the database file in N kB chunks. This could potentially speed up new & changed rescans when adding new tracks by requiring the file to be expanded less often. I have both 7.4 Trunk and the 7.4 SQLite branch running simultaneously on my server now, so I can do some better head to head testing if the scanning performance. I'll post some new test results when I'm more certain that things are as equal as I can get them. -- JJZolx Jim ------------------------------------------------------------------------ JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this thread: http://forums.slimdevices.com/showthread.php?t=63346 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
