mherger wrote: > > From my poor memory I remember SQLite caches the index, not the data > itself. >
actually, it does cache the data: SQLite docs wrote: > > maximum number of database disk pages that SQLite will hold in memory > mherger wrote: > > Therefore assigning a lot of data to the artwork cache might do no harm > in most cases, but promise more than it delivers? > Verifying that caching artworkdb works is fairly simple: - LMS process size grows larger the more covers have been displayed - my artworkdb is on a HDD, so I can literally hear that it's accessed the first time a specific cover is displayed, and not on subsequent renderings > > trackstat > Would be interesting to know which tweak makes the difference, or > whether it's really the combination of them all. > Pretty confident that'll overwhelmingly be the new indices. However, this may actually be a scenario where multi-threading could be used, so mamema could check if more than one core is utilized the next time a trackstat refresh runs. I've also released a new version which adds a dropExtraTrackStatIndices API command, which could be helpful if anyone really wants to perform a detailed analysis. 'Various SW' (https://www.nexus0.net/pub/sw/): Web Interface | TUI | Playlist Editor / Generator | Music Classification | Similar Music | Announce | EventTrigger | Chiptunes | LMSlib2go | ... 'Various HowTos' (https://www.nexus0.net/pub/documents/LMS/): build a self-contained LMS | Bluetooth/ALSA | Control LMS with any device | ... ------------------------------------------------------------------------ Roland0's Profile: http://forums.slimdevices.com/member.php?userid=56808 View this thread: http://forums.slimdevices.com/showthread.php?t=114067 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
