My vote goes for option #1 too. I don’t think that 80% is too aggressive to bring it down.
IGNITE-5717 was created to fix the issue of the 80% RAM allocation on 64 bit systems when Ignite works on top of 32 bit JVM. I’ve not heard of any other complaints in regards the default allocation size. — Denis > On Aug 1, 2017, at 10:58 AM, [email protected] wrote: > > I prefer option #1. > > D. > > On Aug 1, 2017, 11:20 AM, at 11:20 AM, Sergey Chugunov > <[email protected]> wrote: >> Folks, >> >> I would like to get back to the question about MemoryPolicy maxMemory >> defaults. >> >> Although MemoryPolicy may be configured with initial and maxMemory >> settings, when persistence is used MemoryPolicy always allocates >> maxMemory >> size for performance reasons. >> >> As default size of maxMemory is 80% of physical memory it causes OOME >> exceptions of 32 bit platforms (either on OS or JVM level) and hurts >> performance in setups when multiple Ignite nodes are started on the >> same >> physical server. >> >> I suggest to rethink these defaults and switch to other options: >> >> - Check whether platform is 32 or 64 bits and adapt defaults. In this >> case we still need to address the issue with multiple nodes on one >> machine >> even on 64 bit systems. >> >> - Lower defaults for maxMemory and allocate, for instance, max(0.3 * >> availableMemory, 1Gb). >> This option allows us to solve all issues with starting on 32 bit >> platforms and reduce instability with multiple nodes on the same >> machine. >> >> >> Thoughts and/or other options? >> >> Thanks, >> Sergey.
