Advice on update-callback performance and state management

Posted by: joni.dewinter on 19 October 2021, 5:39 pm EST

    • Post Options:
    • Link

    Posted 19 October 2021, 5:39 pm EST


    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 ( 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!

    Kind regards


  • Posted 20 October 2021, 10:26 pm EST

    Hi Joni,

    We are sorry but without any sample, it would be hard to comment on the nature of the issue. Could you please provide a working sample that demonstrates the issue so that we could investigate the issue and help you accordingly?



  • Posted 25 January 2022, 3:37 am EST

    Hello Avinash

    Sorry for the late reply.

    The main reason for long loading times was our approach of manually calling Update-method after every data change to achieve immediate evaluation of conditional formattings (see

    Those calls are much heavier than the built-in automatic callbacks.

    We eventually built a custom (mostly front-end) mechanism to render conditional formattings after every automatic callback.

    This way, we achieved acceptable load times.

    This topic can be closed.

    Kind regards


Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels