This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
The first thing that typically needs scaling is the workers. It sounds like you're good to get started, but your next move will probably be adding another worker to take the worker load from the server controller/db machine.
There isnt a single clear-cut answer to this question, because how and what you scale really depends on how the Server is being utilized.
That said, what you've described is in line with what I typically guide my customers to do - in almost all situations, Worker Bandwidth is the first constraint a server stack runs into and when you scale out for worker bandwidth, what you're describing is correct.
The attached is a diagram that I use often to explain the process.
I would also add that on VM's you will want to be careful with RAM pooling, as this can cause the appearance of CPU issues, when in fact you just dont have RAM available at the right time. Since most Alteryx Processing is done in-memory (in-db tools excluded), you want to make sure RAM is never a constraint.