I don't see anything that would make that big of a difference. I think the problem is elsewhere.

• time is a system call. You could save a little speed by calling it once outside the loop.

• If /approv/i should actually checking for equality, lc($_) eq 'approv' is 122% faster when the check is true and 28% faster when the check is false.

Comments not related to performance:

• $localtime = FormatTime($moduleField[2]) if $moduleField[2];
  $localtime = "n/a" unless $moduleField[2];
  [download]

  could be written

  $localtime = $moduleField[2] ? FormatTime($moduleField[2]) : "n/a";
  [download]

• Assigning to $_ is dangerous. And it's not even necessary here. Change

  $_ = $headers[$dataCount];
  if( /approv/i )
  [download]

  to

  if( $headers[$dataCount] =~ /approv/i )
  [download]

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.