NewSize and MaxNewSize should had been at least (recommended) 25% of the your new heap size (for 4g make it 1gb) but I don't think that would had made a difference anyway, seems the problem at this point is a memory leak.
On Monday, February 1, 2016 at 5:56:49 PM UTC, Sebastian Jastrzebski wrote: > > @guido > > Yep, I have included the jvm settings you suggested in my projects. The > outcome was similar to what I reported. > > ## .sbtops > -J-server > -J-Xms4g > -J-Xmx4g > -J-XX:NewSize=256m > -J-XX:MaxNewSize=256m > -J-XX:+AlwaysPreTouch > -J-XX:MaxTenuringThreshold=2 > -J-XX:+UseConcMarkSweepGC > -J-XX:+ParallelRefProcEnabled > -J-XX:+UseCMSInitiatingOccupancyOnly > -J-XX:CMSInitiatingOccupancyFraction=80 > > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
