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 <timo...@getintheloop.eu>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." <marius.dan...@gmail.com> 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 liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
