in reply to mySQL hits or Storable retrieves?
MySQL is fast enough for most uses like this, but if you have an unusual amount of traffic or a poorly designed schema and your data does not need to be 100% up-to-date, caching is tremendously helpful. The approach you described will work just fine. I would suggest you use Cache::Cache or MLDBM::Sync instead of rolling your own filesystem database though. The biggest problem with this approach is that your data set may become too large to efficiently regenerate all of it every 5 minutes.
I used a load-on-demand approach with caching for the eToys.com product data. This avoids problems stemming from a large data set, but does result in a slower load time for the first user. Here's a description:
Caching is a big subject, and there are lots of tricks you can use (lazy reloading, pre-filling the cache with hot objects, etc.).
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: mySQL hits or Storable retrieves?
by Hero Zzyzzx (Curate) on Oct 02, 2001 at 18:56 UTC | |
by mandog (Curate) on Oct 02, 2001 at 21:43 UTC | |
by kwoff (Friar) on Oct 03, 2001 at 03:14 UTC | |
by perrin (Chancellor) on Oct 02, 2001 at 19:15 UTC |