Cold start

When making the first request you will often notice that ArupCompute is slow to respond, but subsequent requests are quicker. This is called a 'cold-start' and is due to the Azure cloud infrastructure loading the relevant code into memory. When the code is loaded it can then respond to incoming requests quickly. After a certain period of inactivity the code is unloaded from memory. This means Arup does not need to pay for any hosting when libraries are not being used.

NOTE

The ArupCompute roadmap contains a 'warming signal' feature to minimise the impact of cold starts on users. This feature will allow the websites and desktop clients to get ArupCompute to preemptively load libraries when it seems like a user will use them in the near future.