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 | ---------------------------
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
In reply to Re: performance with mysql / file-caching / hash reference on demand
by derion
in thread performance with mysql / file-caching / hash reference on demand
by derion
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |