Discussion
Pegasystems Inc.
IN
Last activity: 29 Oct 2021 9:38 EDT
Office Hours: Runtime Engine with Karthik Eppili
Join @KarthikEppili a lead technical specialist, in this Office Hours from October 25 to October 29
Karthik is an expert in the following areas at Pega and ask him anything about:
- Passivation
- Rule Resolution
- RUF and Library
- Cloud (newer) Case Archival
- Thread Dump Analysis
- Requestor Management
- Memory Management
Office Hours is a new monthly interaction series with Pega SMEs. Read the following rules while asking questions:
- Follow the Pega Collaboration Center's Guidelines
- This is not a live chat. The featured SME will asynchronously answer questions during the week of Office Hours
- Ask questions related to the areas of expertise of the featured SME
- Questions that are open-ended or discuss rarest of the rare scenarios or trivial use cases do not qualify for Office Hours
- Upvote questions that you find interesting by clicking on Like button
- Have fun!
Favorite and Subscribe this post for updates!
Updated: 29 Oct 2021 2:11 EDT
Accenture Pte Ltd
SG
Hello, We are using MS SQL Server database for our Pega application and currently we have allocated 85% of total memory to SQL Server. And currently database server overall utilization goes up to 95% in production environment. We would like to know what is the Pega support recommendation or best practice to configure memory for MS SQL Server database which is being used by Pega application? Current memory settings: Database Server total memory (RAM) - 56GB Memory allocated to MS SQL Server - 48GB Total server memory utilization - ~95%
Pegasystems Inc.
AU
Thanks for reaching out. Please have the DBA do the necessary analysis and if you see any abnormal growth in tables, you can engage Pega Support via an INC.
In general, we cannot recommend a specific size as it completely depends on how much data is stored in DB by each system.
Updated: 29 Oct 2021 2:38 EDT
Pegasystems Inc.
CA
In cloud production environment, we have 2500+ users in production most of the time during the working hours. We have 6 web nodes, so each node will have more than 400 sessions during the day. But once the session count is over 400 sessions, the PDC will issue a critical alert "The current status of "requestors" exceeded the critical threshold limit", this causes system reliability concerns both from tech team and client. Question to cloud team: 1. Is it true that each web node MUST have less than 400 sessions? The webnode has 32 GB JVM. 2. If is, please advise if we need to increase the node count ? 3. If no, how to reset the session threshold limit on the PDC and what would be the safe threshold for session count ?
Thanks
Pegasystems Inc.
AU
Thanks for reaching out. The setting /alerts/requestors/count/thresholdis controls this alert. Please validate this value in your system if it is set to 400.
The number of user sessions depends on what the users are doing and how much memory they are occupying and optimal values can be derived only from the Load test. If you are still looking for more inputs, please reach out @PoojaGadige to get this created as a separate post.
Pegasystems Inc.
CA
@KarthikEppili Thank you for your reply Karthik. I am not able to find this setting in DSS and prconfig file. The system is Pega 8.5.4 and Pega 8.6.
Thanks
Updated: 29 Oct 2021 2:38 EDT
ING
NL
Hello,
I just observed in Engine API documentation has some methods that should work with Local thread-level cache. Unfortunetly there is no explenation about details despite it is in public Engine API. I’m curios about methods in public interface PRThread:
- saveRuleImpl(java.lang.String reusableKey, java.lang.Object aImpl)
- resetRuleImpl()
- saveRuleImplInUseState(java.lang.Integer genJavaHash, java.lang.Boolean bInUse)
- getRuleImplInUseState(java.lang.Integer genJavaHash)
Is that possible to get examples of usage of that methods? And what is the types of parameters that is passed to the methods?
Updated: 29 Oct 2021 2:38 EDT
Pegasystems Inc.
AU
The methods which are publicly accessible for use are provided under PublicAPI Class, I dont see these methods in there which tells us that these cannot be accessed.
The other classes mentioned in the help only give the information about the methods it has and purpose of it but they cannot be used. You might be seeing these in PRThread class, if we see the parameters for these methods it has a genJavaHash which is generally not available for public use and rather only used internally.
If you still feel these methods can be accessed publicly as per the documentation you are referring to, please share the link of Document and a screenshot if possible for us to review it .
Updated: 29 Oct 2021 2:38 EDT
ING
NL
@KarthikEppili Thank you for the response. You are right i found that methods in PRThread Class.
Let me challenge you a little bit. If we follow you logic we should use only methods that is in PublicAPI and nothing that is in other classes. Does it mean that e.g. we should not use any methods in that is in class ClipboardPage. If it methods from ClibboardPage is possible to use what is the difference between ClipboardPage and PRThread. I thought that everithing that is published in Engine API is allowed to use. If not could you mark some how or even hide in that help things that is not allowed to use?
Updated: 29 Oct 2021 2:38 EDT
Centene
US
Does the OOTB cloud archival process work is supported for on-prem / client cloud environment? I believe it should be supported as all the JobSchedulers are available for customization for the customers. Do we have any documentation on how to do it?
Pegasystems Inc.
AU
Thankyou for reaching us out.
The new Archival process is not rolled out yet for On-Prem / Client Cloud environments. But there are plans to roll this out for these environments in future i believe somewhere in or after 8.7. This will be announced very soon.
Pegasystems Inc.
IN
Thank you @KarthikEppili for being the featured guest SME for the October edition of Office Hours this week on Pega Collaboration Center. We appreciate your valuable time and help in answering the questions.
And thank you everyone who posted a question!
We hope to see you in the next Office Hours in November! Stay tuned!