You can monitor it with jconsole. Is the memory building up gradually and not being garbage collected? Is it being redeployed without restarting jetty?
------------------------------------- Peter Robinett<[email protected]> wrote: Thanks all for the comments and suggestions. I'm totally new to the Java world, so thanks for mentioning all these various options. First, my system: MySQL is the database I'm using with my Lift app (and some other very low traffic apps) and is tuned pretty aggressively to use little memory. It seems to only use tens of megabytes. My Lift app is based upon 1.1-SNAPSHOT and archetype lift- archetype-basic. Second, JVM options and analysis: how should I pass options to the JVM when launching jetty and Lift with 'mvn jetty:run'? What heap size should I use? How do I monitor a JVM process? My actors being notified of the REST POSTs are scala.actors, as I understood them to be sufficient[1]: class NodeActor extends Actor with ListenerManager. The CometActors that listen to the NodeActors are defined like: class NodeGraph extends CometActor. Thanks for your help, Peter [1]: http://groups.google.com/group/liftweb/msg/86d518b0c44b1b58?hl=en On Jul 28, 10:31 am, Spencer Uresk <[email protected]> wrote: > I'm not sure about how much overhead Jetty adds to the mix (I'd assume it > would be small, but I could be wrong), but on my production server, a small > Lift app added only 30 - 40 mb or so to the memory usage of my Tomcat > instance. Based on my experience with running Java and Groovy based > applications on a VPS, a 256 mb slice should be plenty unless you have lots > of concurrent sessions and/or big sessions. If people are having a different > experience with Lift-based apps, I'd be interested in hearing that (and > why). > > Peter, Have you tried running jmap on your box to generate a heap dump and > then analyzing that to see what is using up all the memory? Using something > like MAT (www.eclipse.org/mat/) makes it pretty easy to see what the likely > culprits are, and then you can go from there. > > - Spencer > > On Tue, Jul 28, 2009 at 3:55 AM, Timothy Perrett > <[email protected]>wrote: > > > > > Agreed; its pretty light to run all those services. I have a lift based app > > that's been running for quite some time and its using around 250mb of RAM > > on > > average. A raw lift app will probably use 128mb RAM as minimum. > > > Cheers, Tim > > > On 28/07/2009 10:08, "marius d." <[email protected]> wrote: > > > BTW 256mb seems to me ridiculous small for a server side application. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
