Look like OpenVZ container. I play with this a lot.
First of all memory size, not always limits your need.
64M - to low. Hardly to run static serve apache. (moderate load).
VZ container also has limits for (sample from my server)
   100:  kmemsize        2378291    4102256 2147483647
2147483647          0
            lockedpages           0          0        256
256          0
            privvmpages       21128     102598     131072
131072          0
            shmpages             16       1024      21504
21504          0
            dummy                 0          0          0
0          0
            numproc              23         40        240
240          0
            physpages          1743      53890          0
2147483647          0
            vmguarpages           0          0      65536
65536          0
            oomguarpages       5184      54115      26112
2147483647          0
            numtcpsock            6         73      10000
10000          0
            numflock              1          3        188
206          0
            numpty                0          1         16
16          0
            numsiginfo            0         10        256
256          0
            tcpsndbuf         53760    2589440    2589488
3589488        272
            tcprcvbuf         98304    2597248    2589488
3589488       6505
            othersockbuf       8960      37504    2589488
3589488          0
            dgramrcvbuf           0      12160     262144
262144          0
            numothersock         22         36      10000
10000          0
            dcachesize        89250     130725    3409920
3624960          0
            numfile             663        996       9312
9312          0
            numiptent            14         14        128
128          0
=============
Last columns show how many times, processes in vz were limited by
corresponding resource.
Since this my out server with my own container, I try to set maximum,
but even this high sometimes not enough.

So I am not recommend use business critical application in vz for this
reason. Or try to get more resources.

On 11 фев, 09:06, raven <ravenspo...@yahoo.com> wrote:
> Here are the details of memory usage when web2py is NOT running
>
> top - 21:58:38 up 11:57,  2 users,  load average: 0.00, 0.00, 0.00
> Tasks:  10 total,   1 running,   9 sleeping,   0 stopped,   0 zombie
> Cpu(s):  0.0%us,  0.0%sy,  0.0%ni,100.0%id,  0.0%wa,  0.0%hi,
> 0.0%si,  0.0%st
> Mem:     65536k total,    13320k used,    52216k free,        0k
> buffers
> Swap:        0k total,        0k used,        0k free,        0k
> cached

> > > > On Wed, Feb 10, 2010 at 9:40 AM, raven <ravenspo...@yahoo.com> wrote:
> > > > > web2py is working very well for me on my MSWINDOWS desktop.
>
> > > > > I am ready to deploy my first application on a virtual private server
> > > > > running Ubuntu with 64K of guaranteed RAM
>
> > > > > I loaded the web2py source and typed
>
> > > > > python2.5 web2py.py
>
> > > > > and immediatly ran out of memory.
This often happens when process try to allocate memory with margin.
I had cases when something allocate 4G on machine with 1G ram.
And it works because, linux has ability to promise this allocation in
future.
In vz container this case would lead to killed or hang app.

-- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To post to this group, send email to web...@googlegroups.com.
To unsubscribe from this group, send email to 
web2py+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en.

Reply via email to