RackConnect Operational Limits


This article details the recommended RackConnect Operational Limits when building multiple Next Gen Cloud Servers via the Cloud Servers API.  Note: As performance enhancements are made to next gen Cloud Servers and RackConnect, these results are expected to improve over time. Please keep in mind that all of these results only apply to next gen Cloud Servers.

IMPORTANT: Please note that these limits are guidelines and may not exactly match what is possible in your environment.  Some variables that can affect the limits for your environment include:

  • The number of RackConnect Network Policies active in your environment
  • The type of Net Device(s) you are using with RackConnect

Please view the RackConnect Network Device Comparison article for details on the performance capabilities associated with each of the Network Devices supported by RackConnect.

RackConnect Operational Limits
API Limits

Maximum Number of Total RackConnected Cloud Servers when bursting

500

API: Optimal number of concurrent builds (bursting):

50

API: Optimal time delay between builds:

3 seconds

API: Optimal time delay between groups of builds?

Once All Deployed

Linux Limits

Total Potential 512 MB Linux Builds Per Hour (bursting 50 at a time):

150 *

Potential Time to Build 100 (512 MB) Linux Cloud Servers (bursting 50 at a time):

40 min *

Windows Limits

Total Potential 1 GB Windows Builds Per Hour (bursting 50 at a time):

100 *

Potential Time to Build 100 (1 GB) Windows Cloud Servers (bursting 50 at a time):

60 min *

* NOTE: These values are estimates and may not always match your results.

 

LEGEND

Bursting: This term refers to the act of building multiple cloud servers simultaneously via utilization of the Cloud Servers API.  We tested bursting 1, 10, 30, 50, 75, and 100 cloud servers at a time to obtain the results described in this article.

Maximum Number of RackConnected Cloud Servers: The maximum amount of cloud servers you can deploy in your environment before you can expect to begin receiving consistent RackConnect deployment failures.  If you need to deploy more than this amount of cloud servers, we highly recommend contacting your RackConnect Support Team first.  Note: Not all customer environments (Net Devices) will be capable of handling 500 active cloud servers adequately.

API: Optimal number of concurrent builds (bursting): The maximum number of cloud servers you should burst at the same time.  Exceeding this value may lead to a degradation in performance or build errors/failures.

API: Optimal time delay between builds: The minimum amount of time you should wait between cloud server builds.  This applies even between cloud servers built during a single bursting process.  Exceeding this value may lead to a degradation in performance or build errors/failures.

API: Optimal time delay between groups of builds: After bursting a group of cloud servers, the amount of time you should wait before bursting another group of cloud servers.  The "Once All Deployed" time delay signifies that after bursting a group of cloud servers, you should wait until that group is fully deployed with RackConnect before attempting to burst another group of cloud servers.

Total Potential Linux/Windows Builds Per Hour (bursting 75 at a time): The total amount of Linux/Windows cloud servers you can expect to build in an hour by bursting 75 cloud servers, waiting for them to fully deploy with RackConnect, then immediately bursting 75 more cloud servers, repeating this same bursting process for a full hour.

Potential Time to Build 100 Linux/Windows Cloud Servers: The total amount of time you can expect it to take to build 100 Linux/Windows Cloud Servers by bursting 75 cloud servers, waiting for them to fully deploy with RackConnect, then immediately bursting 25 more cloud servers.

 

 SUMMARY OF FINDINGS

 These findings indicate:

  • If you need to create more than 500 cloud servers in your RackConnect environment, we recommend contacting your RackConnect Support Team first.  Due to the time requirements when deploying cloud servers above 500, it may only be feasible for static environments that will not be changing often.
  • For the best results, there should always be a 3 second time delay between API build calls when building multiple cloud servers at once.
  • For the best results, you should burst no more than 50 cloud servers at once (with a 3 second delay between builds), wait for them to all go into a RackConnect “Deployed” status, then burst no more than 50 more, repeating the same bursting process until the desired number of cloud servers is reached.
  • The "Once All Deployed" time delay signifies that after bursting a group of cloud servers, you should wait until that group is fully deployed with RackConnect before attempting to burst another group of cloud servers.
  • As long as the limits detailed above are followed, there should not be a significant time difference, normally less than 20%, between building smaller and larger cloud server flavors.

 

For further information on utilizing the APIs available, please visit the following links:

Next gen Cloud Servers API documentation

The RackConnect API

How to programmatically determine the RackConnect automation status of you cloud servers



Was this content helpful?




© 2011-2013 Rackspace US, Inc.

Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License


See license specifics and DISCLAIMER