Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upDisk throughput in node console #1751
Comments
This comment has been minimized.
This comment has been minimized.
|
The sector size is always 512 for that variable, and that's how node_disk_bytes_read is calculated. |
This comment has been minimized.
This comment has been minimized.
|
So if I have 4 KB sectors I'll have to multiply by 8? |
This comment has been minimized.
This comment has been minimized.
|
It'll multiply by 512, and produce the correct value. |
This comment has been minimized.
This comment has been minimized.
|
So does this mean that for a 4 KB blocks device node_exporter will report each block as 8 ones? |
This comment has been minimized.
This comment has been minimized.
|
Yes, that's what the kernel does. |
This comment has been minimized.
This comment has been minimized.
|
Got it, thank you! |
hryamzik
closed this
Jun 17, 2016
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
hryamzik commentedJun 17, 2016
Shows speed in bytes counted as
node_disk_sectors_read * 512but sector size could be different. Looks likenode_disk_bytes_readshould be used instead.