Huge performance drop when using translating libraries like i18n-intl or paraglide-js
Unanswered
Himalayan posted this in #help-forum
HimalayanOP
Normally, when I run the build of the fresh Next app I get around 4600 req/s for the homepage.
With paraglide-js or i18n-intl I am getting around 600 which is almost 8x less requests. Which brings us to the Laravel type of performance aka not good at all.
Why this huge drop? I am adding a screenshot which includes a response from the paraglide-js developer who suggested that it is related to the middleware in Next. Any idea what is going on and how to fix this drop? I did a similar test with SvelteKit and later with Nuxt and the drop is almost non-existent with SvelteKit and only 200 - 300 req/s for Nuxt.
With paraglide-js or i18n-intl I am getting around 600 which is almost 8x less requests. Which brings us to the Laravel type of performance aka not good at all.
Why this huge drop? I am adding a screenshot which includes a response from the paraglide-js developer who suggested that it is related to the middleware in Next. Any idea what is going on and how to fix this drop? I did a similar test with SvelteKit and later with Nuxt and the drop is almost non-existent with SvelteKit and only 200 - 300 req/s for Nuxt.
4 Replies
HimalayanOP
Here is the screenshot.
HimalayanOP
Any Next advanced user who could help and pinpoint the culprit of this massive slowdown when using i18n-intl or paraglide-js?
As I said, it doesn't happen in SvelteKit and Nuxt. Only in Next.
HimalayanOP
Could it be related to this? https://github.com/vercel/next.js/issues/38273