Increase chunk size for stats endpoints #93
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
job.items.stats()
takes double time comparing to a plain request to the same endpoint - it was reported by @immerrr, but I have just found some time to prepare a patch, please take a look.In a word, the problem is that current
apiget
logic always iterates through a response body with 512B chunks returning an iterator with JSON lines. And if there's a large single JSON line in a response (about ~800KB in the example above), it will take significant time to get it and split the whole content to a set of lines by a delimiter.There're different solutions to this problem, but the most straightforward one is just increasing a chunk size when working with the stats endpoints.