On Sat, 2005-06-25 at 18:09 -0400, Peter Arremann wrote:
Heavy network IO for a webserver is a 100mbit link. Heavy network IO for a database server is a trunked gigabit link or something proprietary like a firelink. Heavy disk IO is 4 to 8 fibre links to an EMC or netapp. I was simply using IPM as an example because it runs on exactly the kind of hardware we've been talking about - dual/quad opterons... v40z to be exact.
I was just saying that "Heavy [network] IO" from a performance standpoint of optimally leveraging Opteron NUMA/HyperTransport (or most RISC/UNIX platforms) versus just your typical, desktop PC-focused (just wider) Xeon MCH interconnect is rarely done with web apps.
Case-in-point: I've seen far too many consultants used to designing web servers install a piss-poor network fileserver or LAN application server. And when I've challenged them or their clients on this, they have absolutely no idea what I'm talking about. It's only when I put my money where my mouth's at with a minimal investment and minor system change that they realize what I'm talking about.