New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Server timing API #683

Open

chaoran-chen opened this issue Mar 1, 2024 · 1 comment

Labels

Member

chaoran-chen commented Mar 1, 2024

The Chrome dev console pointed me to the Server Timing API (web.dev, MDN). It looks very useful, should we implement it?

Chrome dev console screenshot

chaoran-chen added the performance label

Member Author

chaoran-chen commented Mar 5, 2024

For now, I added the following line to the nginx config on the s0 server for LAPIS:

add_header Server-Timing "requestTime;desc=\"Total Request Time\";dur=$request_time, upstreamConnect;desc=\"Upstream Connect Time\";dur=$upstream_connect_time, upstreamHeader;desc=\"Upstream Header Time\";dur=$upstream_header_time, upstreamResponse;desc=\"Upstream Response Time\";dur=$upstream_response_time";

Note: the values are provided in seconds.

Information about the variables can be found in the Nginx documentation.

chaoran-chen mentioned this issue

Aggregated endpoint is slower than expected #684

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment