CPU Utilization Expectations during upgrade to 8.X for Existing Multimedia Customers

INFORMATION

During upgrades, for Multimedia Contact Center customers, the installer migrates in-queue and in-progress multimedia messages to Elasticsearch. This migration uses a large share of the processor resources and, as such, may adversely affect system stability for Remote Desktop Sessions. After the migration process is complete, the installation continues and processor resources return to normal consumption levels.

NOTE: If system monitoring or management systems are configured to alarm on high resource utilization, a false flag may present during upgrades.
After installation is complete, multimedia interactions continue to be processed in the background and placed into the Elasticsearch archive. Multimedia messages are not searchable via the Ignite client until the message has been archived. Messages are archived, beginning with the most recent interactions, at a rate of approximately 8000 items per hour. The processing rate depends on your processor, available system resources, and number of historical multimedia interactions to be migrated.

Migration speed can be decreased if the server is under high load and you want to prioritize production operations. Migration speed should only be decreased if the system is in a high performance production environment and there is no immediate need to search older archived items. Default settings should provide appropriate performance for the majority of multimedia implementations.

To modify the migration speed, prior to upgrading:
1. Open the Global App Settings Editor in [Install Dir]CCM\Services\ConfigService\ .
2. Fill in the following details:
    • Application: Leave this empty.
    • SectionGroup: StorageService.ElasticsearchMigration.Properties.Settings
    • Name: MigrationDelay
    • Value: The default value is 1. Increasing this value slows down the migration speed. (A value of 100 makes the migration 10 times slower.)
    • Description: Provide a description and click Save.
3. You can now proceed with the upgrade.

APPLIES TO

MiCC Version 8.X and newer