Best practice for 30-40 concurrent commands

[zoell]

I am having an experiment, I need to run the same command like 30 times at the same time (coming in via multiple requests). How this daemon will be able to handle this? Should I configure 30 child instances in the config file for this? What if I send in more requests like 40 requests while the max child is 30?

[Gutza]

It's probably best to experiment a bit before deciding, because the optimal solution depends on multiple factors – your server's performance, the amount of setup needed before actually running the command (and how much of the setup you can reuse), how CPU-intensive the commands are, how memory-intensive they are, and what your server is also doing at the same time.

[zoell]

Thanks. I am actually asking because over a couple of days period my whole server application is getting slower. And what I do is basically I am doing an exec on the octave binary 40 times every 3 minutes so during a day is it spawning like ~20k times. How is octave daemon actually works? How is it connecting to the octave process? (I am using node.js, just looking for alternative methods to connect to octave without starting it up every time)