I’m trying to save 1500 users, and the password hashing is killing my overall performance. The CPU is in 100% always.
Currently, I passed this task to a job (vsivsi-job-collection) with a setTimeout, but is useless… or the job takes too much time, or meteor takes too long to the other users.
Do you have any solution to this, for a single-core server?
what you could do is write a second Meteor app or maybe just a simple node worker who does this stuff for you. then you only need to find a proper way on to restrict this separate node process to xy% of the CPU.