...
In case of 32-bit machines, a java process can span up to a maximum of 1.6 GB of memory. Assuming that the heap - size is set to the maximum, that is, 1.6 GB limit, the number of 'In Memory' components can be increased until the Peer server 's memory usage reaches this point (or within safe limits of this point, say approximately 70% of 1.6 GB).
In case of 64-bit machines, the java heap memory is relatively high (approximately 4 GB) and a larger number of components can be launched in In-memory. However, one needs to be careful in assigning more memory to the Peer Server process since more Heap memory has an impact on the number of threads that can be created by the JVM. As the heap memory of a process increase, the number of threads that can be created is less; this can have an adverse effect on Peer Server performance. As such, the precise heap - memory allocated to the Peer Server JVM has to be determined by testing that particular configuration being run (that is, by running the full application to ensure there are no adverse effects on the system).
...