In my early days in Perl on Windows, glob behaved in some undesireable fashion -- I no longer remember what the problems were.
You might try to isolate whether glob is causing the high CPU utilization -- I suspect it is NOT, but worth checking. You can replace glob with something like this:
# ... Create a regular expression to represent the wildcard string nor
+mally submitted to glob
my $MatchPatternRegex = "ABC\\_XYZ\\_.{9}\\.xml";
if (opendir CURDIR, $directoryName) {
my $nextFilename = readdir CURDIR;
while ($nextFilename)
{
if ($nextFilename =~ /$MatchPatternRegex/)
{
# ... Do your stuff here
}
}
closedir CURDIR;
}
If using this instead of glob eliminates your CPU problem, you know something new about your environment, and perhaps you'll want to craft around glob. If this does not change the behavior, you've ruled out glob as the problem, which could be useful information as you troubleshoot this.
-
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.
|