>I think my philosophy is that within reasonable boundaries first
>write maintainable, well tested code that does what it needs to do
>and only then check if there is any performance issue.
Agreed, Gabor. The code does "[do] what it needs to do..." which is
maintaining an HTML Web page that reports workstation configuration data,
a rather time-consuming process. Some of the hashes I use change
frequently as new data for table rows comes in (e.g.: new software, new
trusted sites).
The hashes are used to track progress through the file, and to catch new
additions as well as any disappearances. It's because of this that I'm
frequently adjusting the preallocation numbers.
Because the actual process is rather slow--and I'm not sure there's much
to be done to speed things up, I try to pick up what snippets of
performance I can in the setup code, hence my query.
Thanks for your time and considered advice.
Deane Rothenmaier
Programmer/Analyst -- IT-StdCfg
Walgreens Corp.
2 Overlook Point #N5102D
MS 6515
Lincolnshire, IL 60069
224-542-5150
People using flintlock pistols shouldn't fire warning shots. -- Andrew
Borntreger
_______________________________________________
ActivePerl mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
