Skip to content
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.

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

5MB -> 4MB body size limit #26887

Merged
merged 2 commits into from
Jul 2, 2021
Merged

Conversation

padmaia
Copy link
Member

@padmaia padmaia commented Jul 2, 2021

This decreases the body size limit that triggers a warning from 5MB -> 4MB, which provides a little more wiggle room. Certain things like using base64 on body, headers, path, etc can cause the response to be larger than initially calculated.

Initial PR: #26831

ijjk
ijjk previously approved these changes Jul 2, 2021
Copy link
Member

@styfle styfle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@ijjk
Copy link
Member

ijjk commented Jul 2, 2021

Stats from current PR

Default Build (Increase detected ⚠️)
General
vercel/next.js canary padmaia/next.js fix/warn-on-4mb-response Change
buildDuration 12.4s 12.5s ⚠️ +101ms
buildDurationCached 3s 3.1s ⚠️ +52ms
nodeModulesSize 49.3 MB 49.3 MB
Page Load Tests Overall increase ✓
vercel/next.js canary padmaia/next.js fix/warn-on-4mb-response Change
/ failed reqs 0 0
/ total time (seconds) 2.256 2.229 -0.03
/ avg req/sec 1107.91 1121.69 +13.78
/error-in-render failed reqs 0 0
/error-in-render total time (seconds) 1.232 1.23 0
/error-in-render avg req/sec 2028.41 2032.06 +3.65
Client Bundles (main, webpack, commons)
vercel/next.js canary padmaia/next.js fix/warn-on-4mb-response Change
359.HASH.js gzip 3.09 kB 3.09 kB
framework-HASH.js gzip 42 kB 42 kB
main-HASH.js gzip 20.2 kB 20.2 kB
webpack-HASH.js gzip 1.49 kB 1.49 kB
Overall change 66.9 kB 66.9 kB
Legacy Client Bundles (polyfills)
vercel/next.js canary padmaia/next.js fix/warn-on-4mb-response Change
polyfills-HASH.js gzip 31.1 kB 31.1 kB
Overall change 31.1 kB 31.1 kB
Client Pages
vercel/next.js canary padmaia/next.js fix/warn-on-4mb-response Change
_app-HASH.js gzip 803 B 803 B
_error-HASH.js gzip 3.18 kB 3.18 kB
amp-HASH.js gzip 526 B 526 B
css-HASH.js gzip 329 B 329 B
hooks-HASH.js gzip 903 B 903 B
index-HASH.js gzip 263 B 263 B
link-HASH.js gzip 1.65 kB 1.65 kB
routerDirect..HASH.js gzip 322 B 322 B
withRouter-HASH.js gzip 320 B 320 B
bb14e60e810b..30f.css gzip 125 B 125 B
Overall change 8.42 kB 8.42 kB
Client Build Manifests
vercel/next.js canary padmaia/next.js fix/warn-on-4mb-response Change
_buildManifest.js gzip 390 B 390 B
Overall change 390 B 390 B
Rendered Page Sizes
vercel/next.js canary padmaia/next.js fix/warn-on-4mb-response Change
index.html gzip 523 B 523 B
link.html gzip 535 B 535 B
withRouter.html gzip 515 B 515 B
Overall change 1.57 kB 1.57 kB

Webpack 4 Mode (Decrease detected ✓)
General
vercel/next.js canary padmaia/next.js fix/warn-on-4mb-response Change
buildDuration 11.1s 10.9s -162ms
buildDurationCached 4.5s 4.4s -57ms
nodeModulesSize 49.3 MB 49.3 MB
Page Load Tests Overall decrease ⚠️
vercel/next.js canary padmaia/next.js fix/warn-on-4mb-response Change
/ failed reqs 0 0
/ total time (seconds) 2.258 2.22 -0.04
/ avg req/sec 1107.02 1125.92 +18.9
/error-in-render failed reqs 0 0
/error-in-render total time (seconds) 1.207 1.244 ⚠️ +0.04
/error-in-render avg req/sec 2072.06 2009.6 ⚠️ -62.46
Client Bundles (main, webpack, commons)
vercel/next.js canary padmaia/next.js fix/warn-on-4mb-response Change
14.HASH.js gzip 3.11 kB 3.11 kB
677f882d2ed8..HASH.js gzip 13.4 kB 13.4 kB
framework.HASH.js gzip 41.8 kB 41.8 kB
main-HASH.js gzip 8.07 kB 8.07 kB
webpack-HASH.js gzip 1.19 kB 1.19 kB
Overall change 67.5 kB 67.5 kB
Legacy Client Bundles (polyfills)
vercel/next.js canary padmaia/next.js fix/warn-on-4mb-response Change
polyfills-HASH.js gzip 31.3 kB 31.3 kB
Overall change 31.3 kB 31.3 kB
Client Pages
vercel/next.js canary padmaia/next.js fix/warn-on-4mb-response Change
_app-HASH.js gzip 1.07 kB 1.07 kB
_error-HASH.js gzip 3.83 kB 3.83 kB
amp-HASH.js gzip 531 B 531 B
css-HASH.js gzip 333 B 333 B
hooks-HASH.js gzip 910 B 910 B
index-HASH.js gzip 227 B 227 B
link-HASH.js gzip 1.64 kB 1.64 kB
routerDirect..HASH.js gzip 295 B 295 B
withRouter-HASH.js gzip 292 B 292 B
e025d2764813..52f.css gzip 125 B 125 B
Overall change 9.26 kB 9.26 kB
Client Build Manifests
vercel/next.js canary padmaia/next.js fix/warn-on-4mb-response Change
_buildManifest.js gzip 418 B 418 B
Overall change 418 B 418 B
Rendered Page Sizes
vercel/next.js canary padmaia/next.js fix/warn-on-4mb-response Change
index.html gzip 567 B 567 B
link.html gzip 580 B 580 B
withRouter.html gzip 559 B 559 B
Overall change 1.71 kB 1.71 kB
Commit: a4fbc63

@kodiakhq kodiakhq bot merged commit b8f3a6d into vercel:canary Jul 2, 2021
@padmaia padmaia deleted the fix/warn-on-4mb-response branch July 7, 2021 19:53
flybayer pushed a commit to blitz-js/next.js that referenced this pull request Aug 19, 2021
This decreases the body size limit that triggers a warning from 5MB -> 4MB, which provides a little more wiggle room. Certain things like using base64 on body, headers, path, etc can cause the response to be larger than initially calculated. 

Initial PR: vercel#26831
@vercel vercel locked as resolved and limited conversation to collaborators Jan 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants