Looking for solutions to make Meteor cheaper

Thanks for sharing the idea, I agree that the start of new processes/workers would be something that meteor should support in the core, since adding things on top of the meteor build makes it a little messy for deployment. Also it would be great to be able to define multiple entry points so there can be different “files in the project” that can be started separately without having to create multiple bundles and “orchestrating” everything manually. I know there was a feature request about this at some point, not sure if with Meteor 3 this would be easier to implement.

(Also, I know there was a workaround to create entrypoints by storing files in the private folder, but then imports to npm could fail and generally it was not a perfect solution.)

1 Like

agree with you, could you(or someone here) open an issue about it? then we could, dicuss the DX, prioritize and work on it :smiley:

4 Likes

I created a discussion here: Enables Meteor JS application to run multiple instances of itself to maximize hardware utilization · meteor/meteor · Discussion #13823 · GitHub

4 Likes

Would there be a way to easily detect whether meteor uses the full available amount of processors and resources? I think many have no idea, if there would be some kind of package / simple script to measure and monitor it would give a lot of insight for many people.

Many things read in this topic are highly interesting and also highly technical on the server side which is not common knowledge for many developers.

We might be surprised about the amount of unused resources I guess.

1 Like

If you don’t use the cluster technology you are 100% sure to only use 1 CPU. If you want to use clustering, you have this:

const os = require('os');
const cpuCount = os.cpus().length;
console.log(cpuCount);
// also Node.js v18+
const os = require('os');
const availableProcessors = os.availableParallelism();
console.log(availableProcessors);
2 Likes

But Support ARM on Linux is merged. Is it not working?