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 remember once compiling a "minimal" perl that was 2MB. I imagine
that would probably be insufficient to run Mojolicious, though I really
haven't a clue, but it suggests to me that it's possible to reduce the size
of the perl interpreter and, therefore it seems, the size of the
Mojolicious daemon?
On Wed, Sep 19, 2018, 8:19 PM Charlie Brady <
charlieb-m...@budge.apana.org.au> wrote:
>
> 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 anyone have some advice on where to start looking at where memory is
> being used and how to minimise it?
>
> Thanks
>
--
You received this message because you are subscribed to the Google Groups
"Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mojolicious+unsubscr...@googlegroups.com.
To post to this group, send email to mojolicious@googlegroups.com.
Visit this group at https://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.
