If thats the time it takes, then thats the time it takes. I have explained the other thread how to try and see if you can execute it faster using the "indexed' option, but it mainly applied when only doing geo search without any other constraint.
How many machines do you have? Is that that single machine? How many docs match the query provided without the geo bounding box filter?
On Tuesday, February 7, 2012 at 12:36 PM, BeyondLimit wrote:
Hi there ,
i have been writing about this issue in the Elasticsearch google
groups , but unfortunately no one address the issue.
So i am posting it again , i guess you guys are not able to see my
older post.
Problem :
Setup 4 core cpu with 24gb of ram .
Index size is 10gb , Using ES latest version
Now when i have no where clause in the query its gives results in no
time say 20 ms. but when i added BoundingBox filter its started giving
result in > 200 ms .
Please correct me if i am wrong , i have used the same example you
guys have mentioned in the Elastic Search (GeoBoundingBoxTests.java).
Do i have to do something else or is this the limitation of ES.
Regards
Prashant