[tacticalogic]

Performance testing that does disk I/O can produce results in the test that don't translate in production because of disk contention from other processes that may be running alongside the process in production.

One million single writes to disk can be a much different proposition if the test has the disk all to itself than it is on a busy system where every write operation can potentially have to get queued and wait for some other process to release the disk channel.

IMHO

[mbj]

What if there’s little contention because you use queuing (a bus) and also scale out?

What if your algorithm is smart enough to somehow prevent contention?