Re: performance with mysql / file-caching / hash reference on demand

Thanks to all for the comments on my post. I got some new ideas and tasks.

One part of my initial question is still not clear for me.

If caching information to get better performance is a good way why is doing this with Storable and DB a bad or at least not so good way?

I could do my routines on a daily basis, freeze the hashref, store it in a table and retrieve the hashrefs of one item by ID with only one request.

---------------------------
| my_cache_table          |
---------------------------
| ID (primary)            |
---------------------------
| hashref with prices     |
---------------------------
| mod_date of prices      |
---------------------------
| hashref with images     |
---------------------------
| mod_date of images      |
---------------------------
| hashref with other stuff|
---------------------------
| mod_date of other stuff |
---------------------------
[download]

I don´t want to appear stubborn but I like to comprehend things. Caching one or another way seems to be common practice the above mentioned way not at all.

Thanks for some more enlightment

Comment on Re: performance with mysql / file-caching / hash reference on demand Download Code

Replies are listed 'Best First'.
Re^2: performance with mysql / file-caching / hash reference on demand by 1nickt (Canon) on May 02, 2021 at 19:05 UTC
There doesn't seem to be anything wrong with that design to me. The way forward always starts with a minimal test.	[reply]