Cache "successfuly" fails to be applied when more than 65 GiByte is configured

[Kalex]

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.)

65GB.gif (159.79 KiB) Viewed 2287 times

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.

66GB.gif (163.44 KiB) Viewed 2287 times

[Support]

It seems that PrimoCache failed to allocate memory as L1 cache. Because L2 cache can start, PrimoCache will still create the cache task. That's why you see L1 is 0 but cache task is created successfully.

Is your system a NUMA architecture? If yes, you need PrimoCache Pro and enable NUMA-aware. See
https://kb.romexsoftware.com/en-us/2-pr ... numa-aware

[Kalex]

Nope, not a NUMA.

Why does it fail to allocate more memory when there is still plenty of it available?

[Support]

PrimoCache will log an event when it is unable to obtain the required amount of RAM. Could you follow the guidance in the link below to check if there are any events with source "FancyCcV"? If there are, please export these events and send them to [email protected].

Also please follow the instructions in the link below to send us your system information for our reference.
https://kb.romexsoftware.com/en-us/3-ge ... leshooting

Thank you.

PS. PrimoCache uses Windows functions to obtain RAM. The most likely reason for this situation is due to the limited amount of memory per node in the numa architecture. So I asked before whether your computer was a Numa architecture computer.