Linux

解釋 tiobench 結果

  • January 2, 2012

tiobench在我的 raid1 上執行,它給了我以下結果。

  1. 為什麼#####顯示而不是吞吐量?
  2. 為什麼 8 執行緒的 seq.reading 使用 2836% CPU?

我的結果:

$tiobench
No size specified, using 2000 MB
Run #1: /usr/bin/tiotest -t 8 -f 250 -r 500 -b 4096 -d . -TTT

Unit information
================
File size = megabytes
Blk Size  = bytes
Rate      = megabytes per second
CPU%      = percentage of CPU used during the test
Latency   = milliseconds
Lat%      = percent of requests that took longer than X seconds
CPU Eff   = Rate divided by CPU% - throughput per cpu load

Sequential Reads
                             File  Blk   Num                   Avg      Maximum      Lat%     Lat%    CPU
Identifier                    Size  Size  Thr   Rate  (CPU%)  Latency    Latency      >2s      >10s    Eff
---------------------------- ------ ----- ---  ------ ------ --------- -----------  -------- -------- -----
2.6.32-37-server              2000  4096    1  ###### 93.62%     0.001        0.02   0.00000  0.00000  6897
2.6.32-37-server              2000  4096    2  ###### 384.4%     0.001        0.03   0.00000  0.00000  2778
2.6.32-37-server              2000  4096    4  ###### 1552.%     0.001        0.07   0.00000  0.00000   980
2.6.32-37-server              2000  4096    8  ###### 2836.%     0.002       10.15   0.00000  0.00000   533

Random Reads
                             File  Blk   Num                   Avg      Maximum      Lat%     Lat%    CPU
Identifier                    Size  Size  Thr   Rate  (CPU%)  Latency    Latency      >2s      >10s    Eff
---------------------------- ------ ----- ---  ------ ------ --------- -----------  -------- -------- -----
2.6.32-37-server              2000  4096    1  ######     0%     0.001        0.01   0.00000  0.00000     0
2.6.32-37-server              2000  4096    2  ######     0%     0.001        0.00   0.00000  0.00000     0
2.6.32-37-server              2000  4096    4  ######     0%     0.001        0.00   0.00000  0.00000     0
2.6.32-37-server              2000  4096    8  ######     0%     0.001        0.00   0.00000  0.00000     0

Sequential Writes
                             File  Blk   Num                   Avg      Maximum      Lat%     Lat%    CPU
Identifier                    Size  Size  Thr   Rate  (CPU%)  Latency    Latency      >2s      >10s    Eff
---------------------------- ------ ----- ---  ------ ------ --------- -----------  -------- -------- -----
2.6.32-37-server              2000  4096    1   87.39 6.816%     0.030     2509.77   0.00059  0.00000  1282
2.6.32-37-server              2000  4096    2   89.32 17.86%     0.057     2478.84   0.00039  0.00000   500
2.6.32-37-server              2000  4096    4   86.98 36.70%     0.113     2353.49   0.00020  0.00000   237
2.6.32-37-server              2000  4096    8   86.46 82.35%     0.214     6847.69   0.00078  0.00000   105

Random Writes
                             File  Blk   Num                   Avg      Maximum      Lat%     Lat%    CPU
Identifier                    Size  Size  Thr   Rate  (CPU%)  Latency    Latency      >2s      >10s    Eff
---------------------------- ------ ----- ---  ------ ------ --------- -----------  -------- -------- -----
2.6.32-37-server              2000  4096    1    1.75 0.335%     0.001        0.02   0.00000  0.00000   521
2.6.32-37-server              2000  4096    2    1.73 0.221%     0.002        0.03   0.00000  0.00000   781
2.6.32-37-server              2000  4096    4    1.71 0.877%     0.002        0.02   0.00000  0.00000   195
2.6.32-37-server              2000  4096    8    1.74 2.671%     0.002        0.03   0.00000  0.00000    65

這意味著東西溢出,計算毫無意義。

如果你想在讀取測試中獲得有意義的數據,你需要確保文件大小比你的 RAM 大得多,否則你所測試的基本上是你的 RAM 速度和核心的記憶體算法。

嘗試mem=256M在核心引導行的末尾進行引導,然後重新執行您的測試,--size 1000以獲得大約 1G 的被測文件大小。

如果您在測試期間沒有聽到磁碟的聲音,要麼它們真的很安靜(對您有好處!),要麼您正在執行的測試沒有測試您認為的內容。

引用自:https://unix.stackexchange.com/questions/28150