Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Lokanath Ganji (LOKANATH)
Cognizant
Pega SSA
Cognizant
US
LOKANATH Member since 2011 3 posts
Cognizant
Posted: Jun 16, 2020
Last activity: Sep 17, 2020
Posted: 16 Jun 2020 16:54 EDT
Last activity: 17 Sep 2020 22:58 EDT
Closed

How to avoid performance degrade when PRPushServlet feature is enabled ?

When Performance degrades on using PRPushServlet and if the push feature is not required for the application , we are aware that we can disable the push servlet features by doing the below configuration change.

Disable the Push feature by setting the following Dynamic System Setting: Owning Ruleset: Pega-Engine Purpose: prconfig/server-push/enabled/default value: false

But eventually what is the solution to avoid the performance degrade when we enable the PRPushServlet feature for the given application? Any recommendation or best practices ?

Any thoughts or inputs on this ?

Thanks in advance.

 

***Edited by Moderator: Pallavi to update platform capability tags***

To see attachments, please log in.
Pega Platform 7.2.1
User Experience

  • Guangri Liang
Posted: 4 years ago
Updated: 4 years ago
Posted: 9 Jul 2020 1:09 EDT
Updated: 13 Jul 2020 1:46 EDT
SaiKiran Nukala (nukas) Associate Architect
Pegasystems Inc.
IN

Hi Lokanath,

What is the performance issue you are seeing?  could you please elaborate with more details and share your stack (WAS/JBOSS/Tomcat/WebLogic and load balancer details or any startup logs?

Push feature is a technology upgrade to improve scaling and publish messages from server to browser, there are many out-of-the-box features that use Push to deliver messages.

Brief technical overview about request/response for Push:

Many of the application/web servers support JSR356 or Servlet 3.0 features. Either of these features will not hold any thread resource at the server for longer period. If server and load balancer support WebSockets (JSR356) then WebSocket will be established otherwise framework will fallback to Long-Polling, even with long-polling for every 60 seconds a long-polling request will be sent from the browser and at the server if the request has any messages to be delivered it will immediately by sending the response. If there are no messages the request will be suspended for 60 seconds, this means thread resources will be released, and only when messages have to be sent the thread will be used, this feature is called Async Servlet request processing. With Push, in our internal performance testing, we were able to deliver thousands of messages without any performance impact.

Regards,

Saikiran

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice