Hello Gary, Yes, I must have compared the virtual memory with real memory. However, the "used" memory shown by top seems to go with virtual memory size, i.e., if I start 10 Python, there will be about 800MB memory shows "used." And if I want to start more, I'll start to get memory errors. So, no matter what that is, I'm having a hard time starting 20 Python processes with 1.5GB memory. I didn't have this problem with PHP, and don't have this problem on Windows. Something doesn't sound right here :) Maybe those who are running big sites with web.py can speak up and tell us how well Python apps scale on Linux servers?
Jack > You've compared them wrong - you're comparing virtual memory use on > Linux to real memory use on Windows. For example, here's the physical > and virtual usage I get (on OS X) for a freshly opened Python > instance: > grbmbp:~ grb$ ps -c -p 17894 -o command,rss,vsize > COMMAND RSS VSZ > Python 2556 37140 > Here's the same thing on Linux: > [EMAIL PROTECTED] ~]$ ps -o cmd,rss,vsize -p 17853 > CMD RSS VSZ > python 2672 7620 > RSS (or RSIZE, or RES) is the "resident set size", which is roughly > the amount of physical RAM the process is using. This is generally > what you should care about. VSZ (or VSIZE, or VIRT) is a measure of > the size of the process' virtual address space. You probably > shouldn't be concerned with this number at all. Measuring actual > memory usage is a very subtle and error-prone process, and there's no > single number in top or anywhere else that can summarize it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
