> 2) I am not exactly sure what you mean by "profiled your Perl", however I do > do benchmarks on code. I am in the process of redesigning our website, and > thus taking this opportunity to improve upon old scripts that will need > changing anyways. Current improvements to our main script have it runnning > 400% faster than the original. If I can make that 800% with C, I just might > reprogram it entirely.
Another .02 on this. If you're doing stuff for the web, agonizing over small performance improvements in your code can be a real waste of time. Don't kill yourself getting some script to run half a second faster when the finished page contains 200K of graphics and lots of your users are connecting with 28.8 and 56K modems. All of your performance gains will be lost in the bigger delays caused by graphic size, latency, and the like. Now, if you're finding things like the server is bogging down because it isn't handling the incoming requests quickly enough, that's another story. But when increasing web performance, you have to take the entire user->server->user roundtrip process into account. This e-mail is intended solely for the above-mentioned recipient and it may contain confidential or privileged information. If you have received it in error, please notify us immediately and delete the e-mail. You must not copy, distribute, disclose or take any action in reliance on it. In addition, the contents of an attachment to this e-mail may contain software viruses which could damage your own computer system. While Electronic Ink, Inc. has taken every reasonable precaution to minimize this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should perform your own virus checks before opening the attachment. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
