Table B.6 and
Table B.7 are empty tables that you can use for copying and recording data. The bottleneck calculation in the previous example can be done in a spreadsheet, or manually with Table B-8. If Samba is as good as or better than FTP, and if there aren't any individual test runs that are much different from the average, you have a well-configured system. If loopback isn't much faster than anything else, you have a problem with your TCP/IP software. If both FTP and Samba are slow, you probably have a problem with your networking: a faulty Ethernet card will produce this, as will accidentally setting an Ethernet card to half-duplex when it's not connected to a half-duplex hub. Remember that CPU and disk speeds are commonly measured in bytes, network speeds in bits.
We've included columns for both bytes and bits in the tables. In the last column, we compare results to 10 Mb/s because that's the speed of a traditional Ethernet.
In
Table B.8:
-
CPU throughput = (KB/second from Figure 6-5) (number of CPUs)
-
Disk throughput = (KB/second from Figure 6-4) (number of disks)
-
Network throughput = (KB/second from Figure 6-6) (number of networks)
-
Total throughput = min (Disk, CPU, and Network throughput)
A typical test, in this case for an FTP
get, would be entered as in Table B-9:
The Sparc example we used earlier would look like Table B-10.
