Our Pega developers using tracer are noticing that it can take up to 30 seconds to view the contents of pyWorkPage in a tracer step. Granted, pyWorkPage is very large and we only trace it when we need to know its contents at a certain point in execution. I was wondering if anyone knew of any tricks to help the performance of tracer in situations like this.
I did some searching on the PDN already but could not find any topic like this already. Apologies if I missed something that already covers this.
In case it matters, this is running Pega Platform 7.4, but we have a server running Pega Platform 7.2 as well and behavior is pretty consistent.
Agreed. Developers have removed what they did not want to see. They are just trying to look at pyWorkPage on specific steps. So no watch pages. In one instance they were only tracing 74 lines of activities. Access Deny rules, Data Transforms, Exception, and When rules were unchecked in events.