Memory use of Dancer2 running under Starman
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
Hi Andy I've got about the same memory usage per starman process. FWIW I keep different apps on different (smaller) servers. The pricing is comparable and I feel it's easier to upgrade/install Perl modules for one app without worrying about the impact on the other ones. Andrew On Thu, Mar 19, 2015 at 9: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
-- Andrew Solomon Mentor@Geekuni http://geekuni.com/ http://www.linkedin.com/in/asolomon
On Thu, 2015-03-19 at 11:35 +0000, Andrew Solomon wrote:
I've got about the same memory usage per starman process.
Thanks Andrew, that's good to know.
FWIW I keep different apps on different (smaller) servers. The pricing is comparable and I feel it's easier to upgrade/install Perl modules for one app without worrying about the impact on the other ones.
Yeah, fair one, good point. What I should have said is that it's actually the same app duplicated (one for each customer), but each one running in its entirely own instance for security and scalability reasons. Most of the time it's only one customer using a single app at any one time. Therefore, the only resource limitation is the RAM, so I was looking for ways to work around this. It would be interesting to see how it works with a decent-sized swap space, so maybe I should move to another provider and/or use a dedicated server. Thanks, Andy
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
I'd just like you to expand on this Sawyer:
and the one after (0.159003) will introduce two additional memory leaks.
Do you mean "will introduce FIXES OF two additional memory leaks"? Andrew On Fri, Mar 20, 2015 at 4:57 PM, Sawyer X <xsawyerx@gmail.com> wrote:
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
_______________________________________________ dancer-users mailing list dancer-users@dancer.pm http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
-- Andrew Solomon Mentor@Geekuni http://geekuni.com/ http://www.linkedin.com/in/asolomon
On Fri, Mar 20, 2015 at 6:01 PM, Andrew Solomon <andrew@geekuni.com> wrote:
I'd just like you to expand on this Sawyer:
and the one after (0.159003) will introduce two additional memory leaks.
Do you mean "will introduce FIXES OF two additional memory leaks"?
Eeek. Yes! That! Thank you, Andrew. :)
participants (3)
-
Andrew Beverley -
Andrew Solomon -
Sawyer X