16 bit or 256 Colors?? (thin clients)

[bran2235]

Hi everyone-
My WTSs are set at 256 colors... We publish a desktop to our end users who connect via WYSE Winterms and Neoware Thin Clients...

The terminals are set to 256 colors (I thought it would be best to match my server's settings (?) ... Would we be sacrificing performance if we set our thin clients to, say 16 bit??...

What's the rule of thumb here when publishing a desktop and using Thin Clients to connect to it?? (Colors)??


Any advice is appreciated!!
Brandon

 

[patrickrouse]

The performance hit comes by way of extra bandwidth, but not a big deal if this is over a LAN connection to the MetaFrame Servers.

If there is no lack of bandwidth, and the app looks a lot better in 16 bit color, then give it a try.



Patrick Rouse
Microsoft MVP - Terminal Server

http://www.workthin.com

 

[bran2235]

Does it take more Bandwidth to push 16 bit colors/screenshots as compared to 256?? Are there any citrix guidelines for using one setting at your console/server and different color setting at your endusers session??

I just remember hearing in one of my Citrix classes that the more colors the bigger performance hit on the server(s)... then, I read something not too long ago (can't remember where) that said just the opposite now...

I'm running XPe SP2 FR2 WinSP3

Thanks everybody!
Brandon

 

[patrickrouse]

It absolutely takes more bandwidth, but I can't quantify the performance hit (if any) on the server. The extra bandwidth on an RDP connection is about 3-4Kbps more than a 256 color connection at the same resolution, so I image the difference for an ICA connection is similar.

The display settings on the server have no effect on the client, unless you're only specifying the settings you enter in a published application.

I use 16 bit color on almost every session, because many applications look like garbage at 256 colors.

Patrick Rouse
Microsoft MVP - Terminal Server

http://www.workthin.com