Page 1 of 1

Prefetch Inactive, even though selected. (v2.5.0)

Posted: Fri Sep 02, 2016 5:00 pm
by Mic
Seeing an issue here where my prefetch doesn't seem to be happening.

Setup I have is two tasks: a primary 1TB SSD system disk with a 4GB L1 cache only, and a secondary mechanical disk, with a separate (old) 128GB SSD as L2, and a separate 4GB L1 cache. Both cache tasks when viewed show "Prefetch: Inactive" in the main GUI, with the majority of the cache free (>1GB of L1 on both, and 111 of the 128GB on the L2)

Prefetch is enabled on both tasks, along with the option to fill the cache at windows start. From the looks of that though, this isn't happening. Any known issues there, or is there some way I can diagnose why these options don't seem to be taking effect? As noted in subject line, am running v2.5.0 - latest version at the time of posting ;)

Main UI:
Image

and the config (task #1 with both L1 and L2 displayed, relevant bits of #2 is the same)
Image

Re: Prefetch Inactive, even though selected. (v2.5.0)

Posted: Fri Sep 02, 2016 5:55 pm
by Jaga
Prefetch operates on a per-drive basis, not per-cache-task. Selecing the different drives will give you their prefetch status.

Prefetch requires that the information be flagged as previously loaded into the cache, and is only run at boot time. Sometimes it takes several boots to get the prefetch kicked off and loading information - normally it is far more active on the boot drive (C:) than other drives.

Try clicking on your C: drive after another boot or two and see how it looks. I also find the cache fills up and has a higher hitrate when I leave Windows 10 at the login screen for a minute or two, instead of logging in immediately.

Hope some of that helps.

Re: Prefetch Inactive, even though selected. (v2.5.0)

Posted: Fri Sep 02, 2016 6:45 pm
by Mic
Hrm.. Yup, just had another look at it now and then came back here to update and saw the above ;) Now seeing Prefetch: Done for C:, D: and the 'system reserved' partition... Kinda weird, but fair enough.