[BuckeyeTexan]

I'm really glad I didn't see this thread until now. It's less than helpful and not even somewhat amusing when someone makes bold statements about how easy it is to make a change to software that they didn't write and don't maintain.

I write .net software applications and .aspx and the implentation of what this post was asking is does NOT require a major undertaking; in fact, it’s very easy to do.

And you deploy those applications in a unix environment, right? Oh, you don't? Then stop wasting everybody's time with "in fact, it's very easy to do."

[Lazamataz]

It’s actually a little easier to do in Windows, which obviously 99% of aspx (ASP.NET) deploys to. But yeah. Yer right.

[Jim Robinson]

All I can say is prayer works. I was praying like crazy that John would find and fix the problem before the election, and lo and behold, the miracle was granted. And it was not the pipe, not the hardware, not the FR application software, not authentication, not the database, not a whole lot of other things that were suggested. And not outside interference. Turns out it was a conflict between two otherwise perfectly functioning pieces of systems software, and of course it only occured under maximum load conditions. John finally isolated the problem and reconfigured one of the components on election eve and throughput suddenly jumped. He thought he had it fixed, but on election day it started lagging again. He then installed a new software package that changed the way our frontend system handles web traffic and presto, problem solved. Have faith, my friends.

This is my layman’s understanding. John posted a litle more detail yesterday in tech terms that are over my head. And it was a gutsy call on John’s part. Great job, John!