You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Lucas Bradstreet (Jira)" <ji...@apache.org> on 2020/02/28 16:04:00 UTC

[jira] [Comment Edited] (KAFKA-8963) Benchmark and optimize incremental fetch session handler

    [ https://issues.apache.org/jira/browse/KAFKA-8963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17047765#comment-17047765 ] 

Lucas Bradstreet edited comment on KAFKA-8963 at 2/28/20 4:03 PM:
------------------------------------------------------------------

A benchmark and some optimizations were added in  "KAFKA-9039: Optimize ReplicaFetcher fetch path" which will be included in 2.5. Further improvements will be best solved by  KAFKA-9048.


was (Author: lucasbradstreet):
A benchmark and some optimizations were added in  "KAFKA-9039: Optimize ReplicaFetcher fetch path" which will be included in 2.5. Further improvements will require KAFKA-9048.

> Benchmark and optimize incremental fetch session handler
> --------------------------------------------------------
>
>                 Key: KAFKA-8963
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8963
>             Project: Kafka
>          Issue Type: Task
>            Reporter: Lucas Bradstreet
>            Assignee: Lucas Bradstreet
>            Priority: Major
>             Fix For: 2.5.0
>
>
> The FetchSessionHandler is a cause of high CPU usage in the replica fetcher for brokers with high partition counts. A jmh benchmark should be added and the incremental fetch session handling should be measured and optimized.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)