O365: Use batching during modification

For whatever reason this week the concurrency limit in Graph went way down
for modify, this event impacts the batches.

It turns out graph is crazy. You can put up to 20 requests in a batch, but
during execution they can fail with throttling and need retry.

Experiments suggest 3 is the right number to avoid throttling on modify,
for some reason. Documentation seems wrong, and probably something broke
recently.

Implement batching, run the batch break up sequentially, and limit the
batches to 3. Use batching only for modify operations. GET can still use a
concurrency limit of 5.

Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>

0 files changed, 0 insertions, 0 deletions