I need a DIAL-UP SIMULATOR, to see how things really load. Perhaps I can setup a proxy with bandwidth throttling on the bbs box, just for kicks.
I couldn't ever tell how fast old/new Haz Labs backups ran, since everytime I loaded them my router just said "lol hay tahts my ip" and routed me straight back in. So I had to bounce through fybertech's server and back to me, and then I could really see how fast they loaded for everyone. Which surprisingly seemed to be pretty decent considering my home connection's upstream isn't very good compared to what a real server can poop out.
As for faster pooping, I read up yesterday on using gzip encoding through Perl, and figured what the hell and went ahead and implemented it, since it didn't involve too much changery of the code. This is good for dial-up users (and well as easier on my monthly bandwidth totals), since it means the web pages get compressed before being transmitted. The forum already uses this automatically since it's practically built into PHP. The main part of the site uses Perl though, which actually requires you to compress the page content and reply with the appropriate http header yourself. The upside is, as I said, the pages will load faster. The downside is that it takes a moment to compress the page, which.. could make the page load slower. A WIN/LOSE SITUATION? I DUNNO! I guess it depends on how busy the server is at the particular moment you're trying to use it. I may disable the feature if it's noticably slower.
Part of the reason it's slow is that Perl runs seperately from the web server software, where as PHP actually runs as a module in the server software. I've been reading about a similar module for Perl, but it would require a bit of reworking the code for the main part of the site, and I have no idea at this point how much of a performance benefit it would provide. BUT, I'm gonna continue looking into it; this, combined with the gzip encoding, might make pages load as fast or faster than the forum does.
And then I stopped blabbering!