in reply to Re^4: Are monks hibernating?
in thread Are monks hibernating?

I have no problem with the speed of Perl, in general. What I do care about, is its rather large memory footprint.

For simple scripts of just a few lines of code, it matters that perl needs to load an executable of 1MB. Often, the load time is several times longer than the actual execution time. And that is something I just can't ignore.

Replies are listed 'Best First'.
Re^6: Are monks hibernating?
by BrowserUk (Patriarch) on Feb 16, 2007 at 11:46 UTC

    That tends to suggest that you use a lot of short-lived, high-frequency (and possibly high-concurrency) and./or IO-bound apps? The archetypal example of which is dynamic http serving, though there are obviously many other server type applications that also fit the bill.

    It's for this type of application that mod_perl/fastcgi are designed to alleviate exactly the problems you describe. It's not hard to see how a similar approach could be used for non-http applications that fit this mode of operation. A daemon app that runs perpectually in the background with all the relevant code loaded and a small, fast front-end that simply fires the parameters to the daemon and retrieves the results.

    Most of my stuff runs in the exact opposite way. Long-lived and infrequently called apps performing cpu-intensive operations on large volumes of data and run for hours or days.

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
[reply]

In Section Perl Monks Discussion