I've gotten a couple messages from users about PHP timeouts, so I've tuned the way it works a little bit. I've increased the timeout limit, and increased the amount of memory a script can consume.
Keep in mind that a part of the time lag is attributable to BlogAds, Amazon, and Google AdSense each hitting their respective homes. However, the example raptor gave on the opinion page equates to comments retrieval.
I haven't run into those problems, but I don't know what's happening on slower lines, like dial-up. So let me know when something breaks. What I'm seeing after the long conversion process is relatively fast and stable.
In the process of trying to make the site bullet-proof, the conversion's now done from ASP to PHP running under IIS for all of the main pages. If you have trouble with that, you can also try http://www.rantburg.com:8080/rantburg/index.php, which is the same site running under Apache 2.0. The original ASP version continues to run on http://www.aach.net/rantburg, though I've let the photos get out of sync, and http://aach.net:8080/rantburg/index.php leads to the Apache version. The IIS version runs Microsoft ASP for the few remaining ASP pages (Opinion and Thugburg for now), and the Apache version runs them under ActiveHTML. I've got a few other toys I'm fiddling with, and if any of them work out, I'll use them, too. Keep in mind, though, that the whole mess lives on one database and its backup. |