Next.js Adventures: Some Blasphemy Against the Holy Image Component
buhalbu.com
2 threads
I’ve felt your pain. We run a Next app on Heroku and we had to disable such component because it was making the app consume in average 500mb of RAM. Our app doesn’t do anything special nor we have many visitors.
Yeah, that's my other pain point - the higher usage of CPU & RAM.
If you believe that the <Image /> component is the finest solution for handling images ever invented, then I suggest you stop reading right now and go find other interesting stuff.