Running it in mod_perl or PPerl with no forking should speed things up a lot. Even just running it all from one script would be better than all that forking. Reading all your data into RAM can be very fast, but puts limits on how much you can scale as more data gets added. Putting it into a format like a dbm file where you can efficiently access individual records works well for some things, and doesn't need to read the whole thing into memory. It is somewhat faster than MySQL.
Your understanding about copy-on-write shared memory is correct, but forking is not always useful. It's most effective in situations where you have a lot of I/O waiting.
-
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.
|
