On Wed, 26 Sep 2018, sri wrote:
> If that's the case, why not just fatpack your mojo app?
Um, because I didn't know about fatpack? :-)
Thanks, looks a good suggestion. The system will continue to be slow, but
not as slow...
Am Mittwoch, 26. September 2018 18:28:10 UTC+2 schrieb Charlie Brady:
>
>
> This is why I need to run a persistent daemon rather than use CGI mode.
>
> root@jy-cx:~# time perl -e exit
>
> real0m0.035s
> user0m0.000s
> sys 0m0.030s
> root@jy-cx:~# time perl -MMojolicious::Lite -e
This is why I need to run a persistent daemon rather than use CGI mode.
root@jy-cx:~# time perl -e exit
real0m0.035s
user0m0.000s
sys 0m0.030s
root@jy-cx:~# time perl -MMojolicious::Lite -e exit
real0m11.011s
user0m8.690s
sys 0m0.400s
root@jy-cx:~#
Looking at an strac
On Thu, 20 Sep 2018, Stefan Adams wrote:
> Wow! That's fascinating! Thanks for sharing! I'm surprised by how
> much the memory footprint grows for a minimal perl program to one
> running M::L!
Bear in mind this is one M::L program which has loaded (via the Mount
plugin) a few dozen other
Wow! That's fascinating! Thanks for sharing! I'm surprised by how much
the memory footprint grows for a minimal perl program to one running M::L!
On Thu, Sep 20, 2018 at 2:57 PM Charlie Brady <
charlieb-m...@budge.apana.org.au> wrote:
>
> Hi Stefan, thanks for trying to help.
>
> I know the pe
There's some good general advice from our friend Brian D Foy here:
https://stackoverflow.com/questions/9733146/tips-for-keeping-perl-memory-usage-low
To bring this more closely focussed on Mojolicious, my daemon is loading a
ew dozen other Mojolicious::Lite applications using the Mount plugin.
Hi Stefan, thanks for trying to help.
I know the perl executable will make some contribution to the memory
footprint, but not much.
I can measure that separately by running a minimum perl program and
looking at its resource usage. If I run 'perl -e "<>"', I see this in
/proc/$pid/status:
..
I shouldn't involve myself in this topic because I haven't the knowledge,
but it sounds fascinating. Wouldn't the majority of the 50MB memory
footprint be from the Perl interpreter itself? Wouldn't the question be,
how to reduce the size of the Perl interpreter? Different compile options?
e.g. I re
Some Mojolicious::Lite code I've written has been adapted by another group
in my company to run on their embedded controller (limited CPU and limited
memory). They are now asking for my advice on how to reduce the memory
footprint of their daemon. It's consuming about 50MB at the moment.
Does
