[GitHub] [flink-web] akalash commented on pull request #524: Add Buffer debloating blog post

[GitBox <gi...@apache.org>]

akalash commented on PR #524:
URL: https://github.com/apache/flink-web/pull/524#issuecomment-1096864423

   > "instabilities", do you mean "imbalances" or "varying conditions" (instabilities refer rather to failures than to stable conditions)
   
   Let's discuss it later but I think that `instabilities` is more correct word since I mean situations when conditions/environment are not stable(for example, it can be related to losing constant losing and establishing network connections)
   
   > why "minimum possible overhead", do you mean "minimum latency" (typical duo is "maximum throughput" and/vs "minimum latency")
   
   latency in general is not so important here. The latency for aligned checkpoints and memory usage for unaligned checkpoints are important. So I try to find somehow the correct word for both of these cases. Perhaps, something like "maximum throughput" vs "minimum  effective memory"( or "memory overhead")
   
   > For Java non-networking/Netty affiliated people, make clear that the term buffer is here used as a data structure to store records but also as the unit that is transfered via network.
   
   It is exactly what is described in `Network buffer`, isn't it? -- ` Flink gather records into the network buffer 
   which is the smallest unit of sending data to subtasks`. Perhaps, it makes sense to rephrase it but I think the explanation is exactly as you described.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org