Ferry fstelte

In my previous blog about Login PI3 I showed how to install and configure Login PI 3. In this blog I will show you how to create new applications in Login PI 3 and will show you how to add basic steps for that application. In this article I will use SumatraPDF (because it is my favorite PDF viewer) as an example, you can replace SumtraPDF with your own application as wanted.

On the sixth of November 2018 Login VSI introduced the Release of Login PI 3. In this blog I will take you with me during my exploration of this new version of Login PI. Version 3 of Login PI is been designed and built from scratch. The need for a windows server to run the application on is gone. Login PI 3 is based on an appliance. To be able to run the appliance you will need ESX 5.

In my lab I have Login PI running to do research. While looking at the dashboard I noticed the following thing, normally logon and running times are around 12~14 seconds. Since an x period the Logon and running times went up to around ~60 seconds (see first pictrure, at point 1) Because I have RES WM also running in my Lab i was quite easy to do troubleshooting on what was causing the slower logon times.

Recently I have been working on a performance scan for a customer. The customer wanted to have a newly built XenApp 7.6 environment validated. Ofcourse I used Login VSI to do the task at hand. While starting the validation, the customer expected to reach about 80 concurrent users on one physical host (with 3 virtual XenApp servers on it). After getting VSI to run in the environment I started a first small test, with 30 users to see what the enviroment did.

In the previous part of this serie of blogs I wrote resource sharing. Also discussed the different kind of technologies, in this article I want to go into the load test I have performed at the customer. All tests are performed with the officeworker workload, 150 sessions, 60 second launch interval. The following test are performed: Baseline office worker (DFSS/RES WM on (default)) DFSS on RES WM off DFSS off RES WM on (default) DFSS off RES WM on (85%) DFSS off RES WM off Below is a chart that represents the test results in % relative to the first (baseline) test.

Intro Currently I am at a customer that uses RES Workspace Manager on Windows Server 2008R2 XenApp servers. Because lots of users logon to your XenApp servers, one can consume all the resources on the server. Thankfully Microsoft and Citrix both have their own technologies to prevent users from eating up all the resources. Both Microsoft and Citrix say that if using XenApp 6.x you should use either Dynamic Fair Share Scheduling (Microsoft technology) or Citrix CPU utilization (Citrix Technology).