Posted 19 October 2021, 5:39 pm ESTHello
In an ASP.NET MVC 5 application, using Spread.NET 14, we found out that as sheets become larger and more complex, the update-callback quickly becomes heavy.
In our case, the call may take up to 1-1.5 seconds and contain a response payload of almost 1 MB.
We are heavily reliant on caching to ensure no remote calls (database, REST api's) need to be made during those callbacks.
We have read the documentation on state management (https://www.grapecity.com/spreadnet/docs/v14/online-asp/spweb-statemgmt.html) and chose for the "session state" option, but this only improved the performance by a few 100ms.
Is there any way we could improve the callback performance to have a more fluent, Excel-like experience with (almost) immediate serverside evaluation?
Could the choice of state management have any impact on this?
Thanks in advance!