There's more...

The number of requests executed within a batch request is capped at 1000.

If you try to execute a batch that is larger than your maximum allowed, an exception will be thrown. However, you can catch the exception, read the maximum allowed number from the exception, and resize your batch accordingly. This MSDN article highlights the code to retrieve the maximum batch size: https://msdn.microsoft.com/en-us/library/jj863631.aspx#fault.

Just like with SQL Server's batching, you'll have to find the sweet spot while tuning your batch parameters. There is a point where increasing the number of requests executed in a batch and the number of parallel executions actually degrades your performance.

As for the request settings implications, the following article highlights the different response scenarios based on the request settings:

https://msdn.microsoft.com/en-us/library/jj863631.aspx#options

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.223.170.63