Make bulk SAI calls in order for non-OID objects in the bulker API #3159
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.
What I did
Today, the bulker library does not maintain order for non-OID objects. This PR changes it to keep the requested order.
Why I did it
As part of the performance improvement effort, we updated P4Orch route manager to use bulk SAI API. With the current bulker library, it does not maintain the order. For the SDN use case, keeping the route programming order is important (for example, the default route needs to be programmed first to avoid packet drop).
How I verified it
Unit test
Details if related
N/A