Cache "successfuly" fails to be applied when more than 65 GiByte is configured
Posted: Fri Dec 08, 2023 11:41 pm
Windows OS: 11 23H2
Hardware Information
Memory: 128 GiByte
PrimoCache Version: 4.3.0 Personal
Problem Description:
When trying to assign 66 GiByte or more L1 Cache to a cache task, PrimoCache will say it successfuly applied the Cache while it actually didn't and assigned nothing.
Until 65 GiByte it will work just fine.
On the left you can see the RAM Usage as shown in the Win11 Task Manager. With 65 GiByte it'll show it's actually gets allocated. Primo Cache will also show the the Unused Cache (L1) correctly.
(Note that the screenshots show the Configuration Dialog after I already applied the config by hitting "OK", not before doing so.)
With 66 GiByte or more the RAM Usage will try to assign some memory and then drop back to 0 - even though PrimoCache's Dialog will say it assigned it successfuly.
Unused Cache (L1) will also show just "0".
Benchmarking the drive using winsat disk -drive X: will also prove there is no caching applied.
Hardware Information
Memory: 128 GiByte
PrimoCache Version: 4.3.0 Personal
Problem Description:
When trying to assign 66 GiByte or more L1 Cache to a cache task, PrimoCache will say it successfuly applied the Cache while it actually didn't and assigned nothing.
Until 65 GiByte it will work just fine.
On the left you can see the RAM Usage as shown in the Win11 Task Manager. With 65 GiByte it'll show it's actually gets allocated. Primo Cache will also show the the Unused Cache (L1) correctly.
(Note that the screenshots show the Configuration Dialog after I already applied the config by hitting "OK", not before doing so.)
With 66 GiByte or more the RAM Usage will try to assign some memory and then drop back to 0 - even though PrimoCache's Dialog will say it assigned it successfuly.
Unused Cache (L1) will also show just "0".
Benchmarking the drive using winsat disk -drive X: will also prove there is no caching applied.