The difference in architecture between PRPC 5.x and Pega 7 is substantial. This alone could certainly have lead to what you are seeing. With that said, we can look a little deeper. Are you seeing this in production under similar load to what was in PRPC 5.x? Any indication which requestor types are impacted?

    You can use pr_hourly_usage in tracking historical data. "You can use pr_perf_stats, pr_daily_usage and pr_hourly_usage table in order to get number of users/requestor logging in Daily/Hourly. These tables have all the details related to request login and logout information. By querying pr_hourly_usage you can get a pattern of number of concurrent request logging in a particular hour." 

Paul,

Mark is out of the office, so I am replying instead. We are seeing similar workloads within Production but the increase in invocations was in the neighborhood of a 60% increase upon switching. I had a sales rep mention to ensure that we have our reg/occ users setup properly. Is there some guidance that can be provided on what to look for within a user account that would make them show as an invocations instead of a user? As an additional note, the we queried the PR_Hourly_Usage table but the numbers generated by the OverallSystemUsage_All report do not match. I feel we are missing a critical piece somewhere.

Thanks.

Have not yet had a chance to research this further. I will see if I can get someone with a deeper understanding to look at this.

Please submit a GCS request to confirm the need to port HFix-27840.

HFix-27840: Incorrect invocation counts caused by Lucene search as the "Method is read-only" check box is not enabled for ootb search related services.

Hi Mark and John,

Please let us know the SR number once you create it. We will tag that to your post above for effective troubleshooting. Also, do not forget to mention the URL of this post in the SR.

Regards,

Lochan  |  Community Moderator  |  Pegasystems Inc.

I have created SR-B5265 for this issue to be ported to PEGA 7.1.6