redis-doc
redis-doc copied to clipboard
Latency trouble shooting
Add document for latency trouble shooting:
- Add 'disable-thp' into latency.md, reference redis change.
- Document 'Latency induced by reading smaps/smaps_rollup', reference atop change.
- Introduce tcprtt to trace TCP latency,
Deploy request for redis-doc pending review.
Visit the deploys page to approve it
| Name | Link |
|---|---|
| Latest commit | 22882a83d3719b2c98442032b3a05b1b9fc28d04 |
Hello @pizhenwei
Thanks for this contribution. Before reviewing it thoroughly, I'd like to understand why this should be included in the docs instead of other perf tools/metrics/etc.
@filipecosta90 please feel free to jump in
Hi @itamarhaber
I read docs from redis.io, followed the 'Edit this page' button, and added these changes in this PR. It's the first time I've tried to contribute to redis doc, if anything gets wrong, please correct me, thanks!
Hi @itamarhaber Could you please give me any hint, should I move any documents into another document or directory?
@itamarhaber PING!
+PONG nothing is wrong with the contribution (thanks and congrats on your first!) per se. I'm not a performance engineer/admin so I'm having difficulties evaluating these tips. I'm also wondering whether there are other, perhaps even more useful, tips that we want to include. Therefore my question :)
@filipecosta90 thoughts?
@filipecosta90 PING!
Hi, I edited the top comment and added link.
Hi, @oranagra
I hope I'm not disturbing you... This seems to have been ignored, could you please take a look at this?
I'm not familiar with some of these details myself either.. i'll try to grab the attention of someone who does.. but also, i guess that for the case of redis.io docs, it wouldn't be a terrible idea to include these details, even if they're slightly misplaced... maybe it'll help someone, and maybe some future edit will change / improve them...
@ushachar, this information is available in Red Hat Linux training and docs. I recommend not adding this information to our docs as third-party docs may change.
Hi, @nermiller @ushachar @itamarhaber
From your suggestions, closing this PR seems right. Thanks for your suggestions!