Recommendation on CPU/Memory for web pod and batch pod
We are using AWS EKS with managed nodes to host PEGA. We do have 8GB memory configured for web pod but there were some complaints of slowness and pod restart due to memory.
I am looking for your recommendation on cpu/memory requests for Web pod and batch pod.
Question 1: What configuration make sense for Dev and QA environment?
Dev environment :
Number of developers - 5
QA env :
Number of test engineer - 3
Question 2: Can we use EC2 spot instances for any of Pega workload?
Question 3: Any suggestion on tool to monitor pod performance for cpu/memory?
Pegasystems Inc.
US
Hi @AnujG702,
I reached out to some of my SMEs and they suggested that you check out these two knowledge base articles below (also check out the Related Content on the side of this post) and you can also reach out to your Account Executive and/or Consulting who can offer you guidance.
I'd also love it if our PCC members could offer you some advice that are outside of Pega! Members, please share your advice and help out one of your fellow PCC members! :)
Hope that helps!
Crum & Forster Insurance
US
Thank you @MarissaRogers
PCC Members - If you use Kubernetes, can you please share what do you have configured CPU and memory limits?
KPN
NL
Hi @AnujG702,
Looking at: Question 2: Can we use EC2 spot instances for any of Pega workload?
Did you had new insights on this? There is a 120 seconds timeframe which can signal the processes within the container. For the web-tiers it could work when offering API services, since these are very short living sessions (calls), but what about GUI based sessions? If all session data is available in Hazelcast it might also work when a user comes resumes its session on another node, but I have not done any testing and seen much about this in the forum.
Maarten