workbook calc speed and general performance with graph api

Question

when using graph api with an excel workbook to calculate values, how do we manage speed?

it's not clear how this is working in the back end, but i figure it is loosely tied to azure. however, i don't see a way to add resources in azure to the graph api.

is there a way to "buy" performance in any way?

also, are there any limitations as to the volume of calculations you can run through the graph api in this way? one or two calcs seem fine, but what about hundreds/thousands/millions?

since it's presumably opening excel in the background somehow, updating the spreadsheet, then calculating, is this all happening on the same machine, or is it different/separate machines operating in parallel? (assuming i have persistchanges=false)

Answer 1

Hi @ThorCRE , At present, the documentation does not point out that there is a clear limit on the amount of calculation.
You can communicate with the back-end engineer by opening a support ticket, and the back-end engineer can view the back-end data operation status.

If the persistchanges=false, this means API calls are made without session information.
The Excel server must find the server's copy of the workbook every time to perform the operation, so this is not an efficient way to call the Excel API. It is suitable for making a one-time request.
At present, the document proposes to add session header to increase computing performance, I hope this can help you.
Documentation: https://learn.microsoft.com/en-us/graph/api/resources/excel?view=graph-rest-1.0

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.