Hi, I noticed MultiEmail/backend has a concrete Node.js path where a small benchmark could be useful. MultiEmail/backend is a Node.js/Express TypeScript backend for an email-management product, with database connection, mail delivery, auth, logging, and API routes.
Evidence I checked:
- package.json uses node/ts-node-dev scripts
- src/app.ts starts Express with process.env.PORT and Mongoose connection.
A low-risk next step would be: Run one existing API startup or smoke-test path under Bun and compare RSS memory, cold start, and p95 request latency before considering a runtime change. For context, this Battle link compares the same tradeoff.
Hi, I noticed
MultiEmail/backendhas a concrete Node.js path where a small benchmark could be useful. MultiEmail/backend is a Node.js/Express TypeScript backend for an email-management product, with database connection, mail delivery, auth, logging, and API routes.Evidence I checked:
A low-risk next step would be: Run one existing API startup or smoke-test path under Bun and compare RSS memory, cold start, and p95 request latency before considering a runtime change. For context, this Battle link compares the same tradeoff.