I guess I don't understand your initial question. Why does a user have to have a unique process if the output data for all users "is very similar"? Could you use a cookie to identify a user who will be using this script? Perhaps you could elaborate more on the problem.

Using mod_perl has some RAMifications (pardon the pun), but the advantage is the large speed increase from not having to compile the script or re-open a database connection for each call. Any data stored in local (not global) variables is freed at the end of the script run, so I don't see it as a big deal.

UPDATE: Ok... so you did elaborate, sorry about that.

If you use a good backend database to keep up with these minute changes you are describing, your SQL calls are on the order of thousands of a second. I would think this is okay.

As far as the actual presentation of data: is there really an advantage to "thawing out" and printing a session versus rebuilding and printing it from scratch? If your backend database is quick, printing out a template with the newer data should work just fine.

Honestly, I don't have a ton (umm.. or any) experience with using sessions. So if there is a stronger argument for why using a session is better, please explain why/how. Thanks.

In reply to Re: Re: Improving efficiency - repeated script hits at small interval by shambright
in thread Improving efficiency - repeated script hits at small interval by BUU

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.