{"id":3861,"date":"2015-11-09T00:01:41","date_gmt":"2015-11-09T08:01:41","guid":{"rendered":"http:\/\/www.atumvirt.com\/?p=3861"},"modified":"2015-11-09T00:01:41","modified_gmt":"2015-11-09T08:01:41","slug":"setting-a-load-management-policy-xenapp-7-x","status":"publish","type":"post","link":"https:\/\/avtempwp.azurewebsites.net\/2015\/11\/setting-a-load-management-policy-xenapp-7-x\/","title":{"rendered":"Setting a Load Management Policy (XenApp 7.x)"},"content":{"rendered":"

XenApp does a decent job distributing users out of the box, but one of the things that can catch users off guard is receiving a server that is very busy that is still accepting new connections, or worse, not accepting connections at all, despite having plenty of free resources.\u00a0 Both of these situations can be addressed by setting a load management policy in Citrix Studio.\u00a0 The available settings are shown below.<\/p>\n

\"lm_1\"<\/a>8<\/p>\n

As you can see from this image, the default \u201cConcurrent logons tolerance\u201d is 2 logons.\u00a0 This number can be quite a pain point if you have a large user base that tends to log in around the same time but a relatively small pool of servers.\u00a0 Additionally, CPU usage and memory usage aren\u2019t used for calculating load by default.\u00a0 The settings I recommend setting are as follows:<\/p>\n

Concurrent logons tolerance: 4<\/p>\n

CPU Usage: 70%<\/p>\n

Memory Usage: 70%<\/p>\n

Maximum number of sessions: 50<\/p>\n

 <\/p>\n

By increasing the concurrent logons, we can ensure a much greater number of users can begin a logon during the “shift rush”.\u00a0 Logons are an intensive process in terms of CPU, IO and processes, so you don\u2019t want to crank this too high.\u00a0 I do encourage you to do testing and find out what your environment can handle, or use a tool like LoginVSI to benchmark it for you.<\/p>\n

CPU usage and memory usage should provide ample room for existing users to continue to work without packing them in too densely.<\/p>\n

Finally, the maximum number of sessions \u2013 realistically I haven\u2019t seen servers get this dense in years due to compute limits being a bottle neck long before session limits.\u00a0 With that said, I\u2019d hate to be the guy to explain why 250 users unnecessarily lost their work all at the same time when they could have been balanced across the other servers.<\/p>\n","protected":false},"excerpt":{"rendered":"

XenApp does a decent job distributing users out of the box, but one of the things that can catch users off guard is receiving a server that is very busy that is still accepting new connections, or worse, not accepting connections at all, despite having plenty of free resources.\u00a0 Both of these situations can be […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[10,75],"tags":[121],"_links":{"self":[{"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/posts\/3861"}],"collection":[{"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/comments?post=3861"}],"version-history":[{"count":0,"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/posts\/3861\/revisions"}],"wp:attachment":[{"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/media?parent=3861"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/categories?post=3861"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/avtempwp.azurewebsites.net\/wp-json\/wp\/v2\/tags?post=3861"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}