Re: Re: Re: mySQL hits or Storable retrieves?

One simple question: Why are you storing your structure on disk? Why not use a CLOB or BLOB (the datatype is called TEXT in MySQL I think, but I forget) and store it in a table?

You may have to think some about how to physically structure the database doing this, but you wouldn't have to worry about file locking and other issues the database can abstract you away from.

Just a thought ....

Comment on Re: Re: Re: mySQL hits or Storable retrieves?

Replies are listed 'Best First'.
Re: Re: Re: Re: mySQL hits or Storable retrieves? by perrin (Chancellor) on Oct 03, 2001 at 08:26 UTC
The common reason for using simple file storage for a cache rather than a denormalized RDBMS table is that the file storage is much faster and consumes fewer resources. There's no network transfer, no SQL parsing, and no logging. And with the Linux file system hot files are generally kept in RAM, making the file system a sort of shared memory cache. It may seem less elegant, but the speed can't be beat and CPAN modules make it really easy.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Re: mySQL hits or Storable retrieves?
by perrin (Chancellor) on Oct 03, 2001 at 08:26 UTC

The common reason for using simple file storage for a cache rather than a denormalized RDBMS table is that the file storage is much faster and consumes fewer resources. There's no network transfer, no SQL parsing, and no logging. And with the Linux file system hot files are generally kept in RAM, making the file system a sort of shared memory cache. It may seem less elegant, but the speed can't be beat and CPAN modules make it really easy.

[reply]