On 11 August 2010 15:38, Thadeus Burgess <thade...@thadeusb.com> wrote:
> There is the ability to reduce memory usage however. Web2py likes to > call the import_all module when it first loads up. This basically > imports every web2py module so they are loaded into the python > interpreter. That means when your code actually imports anything from > gluon, the web server won't have to devote the resources to actually > importing that module when a client requests a page. If you comment > out the calls to the import_all module, it will reduce the initial > memory usage. > > Sorry I mean't Mb, 126M, and it doesn't look right to me I run it by using ./web2py.py. -- > Thadeus > > > > > > On Wed, Aug 11, 2010 at 9:32 AM, Thadeus Burgess <thade...@thadeusb.com> > wrote: > > Thats less than a MB. I don't see why you are complaining =P > > > > Typically my web2py instances all run around 75MB, with a max of 150MB > > under heavy traffic load. > > > > It also depends on how much your caching or how big your select queries > are. > > > > -- > > Thadeus > > > > > > > > > > > > On Wed, Aug 11, 2010 at 8:20 AM, Frank Church <vfcli...@gmail.com> > wrote: > >> I just started web2py on Linux, using the web2py.py command and memory > used > >> by the process is already 126K. > >> > >> What is wrong, how can it be reduced? > >> > >> -- > >> Frank Church > >> > >> ======================= > >> http://devblog.brahmancreations.com > >> > > > -- Frank Church ======================= http://devblog.brahmancreations.com
