>
> I think this primarily a problem of how web2py is being served rather
> than a web2py problem. Just the welcome app and no traffic takes 70MB
> of memory by default.
the problem is with the architecture of webserver behind web2py
processes vs threaded vs async
ok, most of recommended ways of
I think this primarily a problem of how web2py is being served rather
than a web2py problem. Just the welcome app and no traffic takes 70MB
of memory by default.
On Fri, Nov 11, 2011 at 11:59 AM, Bruno Rocha wrote:
> On Fri, Nov 11, 2011 at 12:52 AM, Richard Baron Penman
> wrote:
>>
>> I was al
On Fri, Nov 11, 2011 at 12:52 AM, Richard Baron Penman
wrote:
> I was also surprised how much resources the default configuration
> uses, just for the welcome app. Seems Django has better configuration.
Avoid the use of models, try to use conditional models (subfolders) or
better, create your da
I was also surprised how much resources the default configuration
uses, just for the welcome app. Seems Django has better configuration.
I tried that static technique but haven't noticed a difference yet. I
only have the default welcome app static files.
Webfaction support recommends reducing the
I had the same problem with webfaction - be sure to set your static files
to be delivered by ngenix or apache.
I followed the info in the link above and it reduced my memory usage
However I have both a Django and a Web2py instance set up on my account and
Web2py takes more memory for my a small
Hi Richard,
This thread:
http://groups.google.com/group/web2py/browse_thread/thread/ce28ccceb29a459/e2d7471f2894b177
... provide two solutions to reduce memory usage.
Kind regards,
Annet.
6 matches
Mail list logo
