I'm trying to understand how autoscaling works and I'd like some clarifications.
When a process group load is calculated is that based on actual CPU load, or is it just computed as busy_processes/total_processes in that group? What I'm trying to figure out is the behavior in the case of the TCP process group, which is let's say configured to spawn a new worker when it reaches 70% load for the TCP worker group. Now consider that this group starts with 5 workers and at some point in time, all 5 workers are busy processing a message. In addition let's consider that the DNS lookup is misconfigured and it takes 3 seconds to get an answer. This means that if the proxy receives 5 messages at a time, all 5 workers will be blocked in a synchronous DNS lookup for 3 seconds, but each using 0% CPU. My question is, in this 3 second time window (when all 5 workers are blocked in waiting for the DNS lookup), if a new request arrives over TCP, will opensips spawn a new TCP worker because all 5 workers are busy and it considers the load to be 100%, or it will do nothing because it uses CPU load which is 0% since all 5 processes are sleeping waiting for the DNS answer? -- Dan _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
