comment on

Before we can know whether the extra 8 seconds to use split is of any consequence, we need to know how much other processing you are doing on each line. If the time to process one file is on the order of a minute or so, then extra 8 seconds/file becomes noticeable. If it takes 10 minutes/file, then an extra 8 seconds doesn't make much difference.

If you don't yet know the answer to this question, then it is too soon to make this kind of optimization.

In reply to Re: Optimise file line by line parsing, substitute SPLIT by ramlight
in thread Optimise file line by line parsing, substitute SPLIT by go9kata

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.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks