At present, the live server is firebird (a/k/a lists); it's about eight years old, though it's had some minor upgrades. Originally, we were going to upgrade firebird again, and we bought it a great big disk drive. We installed it in a box named flamingo (outside the mythical-bird naming scheme because it was going to be temporary), with the plan we'd upgrade it, then mirror everything over, shut down and transplant the drive into firebird. Then we ended up buying roc, quite recently. It's hooked up, but isn't doing anything yet. Poor little flamingo, with its big drive but tiny, tiny brain, is doing all the SQL service right now. So if Gamehawk is slow, it's not the code's fault, it's not the web server's fault, it's not even the asphalt, it's the poor little database server's fault, but as soon as I get the database on roc configured, I'll suck it all over and roc can start earning its keep. When roc becomes the web server as well, we'll get another speed boost. At present, whenever you request a Gamehawk page, firebird has to load Perl and make a database connection, both of which are fairly high-overhead. Gamehawk is built to stay resident as a semi-permanent part of the web server, however. That'll happen on roc. So I'm quite aware that some pages take awhile to load, and I'm not overly worried about it right now... I haven't even worried about SQL optimization, which is something else that will improve performance.
