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
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|