Thank You for your continued support and contributions!
dircache+db_cache enabled: 1m 30s (!)
Quotedircache+db_cache enabled: 1m 30s (!)i'd say this needs investigated they are probably fighting each other
yeah, maybe. This is what causes the additional delay: ...There's already a dircache_wait() before that though.
Quote from: chris_s on January 17, 2023, 02:48:39 AMyeah, maybe. This is what causes the additional delay: ...There's already a dircache_wait() before that though.yeah I was looking at that last night it looks to only be checking for deleted entries maybe we could move that out get the list up and check for validity once the user selects it if the scan isn't finished in a separate thread@chris_s whats it do if you just disable the dircache part with #if 0 and let it use file_exists()?
In my personal experience, resulting negative effects are negligible. Tagcache_fill_tags won't work anymore but that seems like a good tradeoff, except, possibly, for the fact that a WPS skin that has an integrated playlist viewer can't display upcoming metadata anymore.
Quote from: chris_s on January 17, 2023, 05:05:32 PMIn my personal experience, resulting negative effects are negligible. Tagcache_fill_tags won't work anymore but that seems like a good tradeoff, except, possibly, for the fact that a WPS skin that has an integrated playlist viewer can't display upcoming metadata anymore.Would that affect the Next Track display that shows a track name and artist in my WPS?
Page created in 0.068 seconds with 16 queries.