New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimise nextFetchDate to speed up queries to Elasticsearch #452

Closed
jnioche opened this Issue Apr 3, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@jnioche
Member

jnioche commented Apr 3, 2017

The queries in the spouts take longer as the status index gets larger. We use sampling with the aggregation spouts but could also optimise the speed by querying on a nextFetchDate value which would be old enough to minimise the amount of docs on which the aggregations run, while retrieving as many docs as possible.

The same approach could also be used for the collapsing spout.

@jnioche

This comment has been minimized.

Show comment
Hide comment
@jnioche

jnioche Apr 19, 2017

Member

The CollapsingSpout currently resets the Date to now if the number of buckets returned is 0. We could set a minimum number of buckets or a distance to the largest nextFetchDate returned when the sorting is on.

Member

jnioche commented Apr 19, 2017

The CollapsingSpout currently resets the Date to now if the number of buckets returned is 0. We could set a minimum number of buckets or a distance to the largest nextFetchDate returned when the sorting is on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment