[mykes]

Originally Posted by Zachery

Like Brian told you at vBa, he also runs a rather larger forum with a stock configuration of the script.

Latest threads could result in a big problem because of a full table scan unless you are limiting it in some way.

OK, so how does a stock script that doesn't limit in some way the full table scans work out of the box on a rather larger forum? The probable answer is he's been hacking on php scripts that slowed his site down so he implemented the proper indexes to speed them up. When HE runs this script out of the box, he doesn't see the problem.

BTW, I'm looking at the output of iostat 1 and not seeing a full table scan happening when I load the page, with latest threads turned on, and with all the bells and whistles.

What I do see is the CPU idle% go to ZERO on all 4 (well, 2 Xeons) CPUs when vba is the site's home page. When it's not the home page, the CPUs are 75% idle, each.

Here's a pretty nifty perl script I wrote to monitor a linux system's health. It requires Term::Screen perl module installed. You may have to make your shell window taller, or hit the 'c' key while it's running to make it display less tall.