We haven't done benchmarks for that (reducing that is in the plans!) but I can tell you the latest version of Dancer2 (0.159002) fixed a memory leak, and the one after (0.159003) will introduce two additional memory leaks.

The first (fixed in 0.159002) we found at $work somehow. It was a very rare situation which is why we haven't encountered it yet. The other two fixes (slated for the next release) include fixes that we were able to test for (and we have the tests for them in the distribution as well) but we (at least $work) were not able to actually produce in our production or testing environment.

Just wanna mention that, since it's in the topic, somewhat. :)

On Thu, Mar 19, 2015 at 10:41 AM, Andrew Beverley <andy@andybev.com> wrote:

Hi dancers,

I'm trying to get an idea of what is a "normal" value in terms of memory
use of Dancer2 running under Starman. I realise this is a "how long is a
piece of string" question, but I would appreciate some replies to make a
comparison.

I'm finding it's roughly 100MB per worker, which seems to be roughly the
case regardless of the application. What do other people's run at? Is
there any way I can reduce the memory use and/or where should I look to
do so?

I'm running 10 different Dancer2 applications on a VPS with 4GB of
memory. Each application has 2 Starman workers. This is about the limit
of what I can run before the memory on the server tops out.

I'd like to get more applications per server. The applications generally
have fairly light-utilisation, but my VPS provider has disabled swap
space, so they can't be swapped out when they're not being used
unfortunately.

Thanks,

Andy

_______________________________________________
dancer-users mailing list
dancer-users@dancer.pm
http://lists.preshweb.co.uk/mailman/listinfo/dancer-users