[
https://issues.apache.org/jira/browse/HBASE-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207259#comment-15207259
]
Enis Soztutar commented on HBASE-15519:
---------------------------------------
bq. We should make sure that we never add that back. We got a 20% improvement
by removing map lookups in the metrics path.
Agreed that we should be careful in the perf analysis to make sure that hot
code paths are not affected. Some overhead was due to long string
concatenations for coming up with the metric name I think. We also check the
quotas per-operation, so something to check.
> Add per-user metrics
> ---------------------
>
> Key: HBASE-15519
> URL: https://issues.apache.org/jira/browse/HBASE-15519
> Project: HBase
> Issue Type: Sub-task
> Components: metrics
> Reporter: Enis Soztutar
>
> Per-user metrics will be useful in multi-tenant cases where we can emit
> number of requests, operations, num RPCs etc at the per-user aggregate level
> per regionserver. We currently have throttles per user, but no way to monitor
> resource usage per-user.
> Looking at these metrics, operators can adjust throttles, do capacity
> planning, etc per-user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
