+1 to Sergey, I think OOME may confuse user and and may spoil the user's impression at first check of Apache Ignite.
вт, 1 авг. 2017 г. в 12:36, Vladimir Ozerov <voze...@gridgain.com>: > +1 > > 80% of RAM is way too aggressive. With this value virtually every user will > have problems with OOME or excessive swapping during development. I would > set maxMemory to some relatively small value, may be even less that 1Gb to > let Ignite run smoothly on developer's laptops, and print a performance > suggestion to increase it in production. > > On Tue, Aug 1, 2017 at 12:19 PM, Sergey Chugunov < > sergey.chugu...@gmail.com> > 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. > > >
