Great suggestion Tom! Will pass it on to the team. Thanks Brian
-----Original Message----- From: AOLserver Discussion [mailto:[EMAIL PROTECTED] On Behalf Of Tom Jackson Sent: 08 October 2007 14:59 To: AOLSERVER@LISTSERV.AOL.COM Subject: Re: [AOLSERVER] More on lost of memory of aolserver process So if the issue isn't that you have only 500meg of memory, but that, for instance, a user got tired of waiting and kept hitting 'reload', or even that a bunch of users wanted the massive report at the same time, you can use a threadpool with a very limited number of threads...max you want simultaneous download. You could still get more requests at once, but they will queue up and wait. Then if they hit reload, no cost. If this is an autogenerated report, you could also save it as a file. That might help by using fastpath as a cache, and mem map on unix like machines. Even though AOLserver will stop sending if the client quits or reloads, you may have a backend process which keeps on going. tom jackson On Monday 08 October 2007 06:22, Fenton, Brian wrote: > Hi Gustaf, > > The developers have acknowledged that this is a bug, so they are changing > their code. However thanks for the good suggestions! :-) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
