Thanks for the info! I have no idea why it’s consuming so much memory on Fly. remix-serve is a simple express server. The build part is just the directory that the express server should serve. We’re not building at runtime.
When testing locally I ran this:
NODE_ENV=production node --inspect-brk --require ./node_modules/dotenv/config ./node_modules/.bin/remix-serve build
That way I could take the memory snapshot and also simulate the same sort of thing that’s happening in production (with the right env vars set etc.).