Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
It would be ood if you can suggest something other than loading the file content into database and fetching it.

Probably, but not based on the information you've provided so far. Why do you seem reluctant to provide information?

Please provide:

  • The size in bytes of both files.
  • The number of records in both files.
  • The number of fields in the lines of both files.
  • A couple of sample records from both files.

    If the data is proprietary, then take a couple of sample records and change the identifying words, numbers etc., but try to ensure that they remain realistic.

  • And idea of how often you will need to do this and how often the file(s) change.

    Ie. "The bigger file remains constant and the smaller changes one a week";

    Or: "This is a one-off problem never to be repeated".

    Or: "The two files never change, but the (combination of) fields used for comparison changes every day".

    Or: ...

With that information, we here have a realistic chance of understanding the scale of the problem and possible solutions.


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^5: Reduce CPU utilization time in reading file using perl by BrowserUk
in thread Reduce CPU utilization time in reading file using perl by madtoperl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.