Receive Side Scaling (RSS) and Windows based Atoms, Clouds and Molecules

Document created by frank_wetzler970218 Employee on Apr 20, 2017Last modified by frank_wetzler970218 Employee on Apr 3, 2018
Version 5Show Document
  • View in full screen mode

For Windows based Atoms, Molecules and Clouds that run on Windows 2008 and 2012 operating systems it is recommended that Receive Side Scaling be enabled. Enabling RSS may lead to measurable performance improvements depending upon the network load being process by the servers hosting the Boomi Integration Environment. Windows 2008 and 2012 R2 server implementations will only allocate a single cpu to handle the network processing load on the servers NIC card if RSS is disabled. As the communication traffic load increases, this solution does not scale well and can negatively impact the overall performance of the Boomi Integration Environment. By enabling RSS the network adapters is able to distribute the network processing load across multiple processor cores in multi-core computers. The distribution of this processing makes it possible to support higher network traffic loads than would be possible if only a single core were to be used and can measurable improve the performance of the Cloud/Molecule. 



Reference Guide Articles

Here are some links to our Reference Guide, which you may find useful when using and configuring RSS.


Example scenarios on how to configure RSS

Scenario 1 - How do I configure RSS on Windows 2012?

Configure RSS on Clouds/Molecules using Windows 2012 R2 by following the guidance provided within Virtual Receive-side Scaling in Windows Server 2012 R2 


Scenario 2 - How do I configure RSS on Windows 2008?

Configure RSS on Clouds/Molecules using Windows 2008 by following the guidance provided within Enabling Receive Side Scaling


Scenario 3 - Virtual RSS 

Configure RSS on Clouds/Molecules using Windows Server (Semi-Annual Channel), Windows Server 2016 Virtual Receive Side Scaling (vRSS)


Common Errors

PerfMon indicator of a potentially inefficient RSS configuration

An indication that RSS is disabled or not configured optimally would be a high number of Interrupts processed by one or more of the processors. The level of CPU interrupts can be seen using a tool like PerfMon. PerfMon can produce a html file call report.html. The high number of Interrupts can be seen as shown in a screen shot below taken from a sample report.html file. This is an indication that the system maybe experiencing a high number of interrupts due to the network traffic load. 





Is RSS a potential issue for Linux based environment ?

In general RSS is enabled by default for Linux based systems. However this can be verified using techniques described for your particular Linux implementation. For example, for Red Hat Linux follow the steps outlined in 8.6. Receive-Side Scaling (RSS) to verify RSS is enabled in a optimal manner.

Who should make these types of changes ?

Unless you are a intimately aware of your operating system and details of your server configuration it would be best practice to work with your network team before making the changes described in this article as these are low level changes that may impact all applications hosted on the environment. 


2 people found this helpful