Why is the threshold for Large Page Data set at 128kb?

[ryohiy]

Summary

Hi there,

I was wondering why the warning for Large Page Data is set at a 128kb threshold. Is there a specific reason for choosing this limit?

I tried looking for more information but couldn’t find anything in the documentation. I appreciate any insights you can provide. Thank you!

Additional information

No response

Example

No response

[icyJoseph]

Hi,

I remember exploring this some years ago: #38364 (comment)

It looks like I arrived at the conclusion that it was somewhat arbitrary, yet reasonable. I'll take a stab at it again, but generally, 128kb of page data, amounts to a lot of text to transfer, and a large object allocation when processing.

Edit

• Add warning for large amount of page data #29956

It must have been that PR that lead me to the arbitrary qualifier 😄

[ryohiy]

@icyJoseph

Thank you! I hadn't come across the related discussions, so I appreciate the help! 🚀

[icyJoseph]

No problem. You know you can also change this in the next.config.js file, because sometimes, you'll just have a ton of data and there's no way around that, so one could increase the limit, or perhaps, in other situations even reduce it!

[icyJoseph]

See here, https://github.com/vercel/next.js/blob/canary/packages%2Fnext%2Fsrc%2Fserver%2Fconfig-shared.ts#L1129

So it is, largePageDataBytes within experimental, that you can tweak to your projects requirements:

    largePageDataBytes: 128 * 1000, // 128KB by default

[ryohiy]

@icyJoseph
Thank you so much for your kind and detailed response!
I was able to get the information I needed, so I will go ahead and close this.