Smalltalk › Gemtalk › GLASS

out of temporary memory in fastcgi adaptor

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Johan Brichau-2

out of temporary memory in fastcgi adaptor

Hi,

I'm running into problems with an out-of-memory error bringing the fastcgi adapter gem down.
I highly suspect this is because of the size of the http response being generated. There are certain places in our application that can potentially lead to quite large http responses being returned.

This leaves me wondering if I should just increase the temp object space size for the entire system, or if I should include a mechanism like 'commit-on-almost-out-of-memory'.

At this time, the FastCGI adaptor simply quits. I would at least prefer that the entire adaptor does not have to be restarted.

Any ideas are appreciated ;-)

Johan

Dale Henrichs

Re: out of temporary memory in fastcgi adaptor

On 03/22/2011 08:13 AM, Johan Brichau wrote:

> Hi,
>
> I'm running into problems with an out-of-memory error bringing the fastcgi adapter gem down.
> I highly suspect this is because of the size of the http response being generated. There are certain places in our application that can potentially lead to quite large http responses being returned.
>
> This leaves me wondering if I should just increase the temp object space size for the entire system, or if I should include a mechanism like 'commit-on-almost-out-of-memory'.
>
> At this time, the FastCGI adaptor simply quits. I would at least prefer that the entire adaptor does not have to be restarted.
>
> Any ideas are appreciated ;-)
>
> Johan

Johan,

It might make sense for you to bump up the size of the temp obj cache
... the vm uses memory mapping so that pages are loaded into real memory
on demand and then shrunk when no longer needed, so there isn't a real
penalty for having a larger tempobj cache...

If you use the common-on-almost-out-of-memory, you run a risk of
committing partial data structures during your request handling and also
you are exposed to commit conflicts that have to be dealt with cleanly
so increasing the tempobj cache is a better solution ...

Dale

Gerhard Obermann

Re: out of temporary memory in fastcgi adaptor

Using topaz -l -T500000 for the fastcgi's should help!

Gerhard

On Tue, Mar 22, 2011 at 6:09 PM, Dale Henrichs <[hidden email]> wrote:

On 03/22/2011 08:13 AM, Johan Brichau wrote:

Hi,

I'm running into problems with an out-of-memory error bringing the fastcgi adapter gem down.
I highly suspect this is because of the size of the http response being generated. There are certain places in our application that can potentially lead to quite large http responses being returned.

This leaves me wondering if I should just increase the temp object space size for the entire system, or if I should include a mechanism like 'commit-on-almost-out-of-memory'.

At this time, the FastCGI adaptor simply quits. I would at least prefer that the entire adaptor does not have to be restarted.

Any ideas are appreciated ;-)

Johan

Johan,

It might make sense for you to bump up the size of the temp obj cache ... the vm uses memory mapping so that pages are loaded into real memory on demand and then shrunk when no longer needed, so there isn't a real penalty for having a larger tempobj cache...

If you use the common-on-almost-out-of-memory, you run a risk of committing partial data structures during your request handling and also you are exposed to commit conflicts that have to be dealt with cleanly so increasing the tempobj cache is a better solution ...

Dale