6 ms·
I see CPU mentioned a bit, but nothing about memory. It seems like 128 MB isn't enough to run Nuxt.js (Vue server-side rendering), but it would be awesome to be
by crisscrosscrash 6y ago
I see CPU mentioned a bit, but nothing about memory. It seems like 128 MB isn't enough to run Nuxt.js (Vue server-side rendering), but it would be awesome to be able to run that (or Next.js for React) at the edge. I haven't actually tried yet on Workers, but they seem to recommend 512 MB memory for App Engine for example.
Are Cloudflare's machine sizes unsuitable for being able to offer more memory as an option?
- eastdakota 6y agoWe will allow in the future the ability to use larger memory allocations.
- crisscrosscrash 6y agoAny rough guesses on when that could happen? Weeks, months, or next year? Depending on the plans, I'd consider waiting for a Workers-based solution for an upcoming project instead of working on a Cloud Run based deployment.
- eastdakota 6y agoIt’s a configuration change that I believe we can support on a per-user basis today. Encouraged Workers team to follow up here and see if we can get you setup on beta.
- alyson-cabral 6y agoWill you sign up for the beta at https://www.cloudflare.com/workers-unbound-beta/ https://www.cloudflare.com/workers-unbound-beta/ linking to this post? Me or my team will follow-up directly to understand your use case and see if it's a good fit.
- austinpena 6y agoThis is a genuine question, why run a database bound application at the edge? Why not just cache HTML on the edge when you can and run the application traditionally?
- thegagne 6y agoReasons I would want to: 1. To eliminate a layer of application/server/network management (especially if you have complex infra). 2. To get “free” application high availability. 3. To integrate with other stuff on the edge (auth/identity). 4. To serve as a central query aggregator from multiple sources.
- austinpena 6y agoMakes plenty of sense. Thank you!