ResDiary 10.18.1 release highlights

Over the past few weeks we've noticed a small number of performance issues when restaurants are at their busiest.To improve performance we've updated the internal API.

Switching WebAPI over to ReadOnly sessions

Over the past few weeks we’ve noticed a small number of performance issues when restaurants are at their busiest. These issues have been occurring when we have received a lot of concurrent requests from the same session,  meaning that the requests are blocking each other.

Most of the concurrent requests from the same session are as a result of ajax requests from javascript code on certain pages of the app that make requests to the internal API( used by the diary application). This internal API needs access to the ASP.NET session in order to complete certain tasks (like authentication) but it doesn’t actually write to the session.

To improve performance we’ve updated the internal API , so that it only asks for read-only access to the session, rather than having to wait for an exclusive lock. This change should allow multiple requests to run in parallel; rather than blocking and causing the request queue on the server to build up to an unmanageable amount.

We will monitor this change on our UK server over the next few days to check whether it is working as planned. If successful, we will then roll it out across all our servers.

Share on: