[jira] [Created] (HBASE-25510) Optimize TableName.valueOf from O(n) to O(1). We can get benefits when the number of tables in the cluster is greater than dozens

["zhuobin zheng (Jira)" <ji...@apache.org>]

zhuobin zheng created HBASE-25510:
-------------------------------------

             Summary: Optimize TableName.valueOf from O(n) to O(1).  We can get benefits when the number of tables in the cluster is greater than dozens
                 Key: HBASE-25510
                 URL: https://issues.apache.org/jira/browse/HBASE-25510
             Project: HBase
          Issue Type: Improvement
          Components: master, Replication
    Affects Versions: 2.4.1, 1.4.13, 1.2.12
            Reporter: zhuobin zheng


There are tens of thousands of tables on our cluster (Most of that is KYLIN table). 
We found that in the following two cases, the TableName.valueOf method will severely restrict our performance.
 
Common premise: tens of thousands table in cluster
cause: TableName.valueOf with low performance. (because we need to traverse all caches linearly)
 
Case1. Replication
premise: one of table write with high qps, small value, Non-batch request.
cause: There are too much wal entry in WAL. So we need to deserialize too many WAL Entry which includes calling the TableName.valueOf method to instantiate the TableName object.


Case2. Active Master Start up
 
 



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