| Name : perl-Cache-FastMmap
| |
| Version : 1.43
| Vendor : obs://build_opensuse_org/devel:languages:perl
|
| Release : 1.1
| Date : 2015-11-20 16:10:03
|
| Group : Development/Libraries/Perl
| Source RPM : perl-Cache-FastMmap-1.43-1.1.src.rpm
|
| Size : 0.12 MB
| |
| Packager : (none)
| |
| Summary : Uses an mmap\'ed file to act as a shared memory interprocess cache
|
Description :
In multi-process environments (eg mod_perl, forking daemons, etc), it\'s
common to want to cache information, but have that cache shared between
processes. Many solutions already exist, and may suit your situation
better:
* *
the MLDBM::Sync manpage - acts as a database, data is not automatically
expired, slow
* *
the IPC::MM manpage - hash implementation is broken, data is not
automatically expired, slow
* *
the Cache::FileCache manpage - lots of features, slow
* *
the Cache::SharedMemoryCache manpage - lots of features, VERY slow. Uses
IPC::ShareLite which freeze/thaws ALL data at each read/write
* *
the DBI manpage - use your favourite RDBMS. can perform well, need a DB
server running. very global. socket connection latency
* *
the Cache::Mmap manpage - similar to this module, in pure perl. slows
down with larger pages
* *
the BerkeleyDB manpage - very fast (data ends up mostly in shared memory
cache) but acts as a database overall, so data is not automatically
expired
In the case I was working on, I needed:
* *
Automatic expiry and space management
* *
Very fast access to lots of small items
* *
The ability to fetch/store many items in one go
Which is why I developed this module. It tries to be quite efficient
through a number of means:
* *
Core code is written in C for performance
* *
It uses multiple pages within a file, and uses Fcntl to only lock a page
at a time to reduce contention when multiple processes access the cache.
* *
It uses a dual level hashing system (hash to find page, then hash within
each page to find a slot) to make most \'get()\' calls O(1) and fast
* *
On each \'set()\', if there are slots and page space available, only the
slot has to be updated and the data written at the end of the used data
space. If either runs out, a re-organisation of the page is performed to
create new slots/space which is done in an efficient way
The class also supports read-through, and write-back or write-through
callbacks to access the real data if it\'s not in the cache, meaning that
code like this:
my $Value = $Cache->get($Key);
if (!defined $Value) {
$Value = $RealDataSource->get($Key);
$Cache->set($Key, $Value)
}
Isn\'t required, you instead specify in the constructor:
Cache::FastMmap->new(
...
context => $RealDataSourceHandle,
read_cb => sub { $_[0]->get($_[1]) },
write_cb => sub { $_[0]->set($_[1], $_[2]) },
);
And then:
my $Value = $Cache->get($Key);
$Cache->set($Key, $NewValue);
Will just work and will be read/written to the underlying data source as
needed automatically.
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/devel:/languages:/perl/SLE_11_SP4/i586 |
Hmm ... It's impossible ;-) This RPM doesn't exist on any FTP server
Provides :
FastMmap.so
perl(Cache::FastMmap)
perl(Cache::FastMmap::OnLeave)
perl-Cache-FastMmap
Requires :
