On Sat, Dec 20, 2003 at 11:16:53AM -0500, Perrin Harkins wrote:
> Eric Sammer wrote:
> >I've had fantastic luck with MLDBM::Sync thus far, not that it's the all
> >in one wonder tool.
>
> I think it's a great tool, especially when you need easy access to
> complex data structures, but I wanted t
Eric Sammer wrote:
I've had fantastic luck with MLDBM::Sync thus far, not that it's the all
in one wonder tool.
I think it's a great tool, especially when you need easy access to
complex data structures, but I wanted to point the non-intuitive fact
that a local MySQL can be a great cache for a r
Perrin Harkins wrote:
Eric Sammer wrote:
Any DBM file or shared memory caching will be infinitely faster than
making a DB round trip.
Actually, it turns out that this is no longer true. MySQL is really
fast these days. A simple query on a local MySQL is faster than just
about anything except
Eric Sammer wrote:
Any DBM file or shared memory caching will be infinitely faster than
making a DB round trip.
Actually, it turns out that this is no longer true. MySQL is really
fast these days. A simple query on a local MySQL is faster than just
about anything except IPC::MM or BerkeleyDB (
Chris Ochs wrote:
I have an application where known users connect, and normally I do a db
query to get their configuration information. What I would like to do is
preload all of this information into memory, say into a global hash where
all the mod perl processes can access it.
You want to use one
I have an application where known users connect, and normally I do a db
query to get their configuration information. What I would like to do is
preload all of this information into memory, say into a global hash where
all the mod perl processes can access it.
I could have each process load the
