On Sat, Jan 10, 2015 at 10:25 PM, <t...@wakelift.de> wrote:
> On 01/10/2015 08:39 PM, Gabor Szabo wrote:
> > Well, whatever it is, this means that the web application fills all
> > the memory and crashes every 30-40 requests.
> > Luckily there are not many people who read the site :)
> > Gabor
> I'm expecting you're talking about
> Can you point me at the actual pieces of code where this problem appears?
> - Timo
I have not analyzed that yet, I just noticed that if I run the application
then it eats up all
the memory quite quickly. So I wanted to write a small example that is
already doing it and
I started with that for-loop.
A step above that would be a simple script using Bailador:
If I launch that and reload it several times I can see how it is is using
more and more memory.
Each number pair is after on request:
2568884 117304 after launch
It is not as bad as the full Perl6::Maven application which gives these
Each number pair is after a single request to the main page which generates
a few more
internal request, but this is one page-view:
2609444 160676 after launch
but of course the Perl6::Maven site loads a JSON file on every request and