Skip to main content

Response Time

When BACKND Function is deployed to the server, the method can be called using the BACKND Base function of the BACKND SDK.
When BACKND Function is called, the response time is method execution time + communication time, and it is less than 300 ms on average. However, response time may be measured to be slower in the following cases:

Cold Start​

When BACKND Function is deployed to the server, it is not activated immediately but is activated when the relevant method is called.
If an inactive method is called, the response time may take about 5,000 ms or more as it is only executed after the method is activated.
Below are cold start cases.

  • When the method is called for the first time after being deployed to the server
  • When the method is called after not being used for a long time
  • When the method is called for the first time after being newly deployed

Warm Start​

If an active method is called, the average response time is 300 ms or less.

Deactivate methods​

An activated method becomes inactive in the following cases:

  • When the method is newly deployed
  • When it has not been used for a long time

Call various BACKND methods within BACKND Function​

In general, calling one or two BACKND methods within the BACKND Function does not have a large effect on response time.
However, if three or more BACKND methods are called within the BACKND Function, response time may be affected.
Since it has to wait for a response to each BACKND method call, the response time becomes slower as the number of BACKND methods called within the BACKND Function increases.

If a method takes a long time to be executed​

As the server responds after completing all calculations, if the logic written by the developer is complex and it takes a long time to execute the method due to the large amount of calculation, it may affect the response time.