its very slow at the moment. i need suggestions on how to speed this thing up :)

I count 16 process invocations (17, including the script), and from the look of things, the script is contributing noise to the overall time. It should be trivial to add some timing code to measure how much time each subprocess is taking.

Then you can figure out how to optimize or combine your subprocess scripts. For example, do you really need to run parsecache twice to generate separate files? Or could that script be changed to spit out two files from a single invocation? Ditto for report. That would cut subprocess invocation in half, which would have to be a win.

In reply to Re: Parsing a lot of data. Very slow. Need suggestions by dws
in thread Parsing a lot of data. Very slow. Need suggestions by vxp

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.