PureEngage Sizing Calculator Release Notes

These are the release notes for Genesys Sizing Calculator.

Important Notes

Read the information below for important notes about using the Genesys Sizing Calculator (GSC). Also see the Known Issues section for more information.

General

• Supported browsers: Google Chrome and Mozilla Firefox.
• Supported file formats for Export To File operation: .JSON and .XLS. Import is supported from .JSON file format.
• As of the 1.1.0 release, .CSV export format is no longer supported.
• GSC restricts the import of JSON file versions that do not match the GSC version. In order to continue an existing project, you must select the corresponding earlier GSC version on the Start page and perform a JSON file import after redirect. (SSC-207).

Database

• Cassandra is sized with the following limitation: micro and All-in-One configurations may have three instances in shared cluster. Larger configurations have more Cassandra instances. Algorithm for sizing shared Cassandra cluster is under development and is not fully implemented in current version.
• Only shared Cassandra should be used for All-in-One deployment (There are not enough VMs to host all dedicated Cassandra nodes). Current implementation doesn't enforce this limitation.
• GIM DB and ICON database sizes are combined and reported as “cm.sql” component.

Sizing data

• The current version of GSC supports sizing for the most resource-consuming components. However, some components are not covered. See the Component Settings table (internal link) for component's sizing status.
• Only two ESX Partitions are available.
• Current Integrated Calculator version has sizing data for Chat, Email, GWE and Open Media services. Other services, such as SMS, GCB, and Classification, can be enabled but current calculator version assigns these components to VM and ESXs without resource utilization consideration. Resource utilization for these services currently presented as zero. Addition of sizing data for SMS and GCB is planned in next versions.
• ORS sizing data is related to the configuration without persistence. This means that during the sizing tests ORS has been running without Cassandra.
• Chat and GMS server components are sized according to N+1 system model. According to this model total load is evenly distributed among component instances. Deployment can have only one Email server primary/backup pair (Email server instances are not marked as primary or backup).
• Linux sizing data is only available for the following Voice components: SIP Server, ORS, MCP, ICON, URS, and StatServer. Primary and Backup VMs should be assigned the same operating system. To change the OS for VMs of a particular type, change the OS of the Primary and Backup VM instances on “VM Settings” Tab.

Known Issues

• The VM Optimized profile currently uses Partition 1 only. When sizing services requiring Partition 2, (such as GWE, GMS, and GCB) as DMZ, user shall edit Partition column for the corresponding VMs on VM Settings Tab.
• You must select DMZ = Custom to manually change the partition for DMZ-related VMs (dg-gms, dg-gwe, dg-cas-gwe, dg-gcb).
• GIA only has partial sizing information. SpeechMiner components are not sized in the current version. GSC calculates impact of GIA on MCP only.
• There is no way to specify parameters "Chats Per Day", "E-Mails Per Day" and "Open Media Interactions Per Day". GSC uses ration 1:5 to calculate these parameters from the peak rate.
• GIR Webdav disk size in “Deployment Schema” is split across webdav instances. In real deployments, webdav instances use the same disk storage. Use information from "Record" tab for the required recording size if necessary.
• GIR sizing is not officially approved by the GIR team. You must consult GIR team for a final GIR sizing approval.