" /> ODS load - Genesys CTI User Forum

Author Topic: ODS load  (Read 4411 times)

This topic contains a post which is marked as Best Answer. Press here if you would like to see it.

Perry

  • Guest
ODS load
« on: January 01, 1970, 12:00:00 AM »
Advertisement
hello, everybody, how are you? this is a great bbs; thank you for all your help. can someone tell me if it is possible to reduce the load on the statserver used by datasourcer. according to dma, we have 350,000 request. is this the number of requests issued to statserver from datasourcer every fifteen minutes? can this number be reduced or are all of these statistics at the same time?

Mike

  • Guest
ODS load
« Reply #1 on: January 01, 1970, 12:00:00 AM »
Perry,

One way that we have reduced the workload for DataSourcer / Stat Server is to create DMA templates with only the specific stats you currently need (+ any known future needs). Secondly, eliminate all other (unused) stats from your CCA Stat Server. (Even though DataSourcer may not request them from the stat server, the stat server still collects any stat configured in the options tab). This has significantly reduced our overhead on these applications and reduced the runtime for ETL as well.

Hope this helps.
Mike

Tony Tillyer

  • Guest
ODS load
« Reply #2 on: January 01, 1970, 12:00:00 AM »
...As Mike suggests, plus (if you have ETL Assistant), edit the longevity of the storage of your statistical data via the ETL Assistant templates. Mine are set something like this:

NOAGG store for 5 days, purge on day 1
HOURLY store for 5 days, purge on day 1
DAILY store for 31 days, purge on day 1
WEEKLY store for 2 years, purge on day 1
MONTHLY store for 2 years, purge on day 1
QUARTERLY store for 2 years, purge on day 1
YEARLY store for 2 years, purge on day 1

In this way, you are not clogging up your ETL DataMart with unecessary or unused data.

HTH?

Tony

Vic

  • Guest
ODS load
« Reply #3 on: January 01, 1970, 12:00:00 AM »
I actually have a similar problem to Perry.
I was looking at our DMA, and for one report it said that there are 110,000 requests!!! I was wondering how it was getting this, since we are using a standard Agent Report template, which has, if I am not mistaken 13 stats or so... There are 3000 people, so would it not be 13*3000=39000 and not 110,000? How does it get this weirdly large number?

Thanks!
Vic

Marked as best answer by on Today at 12:36:41 AM

Beancurd

  • Guest
ODS load
« Reply #4 on: January 01, 1970, 12:00:00 AM »
  • Undo Best Answer
  • The easiest way of reducing the number of requests is to examine the objects against which the stats are associated. Usually the templates are associated with All Agents, the question is then do these stas need to be collected for all agents? If not, then the thing to do is to create an agent group for reporting purposes only and then apply the template for that AG only. The same can be done for Groups of DNs as well.