简体繁体 English

NextJs - 某些 API 请求的服务器端渲染 CPU 峰值

[英]NextJs - ServerSide Render CPU spike with certain API request

原文 2022-06-03 07:57:01 0 0 docker/ next.js/ amazon-elastic-beanstalk/ server-side-rendering

We noticed an interesting issue regarding our serverside rendering of our NextJs application.我们注意到一个关于我们的 NextJs 应用程序的服务器端渲染的有趣问题。

The issue occurred when we decided to add fetching of our translation key values (which are fetched via API) on our serverside calls.当我们决定在我们的服务器端调用中添加对翻译键值（通过 API 获取）的获取时，就会出现问题。

We made this decision to reduce CLS and give the user a better overal experience on first load.我们做出这个决定是为了减少 CLS，并在首次加载时为用户提供更好的整体体验。 We didn't think much of it, since it's just another api call being handled returning the json before rendering the page.我们并没有想太多，因为它只是在渲染页面之前处理返回 json 的另一个 api 调用。

Below you see a graph of our cpu usage on AWS, between 10:00 (10AM) and 14:00 (2PM) the fetching of the translation keys was live on production.下面是我们在 AWS 上的 cpu 使用图，在 10:00（上午 10 点）和 14:00（下午 2 点）之间，翻译密钥的获取在生产中进行。 We had to manually restart every 2h in order for the servers to survive (That is the peak you are seeing).我们必须每 2 小时手动重新启动一次，以使服务器能够存活（这是您看到的峰值）。 After 16:00 (4PM) We removed this api call from that specific serverside call and you see that the server is stable. 16:00（下午 4 点）之后，我们从特定的服务器端调用中删除了这个 api 调用，您会看到服务器是稳定的。 From 20:00 (8PM) we enabled an automatic restart to be sure that the servers would survive the night, but as you can see this was not necessary.从 20:00（晚上 8 点）开始，我们启用了自动重启，以确保服务器能够在夜间存活，但正如您所见，这不是必需的。

The API call in question, just returns a JSON object.有问题的 API 调用只返回一个 JSON 对象。 It can contain up to 700lines of values which should be fine as our Product listing page can have a larger responses (up to 10k lines).它最多可以包含 700 行值，这应该没问题，因为我们的产品列表页面可以有更大的响应（最多 10k 行）。 Everything has caching on enabled, so next/static and the api responses.一切都启用了缓存，因此 next/static 和 api 响应。 We were also thinking that it might have something to do with outgoing connections not closing in time.我们还认为这可能与未及时关闭的传出连接有关。 But I am making this post because no one really knows why this is an issue.但我发这篇文章是因为没有人真正知道为什么这是一个问题。

We are running the following setup:我们正在运行以下设置：