I ask because the pdf you're probably referring to seems to imply the opposite. I only skimmed though but heres what I found that seems to imply the opposite:
"An entire Java heap (large or
small) can be marked consistently without falling behind
and resorting to long garbage collection pauses
because the C4 employs:
• Single pass completion to avoid the possibility of
applications changing references faster than the
mark phase can revisit them
• “Self-healing” traps that ensure a finite workload
and avoid unnecessary overhead
• Parallel marking threads to provide scalability that can
support large applications and large dataset sizes"
Maybe I'm looking at the wrong pdf can you provide a source for your claim? It's something useful to know if it's true.
I am hesitant to post direct link as document says 'Confidential and Proprietary'. But here is something in that doc about memory requirement
`The Zing components require the following amount of RAM on the ZVM machine.
l
64+ GB RAM recommended
16-32 GB RAM minimum, depending on the application memory requirements, for demonstration purposes only. Minimum is not sufficient for performance or scalability production testing of large or memory consuming enterprise applications.
Increase the memory as needed to accommodate the number and size of your Java application/Zing Virtual Machine (ZVM) instances.
The Pool license server requires the following amount of RAM on the license server machine. l 8 GB RAM recommended (4 GB minimum)`
This document is like 300+ pages with all the details about tuning and optimizations which make me think that it is not simple plug and play once you have paid for license.
