I've posted an update elsewhere but hope you can appreciate with the sheer number of various posts - most of them all dealing with the same topic - that it's a little difficult to know which post to update, and still be working on the isolations we're doing to correct the problem.

Here's the update for this thread on April 5, 3pm MST

We beleive that we have isolated the problems which are causing a very unexpected problem with the server performance of FlyerTalk. Literally 98% of the problems are related to the hardware - not the software - and once we have that corrected, then many of you might be forced to go back to the foums you came from and talk travel.

The problems we have isolated so far are realted to load balancing, memory failure, script rewriting and a few other things in the chain of connections. For the record, the old FlyerTalk ran on one server. For this move I ponied up and purchased three brand new servers and other things related so you'd really enjoy FT from an access speed for a long time to come. The way these servers interact with each other is similar to the way that some of you communicate with each other on FlyerTalk - you simply don't hear what the other member is saying, though they insist they are telling you something.

Anyway, we have dropped many features on the relaunch simply to figure out of that was a problem relating to the performance. As noted, none of these features are the problem - only the servers hardware serving up the pages.

We are almost complete with an entire audit of the entire Web site and will likely have the changes and performance available for your comment by the end of the week, if not sooner.

I hope this helps and if you come across any others who haven't read the news - please tell them that contrary to what they may think - we really do know that there's a problem with the servers performance and we missed Spring Break to get it taken care of for you.