Todd Lipcon has posted comments on this change. Change subject: WIP: KUDU-1970: node density integration test ......................................................................
Patch Set 1: (1 comment) http://gerrit.cloudera.org:8080/#/c/6662/1//COMMIT_MSG Commit Message: Line 20: WIP because an itest isn't a great fit; we're not actually testing anything. isn't it a sort of stress test, in that we're testing larger data volumes than other tests do? I've been pondering for years now the idea of changing KUDU_ALLOW_SLOW_TESTS=1 to KUDU_TEST_LENGTH={fast,slow,veryslow}, and this could be the first of the third category, which we might not run pre-commit but could run nightly or post-commit. It could also be named '-bench' as in rpc-bench, and added to the benchmarks script, so we could plot startup time performance, thread count, memory usage, etc, of the test like we plot other numeric metrics from build to build. -- To view, visit http://gerrit.cloudera.org:8080/6662 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ie9b5d01557eb41d386ce92f576ed01ec658e8e7d Gerrit-PatchSet: 1 Gerrit-Project: kudu Gerrit-Branch: master Gerrit-Owner: Adar Dembo <[email protected]> Gerrit-Reviewer: Kudu Jenkins Gerrit-Reviewer: Tidy Bot Gerrit-Reviewer: Todd Lipcon <[email protected]> Gerrit-HasComments: Yes
