" /> StatServer sezing - Genesys CTI User Forum

Author Topic: StatServer sezing  (Read 3101 times)

Offline Edgar

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
StatServer sezing
« on: March 15, 2013, 02:31:18 PM »
Advertisement
Hi,

We are seizing our StatServer. We have 4 Agent groups with 1000 agents each, 20 Statistics and 50 filters. My question is:  If we are opening just AgentGroups statistics (not per single agent), should we take in consideration that every agent group has 1000 agents at the moment to calculate the memory required and to be careful to not exceed the maximum number of statistics that the StatServer supports ?

Example:

4 AG x 1000 Agents x 20 statistics x 50 filters = 4 Millions statistics
MemoryReqd = 100 + (4000000 × 0.0012)

???

Thanks,

Edgar

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: StatServer sezing
« Reply #1 on: March 15, 2013, 02:44:41 PM »
Stat Server is capable of opening millions of statistics simultaneously.

There are no hard limits of statistics for Data Sourcer and Stat Servers, each is relative to the amount of physical resources available on the host and the speed of CPU. Data Sourcers collection units should be limited to 500-600K, however we have seen some customers use Data Sourers to collect over 1 million statistics on powerful servers. Stat Server 7.2-7.6 can calculate 1-1.4 million statistics within 2GB memory limit on Windows, however Stat Server versions vary by memory consumption, Stat Server 7.6 requiring more than 7.2 and 7.5. Stat Server 8.0 drops the memory consumption of statistic definitions of by half.

There is also a difference between calculated statistics and requested statistics as there could be one calculated statistic requested multiple times by same or different client. For such case only one statistics is calculated and mapped to several client requests. Also, for CCA Stat Servers special care must be taken for Data Sourcer clients which request statistics with reset based notification and Stat Server must reset 1 million statistics at once, and keep 2 million Stat Info messages in its buffer for two Data Sourcers, Primary and Backup for Reporting 7.2 HA, to receive them.

If you need collect big amount of statistics, it is recommended to deploy more than one statserver for these purposes and divide statistics "pack" on two half for example - it is not necessary to collect all statistics on one statserver, otherwise is not recommend.
« Last Edit: March 15, 2013, 02:47:36 PM by Kubig »

Offline Edgar

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
Re: StatServer sezing
« Reply #2 on: March 15, 2013, 02:57:46 PM »
Thanks!

My question was mainly because If I take in consideration only the agent groups, in theory, we will have 300.000 opened statistics. But if when opening an Agent group statistic, the statserver "internally" opens the same statistics for every agent to be able to monitor them (even if the Custom client using SDK requested only AgentGroup statistics), I get more than 10 Millions stats.

What's the statserver's behavior with AgentGroup statitistics? I should take the 300.000 or the 10 Millions stats as its real charge?



Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: StatServer sezing
« Reply #3 on: March 15, 2013, 03:04:50 PM »
It depends on statistics configuration and template in DMA - what objects are required and requested. If template request agent as object ,then it will take millions stats.

Offline Edgar

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
Re: StatServer sezing
« Reply #4 on: March 15, 2013, 03:26:23 PM »

The objects should be "GroupAgents". In that case it should be ok for no matter the Category of statistic requested right?