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.
  • I tend to use a variation of this module:

    http://svn.develooper.com/combust/trunk/lib/Combust/Cache.pm

    (use "anon" for username, no password).

    It's quite fast, not a lot of code, supports complex data structures, meta data and a couple of other things.

    (Develooper::DB::db_open is an Apache::DBI like dbh caching thing).

        - ask
    --

    -- ask bjoern hansen [askbjoernhansen.com], !try; do();

  • caching (Score:3, Insightful)

    by inkdroid (3294) on 2003.08.12 8:37 (#23017) Homepage Journal
    This would make a nice topic for an article Chromatic.
  • I did a talk on caching modules at OSCON a couple of years back. I've been meaning to write it up into an article for a while now. The basic results of my benchmarking were that IPC::MM, BerkeleyDB (native locking), Cache::Mmap, and MLDBM::Sync are the fastest at sharing data. DBD::Proxy was a neat idea, but has terrible performance. You'd be better off just doing an extra fetch to check a cache table.
  • Got memcached [danga.com]?

    Seriously, for caching of simple key-value pairs, it rocks. It's superfast and dead simple.