ATC/Current/PacingServiceDeployment/ArchitectureArticle - Revision history

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

2020-07-25T02:29:59Z

Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|])PureEngage([\|])" to "|Platform=$1GenesysEngage-onpremises$2"

2020-07-15T11:44:09Z

Text replacement - "\|Platforms?=([^\|]*)PureEngage([\|]*)" to "|Platform=$1GenesysEngage-onpremises$2"

DannaShirley: Published

2018-12-05T14:43:19Z

Published

Bgrenon: 1 revision imported

2018-11-07T15:27:10Z

1 revision imported

DannaShirley at 23:26, October 24, 2018

2018-10-24T23:26:31Z

New page

{{ArticleUnstructured
|DisplayName=Architecture
|Platform=PureEngage
|TocName=Architecture
|Context=Read about performance and high availability considerations for Agent Pacing Service.
}}
==Architecture diagram==
[[File:Pacing-Shared-HLA-Architecture.png]]
The Agent Pacing Service connects to only one Stat Server (high-availability pair).
{{NoteFormat|The Agent Pacing Service requires that the Stat Server has visibility of all potential pacing targets.|1}}

Multiple actively running pacing nodes can belong to the same pacing cluster. Under normal conditions, there is only one master pacing node that provides pacing target information to Altocloud. All pacing nodes are interconnected, and they self-determine which is the master pacing node based on an internal election algorithm.

==Performance==
Each pacing node is designed to support up to 10,000 pacing targets. The execution of the pacing algorithm does not put significant pressure on either the memory or the CPU. However, as the number of pacing targets increases, so does the size of the HTTP request and the corresponding response between Pacing Service and Altocloud. For this reason, network bandwidth becomes a concern in terms of system stability.

Problems may occur if the roundtrip of the HTTP package reaches the timeout limit or the pacing refresh period. If you experience performance problems, try tuning your network bandwidth or reducing the number of pacing targets.

{{NoteFormat|The performance of a single pacing server node has been verified for the following configuration:
* 2 CPUs (Core i7)
* 6 Gb RAM
* 2 Gb of allocated Java Heap memory|1}}

==Scalability==
For nodes belonging to same pacing cluster, the scalability model is N+1. Based on performance testing, two pacing nodes should be sufficient to sustain most deployments.

==High availability==
This release of Agent Pacing Service works with a single Stat Server HA pair. To ensure high availability in a premises-based environment, install two (2) Pacing Server nodes.

@@ Line 1: / Line 1: @@
 {{ArticleUnstructured
 |DisplayName=Architecture
-|Platform=GenesysEngage-onpremises
+|Platform=GenesysEngage-cloud
 |TocName=Architecture
 |Context=Read about performance and high availability considerations for Agent Pacing Service.

@@ Line 10: / Line 10: @@
 {{NoteFormat|The Agent Pacing Service requires that the Stat Server has visibility of all potential pacing targets.|1}}
-Multiple actively running pacing nodes can belong to the same pacing cluster. Under normal conditions, there is only one master pacing node that provides pacing target information to Altocloud. All pacing nodes are interconnected, and they self-determine which is the master pacing node based on an internal election algorithm.
+Multiple actively running pacing nodes can belong to the same pacing cluster. Under normal conditions, there is only one master pacing node that provides pacing target information to {{MINTYDOCSPRODUCT}}. All pacing nodes are interconnected, and they self-determine which is the master pacing node based on an internal election algorithm.
 ==Performance==
-Each pacing node is designed to support up to 10,000 pacing targets. The execution of the pacing algorithm does not put significant pressure on either the memory or the CPU. However, as the number of pacing targets increases, so does the size of the HTTP request and the corresponding response between Pacing Service and Altocloud. For this reason, network bandwidth becomes a concern in terms of system stability.
+Each pacing node is designed to support up to 10,000 pacing targets. The execution of the pacing algorithm does not put significant pressure on either the memory or the CPU. However, as the number of pacing targets increases, so does the size of the HTTP request and the corresponding response between Pacing Service and {{MINTYDOCSPRODUCT}}. For this reason, network bandwidth becomes a concern in terms of system stability.
 Problems may occur if the roundtrip of the HTTP package reaches the timeout limit or the pacing refresh period. If you experience performance problems, try tuning your network bandwidth or reducing the number of pacing targets.

← Older revision	Revision as of 15:27, November 7, 2018
(No difference)