Friday, July 18, 2008

[THIN] Re: Video Performance

Well there is an additional layer of processing whenever going through the CSG. It is an SSL proxy, i.e. all packets must be de-crypted in software on the CSG box. The CSG was never really designed to be anything other than a quick and easy way to add SSL to the session. Conceptually it is adding another layer of processing to the equation. Even the CAG is not necessarily a highly optimized system although it works pretty well up to about 100 users. The Netscaler/Access Gateway Enterprise is clearly more optimized for this function and I know from experience it does not degrade performance.

 

With CSG it is more of an unknown, the speed and power of the box matter and if you are combining the roles on the same system you are asking it to do a lot of simultaneous work for incoming and outgoing packets. Without more information I would simply suggest that the CSG software /hardware cannot keep up with the traffic you are sending through it. You said there are less than 50 users at each location, how many total concurrent users? In my opinion If you are more than 100 or 200 users than you really are beyond CSG/CAG and should be looking at Netscaler Access Gateway….

 

 

Steve Greenberg

Thin Client Computing

34522 N. Scottsdale Rd D8453

Scottsdale, AZ 85266

(602) 432-8649

www.thinclient.net

steveg@thinclient.net

 


From: thin-bounce@freelists.org [mailto:thin-bounce@freelists.org] On Behalf Of Chris Grecsek
Sent: Friday, July 18, 2008 10:24 AM
To: 'thin@freelists.org'
Subject: [THIN] Video Performance

 

We provide published desktops via Citrix/terminal services delivered via the internet. All users come in through the web interface/CSG via high speed, burstable (up to 100mb) connections. Most of the branch offices are <50 users so connectivity/maxxing out the pipe is not an issue. We don’t use any bandwidth restriction policies – users can use as much bandwidth as they’d like. We have bandwidth monitoring to look at all traffic and have our firewalls setup so that only Citrix traffic is using the burstable connection. Latency is sub 20ms and we have no packet loss.

 

Like everyone else using Citrix we’ve had challenges with video performance on the published desktop (Windows media player works great – Flash/other codecs, not so much). We had an interesting discovery today and I was curious if anyone could answer why/how this happens…when we connect to a published desktop via the WI/CSG (from one of our branch offices) video performance is bad. We ran a test today from within the datacenter where we connected to a published desktop, locally (from a laptop at the DC), using the Program Neighborhood as opposed to coming in over the WI/CSG and low and behold, video performance was excellent.

 

When we look at the amount of session bandwidth being used it’s nearly the same when coming in via the WI/CSG as it is when testing at the datacenter. So I guess the question is, is there something with the way the WI/CSG works that would be restricting/degrading the video performance (we ran performance counters on the WI/CSG and it doesn’t seem to be working very hard), is there a difference between using the Program Neighborhood verses the web client, etc.?

 

We’re on Citrix 4.5, latest rollups, latest version of the client, etc.

 

If anyone has any ideas, it would be much appreciated.

 

Thank you!

 

Chris

 

-----------------------------

chris grecsek | centered networks | t:415-294-7776 | f:415-294-7772 | chris@centerednetworks.com

No comments: