If the most time is spent on processing and we have no idea what kind of processing you are doing it is not easy to give you pointers. Perhaps you could put some code or pseudocode online. If not perhaps as someone else mentioned you could take advantage of the database being compiled not interpretive.
If you can arrange for your "processing" to be done at a db level you may be able to simplify the amount of perl-based processing you do. For example you might be able to use a temporary table to do things. Or as mentioned above grouping will be faster in the db.
Can you really not provide any finer resolution on the amount of time taken in the subprocesses of the "processing" step? You should be profiling everything otherwise how are you going to find where the bottleneck is in the code?
-
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.
|
