So I'm implementing work queue with RabbitMQ in NodeJS. The consumer is a child process and I plan to fork new ones as need arises, but I read in the official documentation that :
Because of the additional resource allocations required, spawning a large number of child Node.js processes is not recommended.
So should I stick with only a few of child processes as consumers or is there any flaw in my approach?
Btw, one guy told me to check this out. Haven't tried it out, but it seems using threads is more resource-efficient than forking new child process *shrugs*
Thanks~
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "rabbitmq-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rabbitmq-users/pcynjX5BUEo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rabbitmq-user...@googlegroups.com.