[RELEASE] Texture Cache Maintenance utility
(2015-09-04, 13:50)denywinarto Wrote: all clients will use pxe boot and thus the thumbnails should not need synchronizing

Why won't they need synchronizing? Each client should still be using their own independent Textures13.db and Thumbnails folders - if you're thinking of sharing a single Thumbnails folder between all your clients then don't, as that doesn't work.

(2015-09-04, 13:50)denywinarto Wrote: will this script or mklocal.py help improve the speed for my case?

As each of your clients should still be using their own texture cache, pre-loading the texture cache is still a good idea and will improve GUI performance by avoiding the delays that result when artwork needs to be cached.

mklocal.py is useful for converting remote artwork to local artwork and only needs to be run against one client if you are sharing the library (I assume you mean MySQL, and not sharing the SQLite databases, which would be a bad idea).

Amongst other things, the use of local artwork will result in less delays when artwork needs to be cached. Once you have converted remote artwork to local artwork, update the texture caches of all clients so that the new local artwork is cached.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply


Messages In This Thread
Crash on Gotham on OS X - by desepticon - 2014-05-29, 17:57
RE: [RELEASE] Texture Cache Maintenance utility - by Milhouse - 2015-09-04, 14:57
Cleaning - by AleisterHH - 2018-05-28, 22:03
RE: Cleaning - by Milhouse - 2018-05-28, 22:16
qax genre not updated - by Just-Me_A-User - 2018-06-12, 22:06
RE: qax genre not updated - by Milhouse - 2018-06-12, 23:40
Logout Mark Read Team Forum Stats Members Help
[RELEASE] Texture Cache Maintenance utility17