Search found 477 matches
- Sun Sep 15, 2013 9:45 am
- Forum: Technical Support
- Topic: write cache not working with RamDisk Pro
- Replies: 17
- Views: 13347
Re: write cache not working with RamDisk Pro
My kernel is patched so my OS sees the entire 12GB of memory and uses it. I've read the thread discussing the patching, and things aren't likely to be so simple. While it is possible to increase the total amount of memory usable (up to the PAE limit of 64GB) by such patching, limits still exist on ...
- Sun Sep 15, 2013 12:32 am
- Forum: Technical Support
- Topic: Failed to format this volume to the level-2 storage!
- Replies: 9
- Views: 7426
Re: Failed to format this volume to the level-2 storage!
Pending an official response, does the SSD format normally and does partitioning it (and using PrimoCache to format one partition only) make any difference?
- Sun Sep 15, 2013 12:16 am
- Forum: Technical Support
- Topic: write cache not working with RamDisk Pro
- Replies: 17
- Views: 13347
Re: write cache not working with RamDisk Pro
If you're running a 32-bit OS, then there will be restrictions on smaller blocksizes depending on your cache settings (I need 16KB+ blocksize with a 7GB cache). That's because the reported "overhead" (which I presume is the indexing for the cache) uses conventional memory, so cannot exceed...
- Sat Sep 14, 2013 8:43 am
- Forum: Technical Support
- Topic: write cache not working with RamDisk Pro
- Replies: 17
- Views: 13347
Re: write cache not working with RamDisk Pro
Use the "custom" setting as suggested twice previously, and you should be able to set up the cache as you please. The other options (read and write) both restrict certain choices. The performance figures I posted in the Benchmarking PrimoCache thread were obtained with LFU-R. Write defer s...
- Sat Sep 14, 2013 8:38 am
- Forum: Technical Support
- Topic: cache vs ramdisk
- Replies: 3
- Views: 5406
Re: cache vs ramdisk
Simplest answer - a Ramdisk only contains data you put on it, so can only improve performance if you take the time to (a) identify files/folders used frequently and (b) copy them across to the ramdisk and make any configuration changes needed to ensure the ramdisk version is used (e.g. using links o...
- Wed Sep 11, 2013 3:58 pm
- Forum: Submit Suggestions
- Topic: Preload currently accessed files -> improve Audio/Video/Film
- Replies: 42
- Views: 25523
Re: Preload currently accessed files -> improve Audio/Video/
Setting a large block size (the maximum 512KB) may help out, if you've not already tried it.
- Wed Sep 11, 2013 3:57 pm
- Forum: Technical Support
- Topic: write cache not working with RamDisk Pro
- Replies: 17
- Views: 13347
Re: write cache not working with RamDisk Pro
Re-reading your initial post, you mention using Primo Ramdisk to hold the L2 cache for Primo Cache - don't do this, just forget about L2 caching and have a large L1 cache. The suggested 50/50 split would seem a good place to start, but (if using a 64-bit version of Windows) you should calculate your...
- Wed Sep 11, 2013 3:46 am
- Forum: Report Bugs
- Topic: Severe memory errors with large write cache
- Replies: 4
- Views: 5164
Re: Severe memory errors with large write cache
Does changing block size have any effect (and are you using the default 4KB size)?
- Tue Sep 10, 2013 11:19 pm
- Forum: Submit Suggestions
- Topic: A longer stream of urgent writes should pause the cache
- Replies: 5
- Views: 6000
Re: A longer stream of urgent writes should pause the cache
Sounds like a good idea, assuming that pausing the cache in mid-copy can be done without risk of data loss. But a normal copy shouldn't exercise the CPU at all (disk write speeds limit what can be done and disk controllers should be doing most of that) unless you're using encryption. Care to mention...
- Tue Sep 10, 2013 11:10 pm
- Forum: Technical Support
- Topic: write cache not working with RamDisk Pro
- Replies: 17
- Views: 13347
Re: Configure PrimoCache with Primo Ramdisk
I'm running both and, aside from deciding how to split memory between them, there's not really any complications involved in running them together (I would suggest a 50/50 memory split, unless you have specific reason to allocate more to one product). If you have not already done so, uninstall Fancy...