You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Throughout the measurements conducted on EdgeNet, each cachecash-curl request has a delay of 700-800 milliseconds on average to get the first bundle from the publisher to the client, without any exception. The observations show that this value varies up to 8 seconds. However, the client can retrieve other bundles from the publisher around 100-150 milliseconds.
It indicates an implementation issue that causes an initial start time while getting the first bundle. This issue affects TTFB desperately badly, thus the user experience.
The implementation of gRPC services may cause this kind of issue. In The gRPC handling time of the ClientPublisher service, the 99th and 90th percentile of requests point out long handling times, but it seems OK when I look at the 50th percentile.
The text was updated successfully, but these errors were encountered:
Throughout the measurements conducted on EdgeNet, each
cachecash-curl
request has a delay of 700-800 milliseconds on average to get the first bundle from the publisher to the client, without any exception. The observations show that this value varies up to 8 seconds. However, the client can retrieve other bundles from the publisher around 100-150 milliseconds.It indicates an implementation issue that causes an initial start time while getting the first bundle. This issue affects TTFB desperately badly, thus the user experience.
The implementation of gRPC services may cause this kind of issue. In The gRPC handling time of the
ClientPublisher
service, the 99th and 90th percentile of requests point out long handling times, but it seems OK when I look at the 50th percentile.The text was updated successfully, but these errors were encountered: