Difference between revisions of "Using RRDPound For IO Testing"

From Zenoss Wiki
Jump to: navigation, search
m (Formatting fixes)
 
Line 1: Line 1:
 
[[Category:Deployment]]
 
[[Category:Performance]]
 
 
 
Disk IO can be a major bottleneck on collectors. There is a tool called rrdpound (which will ship in Zenoss 4.2) that allows users to heavily exercise rrdtool and benchmark CPU/IO performance. You can find a copy of rrdpound here: https://gist.github.com/5470dced53234ba47ba4
 
Disk IO can be a major bottleneck on collectors. There is a tool called rrdpound (which will ship in Zenoss 4.2) that allows users to heavily exercise rrdtool and benchmark CPU/IO performance. You can find a copy of rrdpound here: https://gist.github.com/5470dced53234ba47ba4
  
Line 11: Line 7:
 
$ ##i##chmod +x rrdpound3.py
 
$ ##i##chmod +x rrdpound3.py
 
</console>
 
</console>
 +
 +
[[Category:Deployment]]
 +
[[Category:Performance]]

Latest revision as of 15:56, 21 November 2013

Disk IO can be a major bottleneck on collectors. There is a tool called rrdpound (which will ship in Zenoss 4.2) that allows users to heavily exercise rrdtool and benchmark CPU/IO performance. You can find a copy of rrdpound here: https://gist.github.com/5470dced53234ba47ba4

If possible, use the rrdpound that is distributed with Zenoss.

$ wget https://raw.github.com/gist/5470dced53234ba47ba4/82233853799e0631908ff1514423f717a500a935/rrdpound3.py
$ chmod +x rrdpound3.py