cat /proc/<pid>/status will give you a lot of information about memory
usage.
ex:
...
VmPeak:     2316 kB
VmSize:     2212 kB
VmLck:         0 kB
VmHWM:       940 kB
VmRSS:       936 kB
VmData:      164 kB
VmStk:        84 kB
VmExe:        12 kB
VmLib:      1876 kB
VmPTE:        20 kB
...

On Jun 7, 7:57 pm, Jose Galvez <[EMAIL PROTECTED]> wrote:
> newbie question - how do you determine how much memeory your app is
> using, on Linux of course
> Jose
>
> Ben Bangert wrote:
> > On Jun 6, 2008, at 9:43 PM, John Salerno wrote:
>
> >> I was thinking about signing up with a web host that supports Pylons
> >> (among many other things) and one of the differences between the
> >> various plans is application memory for long-running processes. The
> >> plan I'd like to sign up for has 80MB. Does anyone know if this is
> >> enough for basic Pylons applications?
>
> > The PylonsHQ site takes up about 39 megs of memory (25mb on launch,
> > and I cache a bunch of docs to memory which grows it to about 39). I
> > don't see why 80mb wouldn't be enough.
>
> >> Just in general, how exactly can I calculate how much memory a Pylons
> >> application (or any other type of application, for that matter) will
> >> require? Is there some general range I might be able to rely on? Does
> >> 80MB seem like enough for just playing around and hobbyist work?
>
> > Sure, no problem. PylonsHQ will run for months without budging past
> > 39mb. It's serving up the reference docs right now, and has a Pastebin
> > using a Postgres database via SQLAlchemy.
>
> > A significantly larger app that I run at the company I'm at peaks a
> > bit higher at 122mb.
>
> > Cheers,
> > Ben
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" 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/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to