{"id":619,"date":"2022-03-29T05:00:00","date_gmt":"2022-03-29T09:00:00","guid":{"rendered":"http:\/\/192.168.1.40\/?p=619"},"modified":"2022-03-31T13:36:38","modified_gmt":"2022-03-31T17:36:38","slug":"ensuring-citrix-applications-perform-under-pressure-with-eggplant","status":"publish","type":"post","link":"http:\/\/192.168.1.40\/blog\/ensuring-citrix-applications-perform-under-pressure-with-eggplant\/","title":{"rendered":"Ensuring Citrix Applications Perform Under Pressure With Eggplant"},"content":{"rendered":"\n

<\/p>\n\n\n\n

In my performance engineering circles, I hear a lot about shifting left and optimizing code. The emphasis is on early feedback during the development process, and it is great that this conversation is happening. However, there are MANY companies who do not develop software and use packaged applications across large numbers of people. These applications are not developed, they are deployed. The original code may have been tested by the vendor, but it may be heavily customized or extended. To deploy these applications without doing performance and load testing greatly increases the risk of a bad user experience or production outages during high usage times. <\/p>\n\n\n\n

Adding to the complexity, some of these applications are deployed using Citrix Virtual Apps and Desktops.  Even if the native application itself has been load tested, it requires performance validation of the Citrix environment itself. This is because the Citrix environment itself can be complex:<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

*From Citrix Documentation<\/p>\n\n\n\n

Anyone of these access points, or layers can be accidentally misconfigured. Settings need to be validated and tuned based on the individual implementation.<\/p>\n\n\n\n

How prevalent is Citrix today? <\/h2>\n\n\n\n

According to the Citrix website, it\u2019s used at:<\/p>\n\n\n\n