Stratusphere Sizing Guide

Please complete this form to see what you will need for your Stratusphere™ deployment. Click on the Calculate button after filling out the blue Stratusphere™ FIT or Stratusphere™ UX operational details.

Which version of Stratusphere do you have?  
     
Pick your product and the VDI Platform on which it will be running: Stratusphere FIT on VMware, Citrix, Microsoft, or Nutanix
Stratusphere UX on VMware, Citrix, Microsoft, or Nutanix

Stratusphere FIT on Amazon Web Services
Stratusphere UX on Amazon Web Services
 
     
How many devices will Stratusphere be monitoring?  
How often will the devices report back to the Hub? min  
     
     
     
     
Enter number of Virtual Hosts for Network Monitoring  
Enter number of Network Collectors per Virtual Host  
Enter Network Collectors Callback Frequency min  
Enter Average Connections/sec estimated cps
     
How many Admins will be using Stratusphere reporting concurrently?  
     
How full should the database get before purging data? (%) %  
Enter the retention period of Detailed Data. days
Enter the retention period of Daily Roll-up Data. days
     
   
   
 
Recommended number of Hub & Database Appliance sets
Recommended number of Hub & Database Appliance sets
Recommended number of Hub Appliances
Recommended number of Hub Appliances
Recommended number of Connector ID (CID) Keys per set keys
Recommended number of Connector ID (CID) Keys per set keys
Recommended number of Connector ID (CID) Keys per Hub keys
Recommended number of Connector ID (CID) Keys per Hub keys
Recommended number of CID Key Collectors per set***
Recommended number of CID Key Collectors per set***
Recommended number of CID Key Collectors per Hub***
Recommended number of CID Key Collectors per Hub***
Recommended number of Network Collectors per set
   
 
  Minimum Performance
CPU (vCPUs) * vCPU vCPU
RAM GB GB
     
Disk Storage **    
(OS) HD 1 GB IOPS
(SWAP) HD 2 GB  
(DB, DB TMP & DB LOG) HD 3 GB IOPS
(Upgrade Image) HD 4 GB  
Totals GB IOPS
     
 
 
  Minimum Performance
CPU (vCPUs) * vCPU vCPU
RAM GB GB
     
Disk Storage **    
(OS) HD 1 GB IOPS
(SWAP) HD 2 GB  
(DB) HD 3 GB IOPS
(DB TMP) HD 4 GB  
(DB LOG) HD 5 GB IOPS
Totals GB IOPS
 
  Minimum Performance
CPU (vCPUs) * vCPU vCPU
RAM GB GB
     
Disk Storage **    
(OS) HD 1 GB IOPS
(SWAP) HD 2 GB  
(DB, DB TMP & DB LOG) HD 3 GB IOPS
(Upgrade Image) HD 4 GB  
Totals GB IOPS
     
 
 
  Minimum Performance
CPU (vCPUs) * vCPU vCPU
RAM GB GB
     
Disk Storage **    
(OS) HD 1 GB IOPS
(SWAP) HD 2 GB  
(DB) HD 3 GB IOPS
(DB TMP) HD 4 GB  
(DB LOG) HD 5 GB IOPS
Totals GB IOPS
 
CPU (vCPUs) * vCPU  
RAM GB  
 
 
 
Disk Storage **    
(OS) HD 1:/dev/sda1 GB IOPS
(SWAP) HD 2:/dev/sdf    GB  
(DB, DB TMP & DB LOG) HD 3:/dev/sdg    GB IOPS
(Upgrade Image) HD 4:/dev/sdh    GB  
Totals GB IOPS
 
 
     
We do not support using a database appliance with AWS since it is not guaranteed to be assigned to the same host as the Hub appliance.

Adjustments have been made to to the Hub sizing requirements to make up for the lack of a database appliance.
 
CPU (vCPUs) * vCPU  
RAM GB  
 
 
 
Disk Storage **    
(OS) HD 1:/dev/sda1 GB IOPS
(SWAP) HD 2:/dev/sdf    GB  
(DB, DB TMP & DB LOG) HD 3:/dev/sdg    GB IOPS
(Upgrade Image) HD 4:/dev/sdh    GB  
Totals GB IOPS
 
 
     
We do not support using a database appliance with AWS since it is not guaranteed to be assigned to the same host as the Hub appliance.

Adjustments have been made to to the Hub sizing requirements to make up for the lack of a database appliance.
   
 
Please use default, out-of-the-box CPU, RAM, and Disk Storage values.

CPU (vCPUs) vCPU  
RAM GB  
Disk Storage GB  
     
   
 
Please use default, out-of-the-box CPU, RAM, and Disk Storage values.

CPU (vCPUs) vCPU  
RAM GB  
Disk Storage GB  
     
 
 
 

CPU (vCPUs) vCPU  
RAM GB  
Disk Storage GB  
     
 
Please use default, out-of-the-box CPU, RAM, and Disk Storage values.

CPU (vCPUs) vCPU  
RAM GB  
Disk Storage GB  
     
   
 
Please use default, out-of-the-box CPU, RAM, and Disk Storage values.

CPU (vCPUs) vCPU  
RAM GB  
Disk Storage GB  
     
   

* Liquidware has the following observations regarding vCPUs:

  1. Liquidware has observed that the hypervisor sometimes does not schedule virtual machines with 4 vCPUs as often as it does for 1 vCPU or 2 vCPU machines. In these circumstances, it has seen performance improve if the appliances are allocated 2 vCPUs.
  2. If the hypervisor is very lightly loaded and has a lot of free unallocated vCPUs available, 4 vCPUs or higher could help improve the overall user experience of the Stratusphere user.


** Liquidware has the following observations regarding Disk Storage:

  1. The disk storage performance numbers noted were observed by Liquidware during internal testing. They represent the average sustained input/output operations per second (IOPS) required while inserting metrics and information (gathered by the Stratusphere Connector ID Keys) into the Stratusphere Database Appliance. Further, these performance values do not include the disk overhead necessary to support the execution of reports, administrative concurrency, or resource-intensive UI and API-based database queries. The numbers presented represent the minimum requirements for acceptable administrative user experience and overall performance of the Stratusphere Architecture.
  2. The sizer assumes capturing the Top 20% of Application Processes using the most amount of resources. The sizer assumes the CID Keys are capturing data 24x7.
  3. If sizing for Amazon Web Services, please note that the AWS storage devices may not be listed in alphabetical order when configuring your Stratsphere Hub AMI. Make sure the AWS label matches the Sizing Guide. For example, "/dev/sdg" is "HD 3", which is to be used for database storage.


*** Liquidware generally recommends high availability for Collectors serving as CID Key Collectors only (not Network Collectors). This is enabled by default. Thus, the Sizing Guide calculations assume high availability for the CID Key Collectors. If high availability is disabled, then environments with less than 8,000 callbacks per hour will only require 1 CID Key Collector rather than the 2 CID Key Collectors we recommend for high availability. The recommendation increases with over 16,000 callbacks per hour.