We are finding that anytime our application sends back large files to the requestor, we start chewing up memory fast. We haven't determined the precise cause or how to solve it yet, but it sounds like the same kind of situation. In our case, the particular large files are usually not generated by Builder, but typically are actually files being downloaded/transferred (e.g. images, documents, etc.).
On 8/19/07, Chris Carter <[EMAIL PROTECTED]> wrote: > > On 8/19/07, Wayne E. Seguin <[EMAIL PROTECTED]> wrote: > > > > Massimo, > > > > You should post this to ruby-talk mailing list. Make sure to include the > > version of ruby, the version rails, as well as any plugins and/or gems > your > > app uses. If at all possible try to include some code for analysis as > many > > people on that list will jump right on that to tell you what might be > > causing it and a better way to go about it (if one exists). > > > > Best, > > > > ~Wayne > > I think rails-talk would be even more appropriate. > > > -- > Chris Carter > concentrationstudios.com > brynmawrcs.com > _______________________________________________ > Mongrel-users mailing list > Mongrel-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >
_______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
