GitHub user DivineEnder opened a pull request: https://github.com/apache/geode/pull/603
GEODE-3128: Changed the batch size to 1000 when creating AEQFactory * Prevously the batch size was the default 100 * Also added Lucene index overhead tests as performance tests. Currently these tests are ignored because they do not contain an assertions Thank you for submitting a contribution to Apache Geode. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Has your PR been rebased against the latest commit within the target branch (typically `develop`)? - [ ] Is your initial contribution a single, squashed commit? - [ ] Does `gradlew build` run cleanly? - [ ] Have you written or updated unit tests to verify your changes? - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. If you need help, please send an email to dev@geode.apache.org. You can merge this pull request into a Git repository by running: $ git pull https://github.com/DivineEnder/geode feature/GEODE-3128 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/geode/pull/603.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #603 ---- commit d51d650b494b60ffd6a4578c6fc7be3d76ffd705 Author: David Anuta <david.r.an...@gmail.com> Date: 2017-06-19T15:55:34Z GEODE-3128: Changed the batch size to 1000 when creating AEQFactory * Prevously the batch size was the default 100 * Also added Lucene index overhead tests as performance tests. Currently these tests are ignored because they do not contain an assertions ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---