[an error occurred while processing this directive]
Measurement
In this stage we run the benchmark as specified by run rules and verify the results. We also measure system statistics like CPU utilization, memory usage, interrupt usage, and network I/O. Currently we use 'sar' to gather all system information.Analysis
In this stage we use get a closer look at what's going on during the benchmark run. We do this by using tools such as SGI's kernprof and lockmeter . If you have suggestions for other tools, please email lse-tech.This is also where performance problems should be identified.Improvement
Improvement can take on many forms, from server and client tuning,testing existing performance patches, and new code optimizations. The idea here is to improve both absolute performance and relative scalability.
This process should be repeated until we reach a target level of performance
and scalability. To find out what we're workin gon now, check
out the project status.
Note: Performance is measured by throughput, in megabits per second,
as reported by NetBench. Scalability is measured as a ratioof
SMP performance (2P, 4P, 8P, ... ) divided by uniprocessor performance.
Server Hardware
8 x 700 MHz PIII Xeon, 1MB L2, Intel Profusion chipset
4 GB memory, 4 Intel Gbps ethernet adaptersServer Software
Linux 2.4
Samba 2.2
Sysstat 4.0Client Hardware
866 MHz PIII, 256MB memory
100 Mbps ethernetClient Software
Microsoft Windows 2000 Professional
NetBench 7.0.1Network Hardware
2 Foundry Networks Fast Iron workgroup switches