On Sun, 7 Oct 2018 at 19:49, Eirik Bakke <eba...@ultorg.com> wrote: > (As an aside, it would be nice for the heap size calculation logic in > nblauncher.cpp to be factored out to also work for the NetBeans platform > application launcher, in > harness/apisupport.harness/windows-launcher-src/applauncher.cpp . But that's > a separate issue.)
Please don't! I think that's making incorrect assumptions. On Mon, 8 Oct 2018 at 04:43, Tim Boudreau <niftin...@gmail.com> wrote: > The Achilles heel of large heaps is garbage collection. The more memory to > scan, the longer the pause. ... So the right answer is going to depend on > what else the system is doing. If > the IDE gets painfully slow after a while, your heap is probably too big. This! Given how long that logic has been in the launcher, are we really sure that the memory options in the launcher give a better out-of-the-box experience for the majority than the JDK defaults? Personally, with this and the other thread about a Java agent I'd be much more inclined to a UI for generating a user-land conf file than adding more logic to the launchers. Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
