This content has been marked as final. Show 8 replies
I downloaded the Linux 32-bit version, and expanded it into ~/jrts-2.2_ea.
works, and reports an RTS version.
../jrts-2.2_ea/bin/java -jar jarfile.jar
also works, and so does
../jrts-2.2_ea/bin/java -Xmx150M -jar jarfile.jar
../jrts-2.2_ea/bin/java -XXimmortalSize=100M -jar jarfile.jar
Unrecognized VM option immortalSize=100M
Could not create Java virtual machine.
What am I doing wrong?
She_Rab_Pawo wrote:Sorry I don't understand what you are asking. JRTS requires locking physical memory and so the max available memory it can use is a fraction of the available memory. For 32-bit that is likely between 2.5G and 3.0G; for 64-bit it depends on installed memory.
1. What is the memory max with RTS 2.2?
2. I am planning to use this with a program that is intended for production use in about 2 years. Is that reasonable?I'm not sure in what sense you are asking the question.
dibble wrote:The "limit" is the amount of contiguous physical memory that the OS will let you lock.
With the 64-bit build, is there a limit much less than the constraints of the supporting OS and the amount of available RAM (... page locking...) on the sizes of heap, immortal, and scoped memory?
On Linux this is somewhat vague as the over_commit policies lie to you about available memory. Disabling over-commit is only viable if you never get anywhere near to using all memory.