1e015e6e33
This was previously attempted in #8854. I revived that branch and did some performance testing as was suggested in the comments there. I fixed all the errors, mostly just the rest tests, which needed to have http enabled on the node settings (the global cluster previously had this always enabled). I also addressed the comments from that issue. My performance tests involved running the entire test suite on my desktop which has 6 cores, 16GB of ram, and nothing else was being run on the box at the time. I ran each set of settings 3 times and took the average time. | mode | master | patch | diff | | ------- | ------ | ----- | ---- | | local | 409s | 417s | +2% | | network | 368s | 380s | +3% | This increase in average time is clearly worthwhile to pay to achieve isolation of tests. One caveat is the way I fixed the rest tests is still to have one cluster for the entire suite, so all the rest tests can still potentially affect each other, but this is an issue for another day. There were some oddities that I noticed while running these tests that I would like to point out, as they probably deserve some investigation (but orthogonal to this PR): * The total test run times are highly variable (more than a minute between the min and max) * Running in network mode is on average actually *faster* than local mode. How is this possible!? |
||
---|---|---|
.. | ||
community | ||
groovy-api | ||
java-api | ||
javascript | ||
perl | ||
python | ||
reference | ||
resiliency | ||
river | ||
ruby | ||
README.md |
README.md
The Elasticsearch docs are in AsciiDoc format and can be built using the Elasticsearch documentation build process