Liquidware Logo

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.

① Stratusphere Version:
② Stratusphere Product: UX            FIT
③ VDI Platform:
   
Data Collection Settings    
How many devices will Stratusphere be monitoring?  
How often will the devices report back to the Hub? min  

▶  Customize Database Sizing by Feature (Optional)

Use the following options to calculate your size requirements based on your custom configuration in Hub Administration > Connector ID Keys > Connector ID Key Properties.

Required  
Summary KB
Process Stats KB
   
Optional  
  Browser Stats KB
  Event Logs (detail only) KB
  File Folder Stats KB
  Login/Logoff Stats KB
  Machine Health Stats KB
  Machine Location Stats KB
  Process Network Details KB
  Process Optimizer KB
  Process Write Stats (Depth=4) KB
  Profile Container Stats KB
  Remote Network Latency Tests KB
  Speed Test Stats (M-F, 4 hours) KB
  Trace Route Stats KB
  User Sentiment Surveys (DEX) (detail only) KB
 
Connector ID Key Detail Size Per Callback KB
Daily Rollup Space Per Machine KB


Note: Detailed Data for Event Logs and User Sentiment Surveys is stored in the database but is not summarized. Therefore, changes in the Event Logs or User Sentiment Surveys settings will not impact the Daily Rollup Space requirement.

     
How many Admins will be using Stratusphere reporting concurrently?  
>Will the Machine Location feature be enabled?  
     
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
     
Optional Network Monitoring - Most deployments do not add additional monitors.    
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
     
   
   
Recommended Appliances  
Recommended number of Hub & Database Appliance sets
Recommended number of Connector ID (CID) Keys per set keys
Recommended number of CID Key Collectors per set***
Recommended number of Network Collectors per set
   
   
   
Hub Appliance Requirements
 
  Minimum Performance
CPU (vCPUs) * vCPU vCPU
RAM GB GB
     
Disk Storage **    
(OS) HD 1 GB fixed IOPS
(SWAP) HD 2 GB fixed  
(DB, DB TMP & DB LOG) HD 3 GB IOPS
(Upgrade Image) HD 4 GB  
Totals GB IOPS
     
     
Important: Liquidware recommends using high-end processors, 3 GHz or higher, released within the last couple of years. Liquidware does not recommend using CPUs that are more than 3 years old.
 
Database Appliance Requirements
 
  Minimum Performance
CPU (vCPUs) * vCPU vCPU
RAM GB GB
     
Disk Storage **    
(OS) HD 1 GB fixed IOPS
(SWAP) HD 2 GB fixed  
(DB) HD 3 GB IOPS
(DB TMP) HD 4 GB  
(DB LOG) HD 5 GB IOPS
Totals GB IOPS
     
Important: Liquidware recommends using high-end processors, 3 GHz or higher, released within the last couple of years. Liquidware does not recommend using CPUs that are more than 3 years old.
Hub Appliance Requirements
 
  Minimum Performance
CPU (vCPUs) * vCPU vCPU
RAM GB GB
     
 
 
 
Disk Storage **    
(OS) HD 1:/dev/sda1 GB fixed IOPS
(SWAP) HD 2:/dev/sdf    GB fixed  
(DB, DB TMP & DB LOG) HD 3:/dev/sdg    GB IOPS
(Upgrade Image) HD 4:/dev/sdh    GB  
Totals GB IOPS
     
     
Important: Liquidware recommends using high-end processors, 3 GHz or higher, released within the last couple of years. Liquidware does not recommend using CPUs that are more than 3 years old.
 
Database Appliance Requirements
 
  Minimum Performance
CPU (vCPUs) * vCPU vCPU
RAM GB GB
     
 
 
 
Disk Storage **    
(OS) HD 1:/dev/sda1 GB fixed IOPS
(SWAP) HD 2:/dev/sdf    GB fixed  
(DB) HD 3:/dev/sdg    GB IOPS
(DB TMP) HD 4:/dev/sdh    GB  
(DB LOG) HD 5:/dev/sdi    GB IOPS
Totals GB IOPS
     
Important: Liquidware recommends using high-end processors, 3 GHz or higher, released within the last couple of years. Liquidware does not recommend using CPUs that are more than 3 years old.
Hub Appliance Requirements
 
  Minimum Performance
CPU (vCPUs) * vCPU vCPU
RAM GB GB
     
 
 
 
Disk Storage **    
(SWAP/OS) OS GB fixed IOPS
(DB, DB TMP & DB LOG) LUN 0 GB IOPS
(Upgrade Image) LUN 1 GB  
Totals GB IOPS
     
     
Important: Liquidware recommends using high-end processors, 3 GHz or higher, released within the last couple of years. Liquidware does not recommend using CPUs that are more than 3 years old.
 
Database Appliance Requirements
 
  Minimum Performance
CPU (vCPUs) * vCPU vCPU
RAM GB GB
     
 
 
 
Disk Storage **    
(SWAP/OS) OS GB fixed IOPS
(DB) LUN 0 GB IOPS
(DB TMP) LUN 1 GB  
(DB LOG) LUN 2 GB IOPS
Totals GB IOPS
     
Important: Liquidware recommends using high-end processors, 3 GHz or higher, released within the last couple of years. Liquidware does not recommend using CPUs that are more than 3 years old.
   
CID Collector Appliance Requirements
 
Please use default CPU and Disk Storage values. Choose your RAM setting.
  Minimum Performance
CPU (vCPUs) * vCPU  
RAM GB GB
Disk Storage GB  
     
Important: Liquidware recommends using high-end processors, 3 GHz or higher, released within the last couple of years. Liquidware does not recommend using CPUs that are more than 3 years old.
 
Network Collector Appliance Requirements
 
 

CPU (vCPUs) * vCPU  
RAM GB  
Disk Storage GB  
     
Important: Liquidware recommends using high-end processors, 3 GHz or higher, released within the last couple of years. Liquidware does not recommend using CPUs that are more than 3 years old.
CID Collector Appliance Requirements
 
Please use default CPU and Disk Storage values. Choose your RAM setting.
  Minimum Performance
CPU (vCPUs) * vCPU  
RAM GB GB
Disk Storage GB  
     
Important: Liquidware recommends using high-end processors, 3 GHz or higher, released within the last couple of years. Liquidware does not recommend using CPUs that are more than 3 years old.
   
CID Collector Appliance Requirements
 
Please use default CPU and Disk Storage values. Choose your RAM setting.
 
 
 
  Minimum Performance
CPU (vCPUs) * vCPU  
RAM GB GB
Disk Storage GB  
     
Important: Liquidware recommends using high-end processors, 3 GHz or higher, released within the last couple of years. Liquidware does not recommend using CPUs that are more than 3 years old.
   

* 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.
  3. The sizing recommendations are based on using high-end processors released in the last couple of years. Liquidware does not recommend using CPUs that are more than 3 years old.


** 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/sda1" is "HD 1", which is to be used for the operating system.


*** 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.