What are the reasons that max jvm heaps do not have size or max physical memory on the machine?

Question

I have a 64-bit machine, theoretically the address space is 2 ^ 64 bytes and has 32 GB of physical memory.

It is a server server with six cores and is a production server.

Since there is no other process that consumes massive amounts of memory, and the jvm server is the only application that works, is there any reason not to install a bunch of jvm on a really large number?

I see that he is tuned for less than 10 concerts, and there is no explanation that I can think about it.

As I mentioned earlier in the post: I understand that the kernel, cache, and other processes will require sharing RAM. But by banning any other processes and native OS material, nothing else happens. This machine is a production machine and exclusively for this particular jvm.

Is there any reason not to install on something like 20 gigs / 32 g (physical drum)?

From the comments below - it doesn’t look like that ... except for the need for a quick failure, thanks for your inputs

Answer 1

Since the operating system also needs RAM, for cache, buffers, daemons such as syslogd, page tables, kernel data structures, etc.

In addition, JVM designers have no idea what other applications you can start after starting the JVM. Therefore, it is reasonable for the JVM not to depend on all RAM by default.