1) Flat View Caching is not efficient. The typical Flat View is (probably) unfiltered, and a search that returns all items runs faster than reading the same results from a cache. At least on my system.
So, I'm inclined to remove the "Cache Flat View Contents" option. Any objections?
2) The bigger the cache the slower it is compared to a live search. At least on my system. And it takes space on the disk, and, worse, it may trigger lots of wild-jumping head movements depending on the sort order of the cached items.
This calls for some limit. User-defined, of course. So, just FYI, the next version will have an additional field where you can set a limit (my tests suggest "1000 items" -- any larger lists should NOT be cached. Caching was always meant to be applied to meager search results that have been harvested over large search areas. This cache limit will force this idea a little. (A smarter way would be a ratio, e.g. cache only results where 1/10 or less of all scanned items were matches, but this will be harder to explain/understand.)
On Search Results Caching.
-
admin
- Site Admin
- Posts: 67270
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
XYplorer Beta Club