Romex Software Forum

ebfortin wrote:I've been using PrimoCache 3.0 Beta for a month now. No issue. No crash. Speed is as expected, compared to 2.x.

Same - my experience spans several months on two devices.

Single data point: I have been running 3.0.x in Win10 x64 box for several months w/o issue. I did try to upgrade a creaky 32-bit XP machine from 2.7 to 3.0 but ended up with a delayed blue screen. I would not hesitate to deploy v3 wherever it is beneficial.

I'd simply like the ability to preload a folder/file by right-clicking it, and choosing the option from a Primocache context link. You could preload games, videos, whatever you wanted just before you used them, speeding it all up tremendously. That capability is better aligned with a ramdisk IMO. D...

Jaga wrote:I'd simply like the ability to preload a folder/file by right-clicking it, and choosing the option from a Primocache context link. You could preload games, videos, whatever you wanted just before you used them, speeding it all up tremendously.

That capability is better aligned with a ramdisk IMO.

Any assumptions in science and practice always either are confirmed experimentally, or are rejected. Without having results of experiments, there is no sense to argue because it is not soccer and not policy. The experiment must be clean and clear: established checkbox of "Enable Defer-Write&qu...

I do not know whether there is a system defect here, or it is feature of the software. I have read that was written by users and what they have stated wishes. All users have own remarks, people are interested. I bought this software because it is interesting to me, and I apply it on the home comput...

I do not work at/for Romex Software and do not represent the company in any way. If you are suggesting the conversation is no longer constructive then I wish you well. Keep in mind "public opinion" is not represented by a single voice. I invite others to to join the discussion if they wish...

@sinus - I do not doubt what you are seeing on *your* workstation/workloads. However, the various 'write modes' in PrimoCache have been in place for some time and well reviewed by many users. Any systemic defects would have been identified long ago.

Of course - unless the L1 memory cache exceeds the size of the (huge) file being processed. Even if not flagged 'urgent' the effect is the same with data flowing to permanent storage as fast as it is being generated once the memory buffer size is exceeded.

I do not find this to be the case (at all) across several workstations where PrimoCache is installed (mixture of later v2 and v3 beta). In the absence of other decision criteria my preferred flush methodology is "Average" which maintains cache availability as expected without urgent releas...