Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Does the CPAN shell perhaps try to keep the whole module database in RAM?

    Yes, that's how it does some of the query commands it implements. It has been so for a long time now. And yes, under-powered computers may have problems with that. (But it can be worse - CPANPLUS is much heavier or at least was, a long time ago when I tried it.)

    CPAN.pm has an experimental support for the module database in a SQLite db, as implemented by CPAN::SQLite. It decreases the memory consumption. You can try that.

    • Re: CPANPLUS

      It's been also quite a long time since I've looked at how much RAM CPANPLUS takes, but the last time I did, it was raking an impressive 500M. Which, of course, makes it almost impossible to use interactively on the 512M of RAM of my poor machine.

      • by kane (2600) on 2009.02.13 6:09 (#67338) Journal

        CPANPLUS uses far less on my machine, but YMMV; for those strapped for ram, there's the option to use an SQLite backend.

        To enable it, simply follow the following steps from the default shell:

        ### set SQLite as the backend
        CPAN Terminal> s conf source_engine CPANPLUS::Internals::Source::SQLite

        ### update any dependencies (will install sqlite drivers if you need them)
        CPAN Terminal> s selfupdate dependencies

        ### save configuration
        CPAN Terminal> s save