hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9976) Don't create duplicated TableName objects
Date Sat, 16 Nov 2013 01:06:17 GMT

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

stack commented on HBASE-9976:
------------------------------

I'll convert these into CLI args:

-    final long namespaceSpan = 1000000;
+    final long namespaceSpan = 20000000;
     // How long to take to pause after doing a put; make this long if you want to fake a
struggling
     // server.
     final long multiPause = 0;
@@ -749,7 +749,7 @@ public class TestClientNoCluster extends Configured implements Tool {
     getConf().setLong("hbase.test.multi.pause.when.done", multiPause);
     // Let there be ten outstanding requests at a time before we throw RegionBusyException.
     getConf().setInt("hbase.test.multi.too.many", 10);
-    final int clients = 20;
+    final int clients = 5;

This looks good.  Will help server-side too.  Did you figure your sync issue?

> Don't create duplicated TableName objects
> -----------------------------------------
>
>                 Key: HBASE-9976
>                 URL: https://issues.apache.org/jira/browse/HBASE-9976
>             Project: HBase
>          Issue Type: Bug
>          Components: Client, regionserver
>    Affects Versions: 0.98.0, 0.96.0
>            Reporter: Nicolas Liochon
>            Assignee: Nicolas Liochon
>             Fix For: 0.98.0, 0.96.1
>
>         Attachments: 9976.v1.patch
>
>
> A profiling show that the table name is reponsible for 25% of the memory needed to keep
the region locations. As well, comparisons will be faster if two identical table names are
a single java object.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message