Jump to: navigation, search

User:Jokane

Release Note: 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.

1.2.0.3

What's New

This release contains the following new features and enhancements:

  • Implemented new deployment option TLS and calculation of impact of using TLS encryption on resource utilization. (SSC-401)
  • Changed default settings for Cassandra to Dedicated. (SSC-499)
  • Added input parameters Chats Per Day and E-Mail Interactions Per Day. (SSC-480)
  • In order to indicate agent workspace location values Desktop Edition/External and Web Edition/External were added to Agent Workspace Type.
  • Added new components: vc.lds, vc.lds-ss, vc.lds-ag;

Resolved Issues

This release contains the following resolved issues:

  • Chat and Email: Parameter "Max Concurrent Interactions per Agent" = 0 results in undefined value for "Required Number of Agents" derived parameter. (SSC-602)
  • Default configuration upon login contains un-requested Pulse components, Recalculate required to remove. (SSC-607)

1.2.0.2

What's New

This release contains the following new features and enhancements:

  • New version uses test data collected on VM with the latest patches applied. It was verified that "Meltdown and Spectre" related patches do not have significant impact on the sizing. (SSC-306)
  • Sizing model has been updated based on the latest test data.
  • Tooltips information for input parameters is updated. Link to input parameters definitions and tooltips is now included into help page.

Resolved Issues

This release contains no resolved issues.

1.2.0.1

What's New

This release includes only resolved issues.

Resolved Issues

This release contains the following resolved issues:

  • After import Deployment Schema values are not as expected, Recalculate required on Input Wizard Tab. (SSC-495)
  • Problem with import of VM with changed OS field. (SSC-496)
  • Assignment table breaks after importing with DMZ ON. (SSC-497)

1.2.0.0

What's New

This release contains the following new features and enhancements:

  • Implemented generic format for GSC import/export file. New format is essential for planned GSC backward compatibility feature. (SSC-346)
  • VM's name in export file now includes partition number, ESX and component's order number. (SSC-454)
  • Default values for Concurrent Voice Playback Users and Concurrent Screen Playback Users should depend from the size of deployment. (SSC-455)
  • Introduced gir-all.1 and gir-all.2 VMs in VM optimized profile for small deployment sizes. (SSC-457)
  • Introduced gir-all.2-b VM to support correct resource calculation for HA pair. (SSC-458)
  • Moved ESX Parameters from InputWizard menu to a separate tab. (SSC-461)
  • Two new VMs (gir-sm-ir, gir-sm-upl) for GIR solution. (SSC-462)
  • New default values of cores and memory for GIR VMs. (SSC-463)

Resolved Issues

This release contains the following resolved issues:

  • CallBack parameters are shown in FIle even if all Voice services are set to OFF. (SSC-469)
  • Call Back load is not accounted for in Rate of Recording and Number of Calls On Recording. (SSC-488)

1.1.5.2

What's New

This release contains the following new features and enhancements:

  • Change default values for voice and screen recording retention periods. (SSC-441)

Resolved Issues

This release contains the following resolved issues:

  • DMZ is OFF: Different behavior under 'VM optimized' and 'ESX optimized' profiles. (SSC-418)
  • Number of calls on IVR for outbound traffic is incorrect. (SSC-420)
  • Default values for UCS input parameters calculated incorrectly for outbound traffic. (SSC-421)
  • FS should be removed from vc-sip.icon if FS is off. (SSC-422)
  • If gi2 is manually removed and moved to pulse VM “Calculate” doesn’t work. (SSC-423)
  • Number of RP instances is incorrect. (SSC-440)

1.1.5.1

What's New

This release contains the following new features and enhancements:

  • Add deployment option MCP to enable splitting MCP by usage. Let's use Combo-Box with values: Shared, Dedicated. (SSC-349)
  • Add derived parameter SpeechMiner Indexer Size in Recording tab. (SSC-355)
  • Add vc.icon-ocs component. Calculate OCS processing impact on vc.icon, vc.icon-ocs and reporting SQL. (SSC-411)
  • Improve Cassandra nodes deployment for All in one profile. Set minimal number of Cassandra nodes to 4. (SSC-412)
  • Improve ORS nodes deployment for All in one and VM Optimized profiles. Set minimal number of ORS nodes per VM to 2. (SSC-413)

Resolved Issues

This release contains the following resolved issues:

  • Correct resource utilization values for RWS, ES for GIR option. (SSC-353)
  • Incorrect default value for mode of recording if Voice Inbound or Outbound is changed from OFF. In some cases "Recording" mode stays "OFF". (SSC-409)

1.1.5

What's New

This release contains the following new features and enhancements:

  • Introduce deployment option to specify deployment with shared or dedicated RDBMS. (SSC-348)
  • Introduce deployment option to specify deployment with shared or dedicated MCP. (SSC-349)
  • Modify GIR implementation for All in one profile to reduce HW requirement for small deployments. (SSC-350)

Resolved Issues

This release contains no resolved issues.

1.1.4.1

What's New

This release contains only resolved issues.

Resolved Issues

This release contains the following resolved issues:

  • Upload window - range should be 0...24. (SSC-320)
  • ESXs names in Deployment schema are different from Assignment table. (SSC-347)

1.1.4

What's New

This release contains the following new features and enhancements:

  • Added GIR/GIA to sizing calculator. (SSC-65)
  • Removed GMS service from the list of services. Callback service is now under Voice channel. (SSC-278)
  • Added GIR related UI controls to sizing calculator, parameters related to Recording moved from Common to new Recording tab. (SSC-296)
  • Latest GWE performance data incorporated into sizing calculator. (SSC-304)

Resolved Issues

This release contains the following resolved issues:

  • Primary and Backup VMs placed on the same ESX. (SSC-235)
  • VM Settings page: Revert to default is not working for some VM Types. (SSC-268)
  • VM Settings Tab: Number of apps on VM for Dual Data Center All in one exceeds current limit of 16 and shown in incomplete column. (SSC-283)
  • Revert all values to default works not correctly for some fields under Common. (SSC-294)
  • Default value of parameter Outbound Calls Per Day for Outbound service calculated incorrectly. (SSC-324)

1.1.2.1

What's New

This release contains only resolved issues.

Resolved Issues

This release contains the following resolved issues:

  • Deployment schema incorrectly presents IOPS and Size data. It should be divided by number of instances. (SSC-299)
  • IVR sizing implemented incorrectly. (SSC-300)

1.1.2

What's New

This release contains the following new features and enhancements:

  • Redesigned export to XLS (multi tab) document that has number of tabs similar to the browser’s view. (SSC-252)
  • Redesigned Sizing Calculator to use GMS as the only option to work with Chat Server. (SSC-249)
  • Added two pairs of message servers for dual data center deployment (one pair per DC: cm.msg-ext, cm.msg-ext-b). One pair should be used for supporting SCS distributed mode. Another pair should be used for URS “Self-awareness” feature. (SSC-271)
  • Added “Common” derived values for Log size, DB size of ICON, GIM, IXN, UCS and Recording. (SSC-209)
  • Renamed tables “VM Settings", "ESX Totals" and "Assignment Table" to include "per DC" suffix. (SSC-261)

Resolved Issues

This release contains the following resolved issues:

  • Import JSON with Dual Data Center resulting to One Data Center deployment without ability to change it to Dual. (SSC-251)
  • Unexpected application 'dg.sql-ixn' exists for voice-only VM optimized solution in medium3, large and x-large sizes. (SSC-253)
  • xls single-tab, multi-tab exports: "ESX Totals [per Data Center]" table is missing. (SSC-260)
  • IXN Interaction DB Size parameter is not updating when switching between 'voice only' and 'voice and digital' channels. (SSC-263)
  • If size is set to 'OFF' for Voice or Digital, its Profile selection should be ignored. (SSC-269)
  • When Profile All-In-One with 'No' Cassandra is selected, the Cassandra still listed. (SSC-272)
  • If GMS is the only active digital service then all related components have zero CPU utilization. It also wrongly includes IXN related components. (SSC-273)
  • Second Recalculate is required to receive ucs-related components for Digital services; depends on sequence of ordering on Input Wizard. (SSC-274)

1.1.1

What's New

This release contains the following new features and enhancements:

  • Implemented dynamic changes in VM parameters based on size selection. (SSC-230)
  • Added link to Release Notes in Help.
  • Allocated dedicated cm-gi2 VM for all deployment sizes.
  • Implemented export to Excel multi-tab document.
  • Improved “All in one” profile resources allocation.
  • Improved algorithm for VM distribution between ESXs.
  • Defined new ranges for VM parameters. (SSC-241)

Resolved Issues

This release contains the following resolved issues:

  • UCS input parameters are not editable when Selection set to Default. (SSC-181)
  • Import file function requires using Recalculate button otherwise Deployment Schema shows incorrect values. (SSC-187)
  • Incorrect calculating total number of RAM memory in Assignment table tab. (SSC-190)
  • Decimal values instead of rounded up to integers for derived parameter Common/"Number of Calls on Recording". (SSC-191)
  • Number of Calls on Recording ignores inbound calls and equals outbound call rate when Outbound is present and "Start Recording On"="Customer". (SSC-193)
  • Digital VMs have all-0 resources utilization when Linux OS is selected. (SSC-196)
  • ESX optimized profiles are missing one of the two required components "cm.db"; names need correction to cm.db; cm.db-b. (SSC-197)
  • SSC version should be shown on exported files. (SSC-199)
  • Increase maximum number of ESX on partitions. (SSC-200)
  • Digital solution under Linux: 'Recalculate' returns incorrect numbers of ESXs. (SSC-201)
  • ESX Optimized profile shows one primary/backup pair of ORSs regardless of size on VM Settings and Assignment Table tabs for digital services. (SSC-202)
  • Change UI naming to "Genesys PureEngage Solution Sizing Calculator". (SSC-203)
  • 'Strategy Complexity','Queued per Interaction' ,'Complexity Level' fields for several solutions are not editable. (SSC-204)
  • Disable "Recalculate" button if any parameter is invalid. (SSC-206)
  • Restrict importing file that is created by old SSC version. (SSC-207)
  • Change UCS limits (Common Tab). (SSC-212)
  • In VM optimized profile for VMs: cm-fw, cm-fw-b, dg-all.1, dg-all.1-b use cores number= 8 for sizes> small. (SSC-213)
  • "Start" menu is now hidden. (SSC-215)
  • Calculations based on number of agents and resulting number of proxy components (cfg-prx, ixn-prx, ucs-prx) were not updated unless user visits Common section in Input Wizard. (SSC-217)
  • ESX Parameters, Deployment Options and Cassandra Deployment Options are not present in File Tab. (SSC-219)
  • Edited input parameter "Recording Percentage (%)" overwritten by default "100%" if user re-visits Common and uses "Recalculate" while on Common. (SSC-220)
  • Editing of "Required" column on "VM Settings" is ignored and not reflected in resource utilization. (SSC-221)
  • File Tab shows single data center deployment schema even if user sets Dual Data Center = true. (SSC-224)
  • Implement dynamic changes in VM parameters based on size selection. (SSC-230)
  • OS for backup VM of the same type should be set automatically when user sets OS for primary VM (and vice versa). (SSC-231)
  • Physical Cores parameter should not allow 0 value. (SSC-232)
  • Manual changes of "Total Number of Agents" (Common tab.) will be overwritten after “Recalculate”. (SSC-238)

1.1.0

What's New

This release contains the following new features and enhancements:

  • Legal disclaimer added on UI screens. (SSC-192)
  • VM-optimized profile first introduced in version 1.0.10 is now improved with new default VM settings. "VM Optimized" profile uses large VMs. In most cases "VM optimized" profile provides lesser number of VMs and total number of virtual cores on them compared to "ESX optimized" profile. (SSC-194)
  • Cassandra deployment options: user can choose Shared/Dedicated/No Cassandra deployment option for each component. (SSC-210)
  • GSC XLS output report now includes all essential parameters (calculator version, report date, project and user names, ESX parameters and deployment options). (SSC-90; SSC-145; SSC-214)

Resolved Issues

See the 1.1.1 release section for more information.

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.
Retrieved from "https://docs.genesys.com/User:Jokane (2019-03-25 21:58:33)"
This page was last modified on February 5, 2019, at 13:10.