Precisely, that's what I was looking for, instinct and experience. This program that I talk about is a mere example, just looking for any issues on performance when perl compiles large pieces of code. Yes, you're right one of the bottlenecks is the initial DB calls for each instruction (user, session, event control) plus any more that the code requires to return a result to the calling module.
As more "lower level" stuff gets tacked on to each instruction yes, time to response will certainly slow down, though I thought that if perl has to compile 5-6 megs of plain text files for each instruction my immediate thought would be the fact that it would slow the program down where only 200k of that code is relevant.
Certainly makes sense chromatic! Thanks for the reply.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.