High density robot HD

hello everyone,

I am trying to understand the advantages and disadvantages of high density robots.

As far as I read from the documentation, the advantage is being able to run multiple jobs at the same time on the same vdi, having multiple users.

So the advantage would be a savings in deploying machines, as I no longer need to provision a vdi as the license increases.

The disadvantage, however, relates to the remote desktop session host, which is a paid service from microsoft to allow multiple users simultaneously to connect to the same vdi.

Is this correct, do you have any other thoughts on this?

Thank you

1 Like

Hi @andreus91

Check on the below doc

https://docs.uipath.com/robot/standalone/2023.4/user-guide/high-density-robots

Hope this helps!!

Yes, thank you, as I said, I have already read the documentation.

I opened the thread to share, from those who have already implemented this model, further considerations, advantages and disadvantages.

Hi @andreus91

High-density robots, in the context of Robotic Process Automation (RPA), refer to multiple RPA bots running on a single machine or server. These bots share computing resources to execute automation tasks simultaneously.

High-density robots offer cost-efficiency and resource optimization advantages, making them a viable choice for organizations looking to maximize their RPA investments. However, they also come with challenges related to resource contention and management complexity.

These are the main Advantages and Disadvantages of High Density Robots.

Advantages

  1. Resource Optimization
  2. Reduced Infrastructure Complexity
  3. Cost-Efficiency and Scalability

Disadvantages

  1. Complexity of Management
  2. Limited Resource Scaling
  3. Increased Risk of Failures

Cheers…!

Yes, you are correct. The main advantage of high-density robots is that it allows you to run multiple robots on the same machine with different users, which can save you money on hardware costs. However, it is important to note that the remote desktop session host is a paid service from Microsoft, so you will need to factor that into your costs.

Here is a summary of the advantages and disadvantages of high-density robots:

Advantages:

  • Save money on hardware costs
  • Improve resource utilization
  • Reduce maintenance costs
  • Simplify management

Disadvantages:

  • Requires remote desktop session host license
  • May decrease performance
  • More complex to set up and manage
  • May increase security risks

Whether or not high-density robots are right for you will depend on your specific needs and requirements. If you are looking to save money on hardware costs and improve resource utilization, then high-density robots may be a good option for you. However, it is important to weigh the benefits and drawbacks carefully before making a decision.

Here are some additional things to consider when deciding whether or not to use high-density robots:

  • The type of automation you are performing: Some types of automation are more demanding on resources than others. If you are performing complex automation tasks, then you may need to provision more powerful machines or use fewer robots per machine.
  • The number of robots you need to run: If you need to run a large number of robots, then high-density robots may be a good option for you. However, if you only need to run a few robots, then it may be more cost-effective to provision dedicated machines for each robot.
  • Your security requirements: High-density robots can introduce additional security risks, so it is important to implement appropriate security measures.

Hope this helps

Cheers @andreus91

1 Like

thank you very much.

may decrease performance refer to what specifically?

And one last question, how can I size the hardware on the high density serve considering that as of today I have, for example, 10 robots that can run simultaneously on 2 machines?

Thank you

1 Like

Check this document further for setting up high density robot

https://docs.uipath.com/robot/standalone/2023.4/user-guide/setting-up-windows-server-for-high-density-robots

@andreus91

When multiple robots work simultaneously on one machine, it requires more of the server. Applications might run slower etc.

yep, the thing I’m missing is how much to size the servers in terms of disk capacity, computing power, considering that we will have to run 10 robots on 2 servers.

another question is: at the time when I have 2 nodes (2 servers) and a single machine template with the 2 servers connected, how is the run balanced on the 2 servers handled in the HD robot?

Let me explain better, hypothetical of 10 processes (10 licenses) and then 10 users on 2 servers connected to one machine template.

How, if, for example, 6 jobs are launched, are they split 3 in the first and 3 in the second server dynamically instead of 6 all on the first server resulting in possible overloading of resources?

1 Like

well the amount of performance decrease that you experience will depend on a number of factors, including:

  • The type of automation that you are performing
  • The number of robots that you are running
  • The power of the machines that the robots are running on
  • The network bandwidth that is available

To size your servers for high-density robots, you will need to consider all of these factors. It is also a good idea to start with a smaller number of robots and gradually increase the number of robots that you are running as you monitor the performance of your system.

How is the run balanced on the 2 servers handled in the HD robot?

UiPath Orchestrator uses a load balancer to distribute the load of the robots across multiple servers. This means that when you launch a job, Orchestrator will automatically assign the job to the server with the lightest load.

How are 6 jobs launched, are they split 3 in the first and 3 in the second server dynamically instead of 6 all on the first server resulting in possible overloading of resources?

Yes, the 6 jobs will be split 3 in the first and 3 in the second server dynamically. This is because Orchestrator uses a load balancer to distribute the load of the robots across multiple servers.

You can also configure Orchestrator to use a specific load balancing algorithm. For example, you can configure Orchestrator to use a round robin algorithm, which will distribute the jobs evenly across all of the available servers. Or, you can configure Orchestrator to use a least connections algorithm, which will assign jobs to the server with the fewest active connections.

Cheers @andreus91

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.

@andreus91

I see a deviation here
@Paul_Jacobs pls add ur thoughts on this

1 Like