ES|QL version of spatial intersects search slow on some benchmarks #108756
Labels
:Analytics/ES|QL
AKA ESQL
:Analytics/Geo
Indexing, search aggregations of geo points and shapes
>bug
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
v8.15.0
When comparing the three benchmarking tracks: geopoint (point data indexed as geo_point), geopointshape (point dataa indexed as geo_shape) and geoshape (complex geometries indexed as geo_shape), we see that for geopoint and geoshape ES|QL performs somewhat similarly to _search queries. However, for the geopointshape track, ES|QL performs about 100x worse. This performance is as bad as would be expected if the lucene push-down was not being enabled. Since the same queries are used, and the same index configuration, this seems surprising.
ES|QL benchmark results can be seen at https://elasticsearch-benchmarks.elastic.co/#tracks/esql/nightly/default/30d
A summary of queries and results can be seen below:
geoshape
For geoshape we see comparable results, with ES|QL only 44% slower than _search:
geopointshape
For geopointshape things are much, much worse with ES|QL over 100x slower:
geopoint
For geopoint things are reasonable again with ES|QL less than 2x slower:
The text was updated successfully, but these errors were encountered: