Nfsdist tool #1347
Merged
Nfsdist tool #1347
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
samuelnair
requested review from
4ast,
brendangregg,
drzaeus77,
goldshtn and
yonghong-song
as code owners
|
[buildbot, ok to test] |
goldshtn
reviewed
Sep 11, 2017
tools/nfsdist_example.txt
Outdated
| 8191 usecs. Write traffic is largely clusstered in the 64 - 127 usecs bracket. | ||
| The faster read traffic is probably coming from a filesystem cache and the slower | ||
| traffic from disk. The reason why the writes are so consistenly fast is becuase | ||
| this example test was run on a couple of VM's and i believe the hypervisor was |
goldshtn
reviewed
Sep 11, 2017
tools/nfsdist_example.txt
Outdated
| 26K reads falling within 8 - 30 usecs and about 18K reads spread between 128 - | ||
| 8191 usecs. Write traffic is largely clusstered in the 64 - 127 usecs bracket. | ||
| The faster read traffic is probably coming from a filesystem cache and the slower | ||
| traffic from disk. The reason why the writes are so consistenly fast is becuase |
goldshtn
reviewed
Sep 11, 2017
tools/nfsdist_example.txt
Outdated
|
|
||
| In this example you can see that the read traffic is rather bi-modal, with about | ||
| 26K reads falling within 8 - 30 usecs and about 18K reads spread between 128 - | ||
| 8191 usecs. Write traffic is largely clusstered in the 64 - 127 usecs bracket. |
goldshtn
reviewed
Sep 11, 2017
tools/nfsdist_example.txt
Outdated
| applications reading from a NFS share and can better expose problems | ||
| experienced by NFS clients. | ||
|
|
||
| Note that this only traces the common NFS operations (read,write,open and |
There was a problem hiding this comment.
Spaces between operations: "read, write, open, and ..."
goldshtn
reviewed
Sep 11, 2017
tools/nfsdist_example.txt
Outdated
| 4 -> 7 : 137 |****************************************| | ||
| 8 -> 15 : 3 | | | ||
|
|
||
| This shows a write workload, with writes hovering primarily in the 4-7ms range |
|
Damn, I should have run it through ispell. Thanks for the spell check @goldshtn |
|
LGTM! Thanks. |
CrackerCat
pushed a commit
to CrackerCat/bcc
that referenced
this pull request
Jul 31, 2024
nfsdist: trace NFS operation latency distribution, similar to the other *dist tools.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a pull request to add the nfsdist tool, which is to compliment the nfsslower tool that i had added in earlier and in keeping with the suite of {etx4,xfs,zfs}(slower|dist) tools that we currently have.
As before, following the CONTRIBUTING-SCRIPTS.md guidelines and added in the smoke test as well.