Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
  1. If this is to eliminate false positives, why is it necessary to count all the negative hits?

    Doesn't the presence of just one false hit exclude a document?

    If so, the simplest optimisation might be remove the /g;

  2. Presumably, this is just one example of a generic problem?

    Otherwise, if you'd just left the regex running from the point where you posted your question, until you posted your follow-up, you would have processed a little under 1 million documents of the size of those you've linked.

  3. If it is a generic problem of optimising complex regexes, then you'll need a programmable solution.

    Whilst it may be possible to hand-optimise the supplied regex to cut runtime, you'd then be faced with having to do it all again for the next set of false matches.

  4. Perhaps the next simplest solution would be to multi-task your processing of the documents.

    Spread your load across the 4 cores of a typical current machine and you can cut your processing time to a 1/4.

    Purchase a $100 of Amazon's EC2 time and cut your processing time to 1/100th or less.


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.

The start of some sanity?


In reply to Re^2: Help with speeding up regex by BrowserUk
in thread Help with speeding up regex by eversuhoshin

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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others examining the Monastery: (7)
As of 2024-04-23 19:13 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found