Details
-
Bug
-
Resolution: Unresolved
-
Major
-
7.1.2
-
7.1.2
-
Untriaged
-
1
-
Unknown
Description
There is a drop in the latency from the last 7.1.1 build and 7.1.2 builds for geo polygon queries.
The current geo polygon queries returns a very small number if hits.
Hence to confirm that the behaviour persists , I have tested this again by utilising the data points used for bounding box.
I am still seeing an increase in the latency for the geo polygon test.
I also ran the throughput test for the same, with the data points used for bounding box.
Please find the data of the tests run on 7.1.1 and 7.1.2 run with bounding box points below:
Test setup : 1M documents spread over 1 scope 100 collections
Latency :
Test description | 7.1.1-3170 | 7.1.2-3419 |
Bounding box 80% latency | 141 ms | 44.71 ms |
Geo polygon 80% latency | 143 ms | 311 ms |
Test description | 7.1.1-3170 | 7.1.2-3419 |
Bounding box 95% latency | 174 ms | 54.07 ms |
Geo polygon 95% latency | 180 ms | 331 ms |
Links to the latency jobs:
Bounding box:
Build | Link to the job |
7.1.1 | http://perf.jenkins.couchbase.com/job/atlas_collections/6780/ |
7.1.2 | http://perf.jenkins.couchbase.com/job/atlas_collections/7422/ |
Polygon :
Build | Link to the job |
7.1.1 | http://perf.jenkins.couchbase.com/job/atlas_collections/7715/ |
7.1.2 | http://perf.jenkins.couchbase.com/job/atlas_collections/7719/ |
Throughput :
Test description | 7.1.1-3170 | 7.1.2-3419 |
Bounding box Throughput | 98.68 queries/sec | 463 queries/sec |
Geo polygon Throughput | 102 queries/sec | 460 queries/sec |
Links to the job:
Bounding box:
Build | Link to the job |
7.1.1 | http://perf.jenkins.couchbase.com/job/atlas_collections/7722/ |
7.1.2 | http://perf.jenkins.couchbase.com/job/atlas_collections/7721/ |
Polygon :
Build | Link to the job |
7.1.1 | http://perf.jenkins.couchbase.com/job/atlas_collections/7723/ |
7.1.2 | http://perf.jenkins.couchbase.com/job/atlas_collections/7720/ |