PrimoCache L1 cache size and block size
PrimoCache L1 cache size and block size
Hi, i have 4gb ram memory what's the best primocache L1 cache size and block size for me.Thanks.
-
- Level SS
- Posts: 477
- Joined: Wed Oct 06, 2010 11:10 pm
Re: PrimoCache L1 cache size and block size
Welcome to the forums Dusanka,
4GB memory may not be enough for PrimoCache to offer significant benefits over Windows' own file caching (especially as memory allocated to PrimoCache will not be available for other applications). PrimoCache can use an SSD to cache a hard disk also (L2 caching) and you might want to look at using this feature instead (it won't be of any use if you already store programs and data on an SSD).
4GB memory may not be enough for PrimoCache to offer significant benefits over Windows' own file caching (especially as memory allocated to PrimoCache will not be available for other applications). PrimoCache can use an SSD to cache a hard disk also (L2 caching) and you might want to look at using this feature instead (it won't be of any use if you already store programs and data on an SSD).
Re: PrimoCache L1 cache size and block size
I've 2GB of RAM.
My L1 is 256KB. Blocks is 16KB and L2 is 20GB on SSD.
R/W strategy, delay: 10s.
If your OS is 32bits use the max of invisible memory...
My L1 is 256KB. Blocks is 16KB and L2 is 20GB on SSD.
R/W strategy, delay: 10s.
If your OS is 32bits use the max of invisible memory...
Re: PrimoCache L1 cache size and block size
I have 160gb small hdd not ssd, windows 8.1 pro x64 what is the best settings for me.InquiringMind wrote:Welcome to the forums Dusanka,
4GB memory may not be enough for PrimoCache to offer significant benefits over Windows' own file caching (especially as memory allocated to PrimoCache will not be available for other applications). PrimoCache can use an SSD to cache a hard disk also (L2 caching) and you might want to look at using this feature instead (it won't be of any use if you already store programs and data on an SSD).
-
- Level SS
- Posts: 477
- Joined: Wed Oct 06, 2010 11:10 pm
Re: PrimoCache L1 cache size and block size
I would suggest monitoring process memory usage (using Process Explorer or Process Hacker) to determine maximum RAM usage for your system. Subtract this from your 4GB, subtract another 512MB-1GB to give a safety margin and that should give you the amount you can allocate to PrimoCache L1 without hampering application performance. If you have no SSD, then L2 caching is a non-issue.
With 4GB, I doubt you'd be able to allocate more than 2GB to PrimoCache L1 and that only if you are running undemanding applications. In such a situation, I'd be inclined to leave PrimoCache alone and stick with Windows' own file caching (this will use all available memory on your system, but will also give up memory to applications that need it - unlike PrimoCache where memory allocated to L1 cannot be used elsewhere).
With 4GB, I doubt you'd be able to allocate more than 2GB to PrimoCache L1 and that only if you are running undemanding applications. In such a situation, I'd be inclined to leave PrimoCache alone and stick with Windows' own file caching (this will use all available memory on your system, but will also give up memory to applications that need it - unlike PrimoCache where memory allocated to L1 cannot be used elsewhere).
Re: PrimoCache L1 cache size and block size
In process hacker do i need to look in peak commit charge or in physical memory current for maximum ram usage.InquiringMind wrote:I would suggest monitoring process memory usage (using Process Explorer or Process Hacker) to determine maximum RAM usage for your system. Subtract this from your 4GB, subtract another 512MB-1GB to give a safety margin and that should give you the amount you can allocate to PrimoCache L1 without hampering application performance. If you have no SSD, then L2 caching is a non-issue.
With 4GB, I doubt you'd be able to allocate more than 2GB to PrimoCache L1 and that only if you are running undemanding applications. In such a situation, I'd be inclined to leave PrimoCache alone and stick with Windows' own file caching (this will use all available memory on your system, but will also give up memory to applications that need it - unlike PrimoCache where memory allocated to L1 cannot be used elsewhere).
-
- Level SS
- Posts: 477
- Joined: Wed Oct 06, 2010 11:10 pm
Re: PrimoCache L1 cache size and block size
In Process Hacker, System Information/Commit Charge/Peak is the best indicator of maximum ram usage.