The second run

As I use Optimizeit to drill down into the code during my second run, I get to a point where I can see that over 31% of the application run time is spent running the find() method of the Matcher class. This is shown in the following figure.

Ordinarily I would dive right into that second method and see what I can do to fix it, but there's a problem here. It doesn't seem to be my code; it's the code from the regular expression classes built into the JDK.

Next: The third run - Up: Optimizing your first project Previous: The first run -