Question
PegaOne
IN
Last activity: 25 Oct 2019 10:02 EDT
Disable HTTP Compression for Dynatrace
Hi all,
We have Dynatrace integrated with our Pega CPM application. In order to effectively utilize Dynatrace, HTTP Compression on Pega needs be disabled on prconfig file.
Post this change, would there be any impact on the functionality or performance in Application servers? Would this require a server restart to take affect?
Any information would be useful, thank you.
***Edited by Moderator Marissa to update SR Details; update platform capability tags***
Accepted Solution
Pegasystems Inc.
IN
You can use below setting in prconfig.xml to turn off http compression:
You can use below setting in prconfig.xml to turn off http compression:
<env name="initialization/httpcompression" value="false" />
For application impact, suggest you to thoroughly test the application.
Kaiser Permanente
US
Hi Arvind,
Any performance impact on existing PROD servers if we turn off "http compression" (the current application using internal and external users (SSL) ) ?
Would this require a server restart to take affect?
Thank you in Advance !!.
Regards,
Omkar
Triton Consulting
US
We are facing a similar situation. Can anyone please chime in if they disabled the compression and the resulting performance impact.
Thanks in advance.
The Toronto Dominion Bank
CA
Hi all,
Can this setting be done through a DSS like below:
Ruleset: Pega-Engine
setting purpose: prconfig/initialization/httpcompression/default
value: true
Pegasystems Inc.
US
Hi,
The use of HTTP compression is part of general web application performance to improve transfer rates and bandwidth utilization.
When you disable HTTP Compression it will have an impact on load times pages for initial page loads on first visit to the application each time. It shouldn't be too bad but maybe noticeable. The .js files will be a lot larger and therefore take just a bit more time to come from server to client and get loaded into dom.
Your trying to use a third party product to monitor our client side processing but you have to modify our default performance setting to do so. That doesn't sound like a great idea but if the data you get from Dynatrace is providing you some sort of good input then you need to determine if it's worth it. In my opinion a monitoring tool shouldn't have to disable performance settings to work.
The history behind this setting even being available was simply to allow for easier debugging of the scripting. When uncompressed it's easier to add break points, see true variable names, and step through the code etc. However, browser debuggers now allow you to click a button, aka tidy print, to uncompress the content so it's easier to debug. I haven't had to use this setting in many is years.