Docs: Indicate High memory usage if not installing sharp for image optimization

[gaplo917]

What is the improvement or update you wish to see?

Introduction

Remote image sizes are difficult to guarantee when some users uploaded very large images on the CMS. The very large images will be retrieved by nextjs and served to the frontend.

The default library squoosh will cause the nextjs process a very high memory usage during image optimizations and might crash the whole nextjs container in a limited resource environment.

Thus, the high memory behaviour should be docuementated to increase the necessarity of installing sharp.

Note: Some of our team members can't see observable differences after installing sharp and then remove it immediately.

Suggestion

Indicate high memory usage of squoosh compared with sharp. For example, a single 5000 x 5000 images would consume ~600MB memory while sharp use less than few MB memory only.

Is there any context that might help us understand?

Demo Recording

Without installing Sharp

Three 5000x5000 images will cause 1.8GB memory usage, and the memory jump is linear.

Installed Sharp

The memory usage remains stable.

Does the docs page already exist? Please link to it.

https://nextjs.org/docs/messages/sharp-missing-in-production

[karlhorky]

Wonder if this issue can be replaced by a PR to switch back to sharp, now that @squoosh/cli and @squoosh/lib are unmaintained:

Project no longer maintained

Unfortunately, due to a few people leaving the team, and staffing issues resulting from the current economic climate (ugh), this package is no longer actively maintained. I know that sucks, but there simply isn't the time & people to work on this. If anyone from the community wants to fork it, you have my blessing. The squoosh.app will continue to be supported and improved.

[karlhorky]

@styfle is there already an issue / PR about switching from squoosh back to sharp somewhere?

Eg. A) reverting @Timer's PR below and B) reverting all followup PRs adding back optional sharp support and C) making sharp again a required dependency of Next.js:

• feat(next/image): remove sharp for wasm variant #22253

M1 support (the original reason for switching to squoosh) has been in sharp for a long time now, and there is an initiative to also get WebAssembly support:

• WebAssembly build lovell/sharp#3522

[styfle]

There's no issue tracking it in Next.js because lovell/sharp#3522 hasn't landed yet.

Once it lands then we can look into removing squoosh as the wasm implementation in favor of sharp.

For now, the linked docs in the original post explain the current status.

[karlhorky]

Looks like [email protected] now includes (experimental) WebAssembly support 🙌

• WebAssembly build lovell/sharp#3522 (comment)
• WASM Support lovell/sharp#3336 (comment)

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.