Hi Ted,
The additional hash map is very small, possibly a few KB. Each request type
("produce", "fetch", etc.) will have such a map which have a few entries
depending on the client API versions the broker will encounter. So if
broker encounters two client versions for "produce", there will be two
entries in the map for "produce" requests mapping from version to meter. Of
course, hash map always have additional memory overhead.
Thanks,
Allen
On Mon, Mar 19, 2018 at 3:49 PM, Ted Yu <[email protected]> wrote:
> bq. *additional hash lookup is needed when updating the metric to locate
> the metric *
>
> *Do you have estimate how much memory is needed for maintaining the hash
> map ?*
>
> *Thanks*
>
> On Mon, Mar 19, 2018 at 3:19 PM, Allen Wang <[email protected]> wrote:
>
> > Hi all,
> >
> > I have created KIP-272: Add API version tag to broker's RequestsPerSec
> > metric.
> >
> > Here is the link to the KIP:
> >
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-
> > 272%3A+Add+API+version+tag+to+broker%27s+RequestsPerSec+metric
> >
> > Looking forward to the discussion.
> >
> > Thanks,
> > Allen
> >
>
