Improve API consumption of _handle_bulk_insert_op
#4091
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.
globalOperations.aggregateList
perform series (usually just 1) of zonal list requests - to stop hittingHeavyWeightReadRequestsPerMinutePerProject
limits;ListRequestsFilterCostOverheadPerMinutePerProjectPerRegion
limits;createTime
range anduser
(both are indexed) into server-side filtering.New approach consumes 0 -
filtered_list_cost_overhead
, while old one was effectively churring (on server side) through all operations.Latency is smaller but not significantly (~2 times improvement) - no thorough sampling has been done.
See: https://cloud.google.com/compute/api-quota#api-rate-limits