Dynamic Threshold - Report Displays becoming CPU Intensive

Highlighted
05 Base Camper

Dynamic Threshold - Report Displays becoming CPU Intensive

I have been working on displays using the data stored on the Dynamic Threshold database but, I have noticed the displays are starting to become taxing on the CPU.  Is there a way to optimize this display anymore without sacrificing the history length or am I simply gonna have to increase the # of CPU cores? Just looking for opinions.

 

Dataview Definition Where Clause:

Approval

SRCNODE = "\" AND REMASSOC = "TOTAL" AND FIELD = "APRV%" AND PROFILE = "DayOfWeek3Month"

Decline

SRCNODE = "\" AND REMASSOC = "TOTAL" AND FIELD = "DENY%" AND PROFILE = "DayOfWeek3Month"

 

Refresh Rate: 5 Minutes

Chart Intervals: 4032

Label Every: 288

Database: DynamicThresholdDBCol

Period: Start 14 Days Ago -> End of data

Collection Interval: 5 Minutes 

 

- No end user load on the top level node in this screen capture. 

Task Manager - Top Level Node - 2020-07-13_20-37-11.jpgDynamic Thresholds - Approval Percentage - 2020-07-13_20-34-51.jpg

Tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Community Manager

Re: Dynamic Threshold - Report Displays becoming CPU Intensive

Hi There,

 

Chart Intervals: 4032 tends to stand out as being a lot of data points to draw when most PC monitors have less than 2000 pixels across. So first thing to try I'd suggest larger interval (10 minutes or 20 minutes or ...) for half or quarter the number of data points to plot. If that can't be done using the DynamicThresholdValues (DTVALUE) record you're using, then the corresponding transaction summary record might be a better choice as the denial, approval fields are of type Average in those records. Even create a database collection of the transaction summary record for it if necessary.

 

HTH

View solution in original post

1 REPLY 1
Highlighted
Community Manager

Re: Dynamic Threshold - Report Displays becoming CPU Intensive

Hi There,

 

Chart Intervals: 4032 tends to stand out as being a lot of data points to draw when most PC monitors have less than 2000 pixels across. So first thing to try I'd suggest larger interval (10 minutes or 20 minutes or ...) for half or quarter the number of data points to plot. If that can't be done using the DynamicThresholdValues (DTVALUE) record you're using, then the corresponding transaction summary record might be a better choice as the denial, approval fields are of type Average in those records. Even create a database collection of the transaction summary record for it if necessary.

 

HTH

View solution in original post

Webinar: Top Ten Predictions in Retail Payments for 2020

Join IR, Celent and your peers as we discuss the top ten predictions for retail payments in 2020 and how evolving your payment solutions will help you stay ahead of your customers’ expectations ...

Join Webinar
Top Liked Members