I'm new to Prevayler: Best Java settings and practices for Prevayler?
Naveen Chawla <[email protected]>
| Newsgroups | gmane.comp.java.prevayler |
|---|---|
| Message-ID | <CAGs7EcXY9UDKL+bMco57fH34GGCuf+=B67wta3u79jLxBG9_OQ@mail.gmail.com> |
I'm (maybe unjustifiably) scared of potentially big crippling garbage collections/allocation failures etc., but haven't really experienced them or how to minimize them. Should I use a fixed or variable sized heap? If fixed, should it just be as big as I can make it? (What % of your total memory have you made it?) If variable, what settings should I best use (Xms, Xmx, Xminf, Xmaxf, Xmine, Xmaxe)? Should I be conscious of potentally large crippling garbage collections? If so, should I prefer instance variables over local variables, or does it matter? Should I induce garbage collection regularly, or just let it do it itself? Just wondering if there are any special known best Java settings and practices for Prevayler because of its potentially big memory size etc. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion _______________________________________________ "Databases in Memoriam" -- http://www.prevayler.org