[ https://issues.apache.org/jira/browse/HBASE-16679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15517194#comment-15517194 ]
Appy commented on HBASE-16679: ------------------------------ Committing. Ran above failing/timed out tests locally. TestBlockEvictionFromClient is flaky while other tests timed out probably becuase of java.lang.RuntimeException: java.lang.OutOfMemoryError. The changes in this patch doesn't affect other tests since these pressure aware controllers are not enabled by default. {noformat} ------------------------------------------------------- T E S T S ------------------------------------------------------- Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 Running org.apache.hadoop.hbase.namespace.TestNamespaceAuditor Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 141.852 sec - in org.apache.hadoop.hbase.namespace.TestNamespaceAuditor Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 Running org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDeletes Tests run: 44, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 91.247 sec - in org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDeletes Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 Running org.apache.hadoop.hbase.wal.TestBoundedRegionGroupingStrategy Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 38.128 sec - in org.apache.hadoop.hbase.wal.TestBoundedRegionGroupingStrategy Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 Running org.apache.hadoop.hbase.wal.TestWALSplit Tests run: 32, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 59.011 sec - in org.apache.hadoop.hbase.wal.TestWALSplit Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 Running org.apache.hadoop.hbase.wal.TestWALSplitCompressed Tests run: 32, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 57.131 sec - in org.apache.hadoop.hbase.wal.TestWALSplitCompressed Results : Tests run: 130, Failures: 0, Errors: 0, Skipped: 0 {noformat} > Flush throughput controller: Minor perf change and fix flaky > TestFlushWithThroughputController > ---------------------------------------------------------------------------------------------- > > Key: HBASE-16679 > URL: https://issues.apache.org/jira/browse/HBASE-16679 > Project: HBase > Issue Type: Bug > Reporter: Appy > Assignee: Appy > Attachments: HBASE-16679.master.001.patch, > HBASE-16679.master.002.patch, HBASE-16679.master.003.patch > > > Minor perf change: > Calculate maxThroughputPerOperation outside of control() since start()&end() > are called only once per operation, but control can be called > hundreds/thousands of time. > Flaky test: > Problems in current test: > - writes only 2.5MB each iteration but control triggers sleep only every 1Mb > write (decided by HBASE_HSTORE_FLUSH_THROUGHPUT_CONTROL_CHECK_INTERVAL). > Either increase data written in each batch or decreasing this threshold for > better throughput control. > - We shouldn't be timing table disable/delete/create and populating data in > throughput calculations. > See the differences below. > With patch (total data written 30M) > run 1: > Throughput is: 1.0113841089709052 MB/s > Throughput w/o limit is: 14.665069580078125 MB/s > With 1M/s limit, flush use 29683ms; without limit, flush use 2130ms > run 2: > Throughput is: 1.0113841089709052 MB/s > Throughput w/o limit is: 14.665069580078125 MB/s > With 1M/s limit, flush use 29674ms; without limit, flush use 2027ms > Without patch (total data written 25M) > run 1: > Throughput is: 0.921681903523776 MB/s > Throughput w/o limit is: 4.06833346870301 MB/s > With 1M/s limit, flush use 27189ms; without limit, flush use 6159ms > run 2: > Throughput is: 0.9422982728478803 MB/s > Throughput w/o limit is: 4.047858424942981 MB/s > With 1M/s limit, flush use 26594ms; without limit, flush use 6190ms -- This message was sent by Atlassian JIRA (v6.3.4#6332)