[
https://issues.apache.org/jira/browse/HBASE-15082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092540#comment-15092540
]
Sean Busbey commented on HBASE-15082:
-------------------------------------
I think now that we can see how long steps take, maybe we can back off of "run
all the tests for both JVM versions".
If you look at the [trends for the old
job|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-HBASE-Build-deprecated/buildTimeTrend],
we'd regularly spend ~200 minutes on builds for a single JVM. Presumably
because we'd always test hbase-server regardless of where the change was.
> Fix merge of MVCC and SequenceID performance regression
> -------------------------------------------------------
>
> Key: HBASE-15082
> URL: https://issues.apache.org/jira/browse/HBASE-15082
> Project: HBase
> Issue Type: Sub-task
> Components: Performance
> Reporter: stack
> Assignee: stack
> Priority: Critical
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: 15082.patch, 15082v2.patch, 15082v2.txt, 15082v3.txt,
> 15082v4.patch, 15082v5.patch, 15082v6.patch, 15082v7.patch
>
>
> This is general fix for increments (appends, checkAnd*) perf-regression
> identified in the parent issue. HBASE-15031 has a narrow fix for branch-1.1
> and branch-1.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
