[
https://issues.apache.org/jira/browse/ACCUMULO-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817563#comment-13817563
]
Keith Turner commented on ACCUMULO-1859:
----------------------------------------
One thing I never did determine was why DefaultConfiguration.iterator() was so
slow. Looking at the code its probably either the annotation checking its
doing and/or resolving the interpolated properties.
> Conditional Mutation with 1000 conditions is slow.
> --------------------------------------------------
>
> Key: ACCUMULO-1859
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1859
> Project: Accumulo
> Issue Type: Bug
> Components: client, tserver
> Reporter: Keith Turner
> Assignee: Keith Turner
> Priority: Critical
> Fix For: 1.6.0
>
> Attachments: 0001-ACCUMULO-1859-experimental.patch,
> 0002-ACCUMULO-1859-experimental.patch
>
>
> The random walk test for conditional mutations creates a conditional mutation
> with 1000 conditions. I noticed this was really slow.
> I did some further testing using MiniAccumulo and was seeing times around
> 1300ms to 1400ms for this operation (the conditions all checked for absence
> and all data for the tablet was in memory).
> I traced the problem down to parsing the iterator config. Iterating over the
> table config, filtering non iterator props, and parsing was taking a little
> more than a 1ms. I modifed TableConfiguration to cache the iterator props
> and saw my test times drop to 120ms to 130ms.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
