[
https://issues.apache.org/jira/browse/ACCUMULO-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14287444#comment-14287444
]
Brian Loss commented on ACCUMULO-3480:
--------------------------------------
Two problems. First, I changed bigTest and set the number of groups to 365 and
the test failed (more than 1000 migrations were generated). Second, I changed
bigTest to numbers more fitting for my intended use, and the test takes a very
long time to run (around 45 seconds).
Here are some profiler numbers from my long run :
{noformat}
balance 95% (46300ms)
populateMigrations 26% (12500ms)
TreeMap.containsKey 11% ( 5500ms)
balanceExtraExpected 16% ( 7700ms)
ColumnKeySet.removeAll 14% ( 7000ms) (this is the Guava table's
ColumnKeySet)
TreeMap.containsKey 14% ( 7000ms)
{noformat}
> GroupBalancer improvements
> --------------------------
>
> Key: ACCUMULO-3480
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3480
> Project: Accumulo
> Issue Type: Bug
> Reporter: Keith Turner
> Assignee: Keith Turner
> Fix For: 1.7.0
>
> Attachments: ACCUMULO-3480-1.patch
>
>
> [~bfloss] made the following comment on ACCUMULO-3439
> bq. The balance method in GroupBalancer does nothing if there are any
> incoming migrations. You probably want to check the incoming migrations and
> only bail out if any of those migrations are for the specific table that the
> GroupBalancer is managing.
> I chatted w/ Brian and he also mentioned that the group balancer should
> record time at the end, and not the beginning.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
