The gpsar from cloudian

gpsar's People

Contributors

Watchers

gpsar's Issues

A user asked for disk IO to be added.

We have this info from sar.

 tps
         Indicate the number of transfers per second that were  issued  to  the
         device.   Multiple  logical requests can be combined into a single I/O
         request to the device. A transfer is of indeterminate size.

 rd_sec/s
         Number of sectors read from the device. The size of a  sector  is  512
         bytes.

 wr_sec/s
         Number  of  sectors written to the device. The size of a sector is 512
         bytes.

 avgrq-sz
         The average size (in sectors) of the requests that were issued to  the
         device.

 avgqu-sz
         The  average  queue  length  of  the  requests that were issued to the
         device.

 await
         The average time (in milliseconds) for  I/O  requests  issued  to  the
         device  to  be served. This includes the time spent by the requests in
         queue and the time spent servicing them.

  svctm
         The average service time (in milliseconds) for I/O requests that  were
         issued to the device.

  %util
         Percentage  of  CPU  time during which I/O requests were issued to the
         device (bandwidth  utilization  for  the  device).  Device  saturation
         occurs when this value is close to 100%.

And also a machine may have lots of disk devices. So it's a lot of
graphs that one could generate.

Guess, you could do read/write Megabytes per second using rd_sec/s and
wt_sec/s. If I also draw %util on the same graph using the right y2 axis
it might not be too bad for one device? What info do you normally look
at? If could do two graphs per device, the second one would be svctm and
await on the y axis with avgrq-sz and avgqu-sz on y2 and maybe put tps
in their somewhere but not sure. Guess I'll have to see how it all looks
and judge from there also.