tbench
tbench is another file server workload similar to dbench. However, tbench produces only the TCP and process load. tbench does the same socket calls that SMBD would do under a netbench load, but tbench does no filesystem calls. The idea behind tbench is to eliminate SMBD from the netbench test, as though the SMBD code could be made fast. The throughput results of tbench tell us how fast a netbench run could go if we eliminated all filesystem I/O and SMB packet processing. tbench is built as part of the dbench package.
Table 6 depicts the impact of Hyper-Threading on the tbench workload. As before, each data point represents the geometric mean of five runs. Hyper-Threading definitely would improve tbench throughput, from 22% to 31%. The overall improvement is 27% based on the geometric mean of the five test scenarios.
Table 6. Effects of Hyper-Threading on tbench throughput
| Number of clients | 2419s-noht | 2419s-ht | Speed-up |
| 20 | 60.98 | 79.86 | 31% |
| 30 | 59.94 | 77.82 | 30% |
| 60 | 55.85 | 70.19 | 26% |
| 90 | 48.45 | 58.88 | 22% |
| 120 | 37.85 | 47.92 | 27% |
| Geometric Mean | 51.84 | 65.77 | 27% |
| Note: Data are throughput in MB/sec: higher is better. | |||
View Hyper-Threading Speeds Linux Discussion
Page: 1 2 3 4 5 6 7 8 9 10 Next Page: Hyper-Threading support in Linux kernel 2.5.x