Replies: 3 comments
-
|
@Likith101 would you look into this please. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
We’re still exploring a few possible improvements in this area, such as chunking strategies and broader use of shape indexes. That said, there aren’t any confirmed patches or active PRs at the moment that specifically guarantee further latency reductions for GeoShape queries. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Is there anything specific I could work on to help out? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Earlier I opened issue #2210 regarding issues with slow GeoShapeQuery times, which seems to have been mostly fixed with release v2.5.3. However, I'm still getting slow query times somewhat similar to what was seen in issue #2114, though a bit shorter.
Repeating the first test using the same code as earlier, just using Bleve 2.5.3:
Is there more work on this in the pipeline? Alternatively, could someone point me in the right direction as to what needs to be improved? I'd be able to work on a patch for this issue if that would be alright.
The test code remains the same, just upgraded the version of Bleve:
https://github.com/tmdigert/simple-bleve-search
Beta Was this translation helpful? Give feedback.
All reactions