> One of the background loads needs to consist of several > threaded applications running concurrently. Threads really mess > up the scheduler and CPU usage. Java programs and just plain > C programs that are threaded will make good background loads. Yes, and loads which generate lots of interrupts. Most SCSI and ethernet traffic generates interrupts at a frantic pace. So any disk or network benchmark would do wonders at causing interrupts at the wrong place or at the wrong time.
