Re: RDP Bandwidth Utilization

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

The answer to how much bandwidth RDP uses is effectively "as much as it can
get". Most applications will take as much bandwidth as they possibly can.
In general, more bandwidth is always better, although there are limits to
what's practical. This is where QoS can come in handy to throttle the amont
of bandwidth WTS sessions can use.

Fundamentally, the RDP protocol is simple data streams that are sent
between the client and the server. If the amount of data moving through the
stream is less than the amount of bandwidth that's available, then
everything will be fine and you'll have no problem. However, if the RDP
protocol tries to use more bandwidth than is available, then we see latency
and slow performance. We can limit the amount of bandwidth that is
requested by the session by disabling theme support and redicted printers
and drives, however it is impossible to say how much bandwidth it needs.

There are statements floating around on the Internet that say things like
"Citrix ICA uses 15kbps" (or 20k or 30k or whatever). There is one thing
that's critical to understand about these statements: Any statement about
ICA or RDP bandwidth usage simply refers to an average over some period of
time. The longer the time period, the more accurate the average.

In real life, ICA and RDP are extremely "bursty." If you don't touch the
mouse and nothing's happening on the screen, no data will cross the network
(except for the occasional keep alive packet). However, if you launch a new
program where the screen is continually updated, then the bandwidth
requirement shoots up.





"Glenn Zamorski" <Glenn Zamorski@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:34A034FF-E9A2-4A2E-A8DA-9C996B384737@xxxxxxxxxxxxxxxx
> Does anyone have any "official" (from MS that is) numbers for the
bandwidth
> used per session on an RDP session?
>
> For instance if you have 40 people coming in through a WAN link what is
> average Kbps each session uses. You could then generate the minimum size
pipe
> you need. Assuming RDP only - no data transfer.
>
> I've hunted around MS and the Net but I haven't found any definitive
> information. I'm trying to save my self a day of sniffer tracing!
>
> Glenn Zamorski
> MCSE


.

Relevant Pages

  • Re: RDP between sites.
    ... RDP will consume all the bandwidth it ... MVP Windows Server - Terminal Server ... connector at a remote site, so the staff there can use a database. ...
    (microsoft.public.windows.terminal_services)
  • Re: office assistant (office 2003)
    ... enormous amounts of bandwidth. ... I did a test last week where using RDP 6.1 ... whereas with our RDP Graphics acceleration it took about 2 seconds. ... > Virtual Client Solutions ...
    (microsoft.public.windows.terminal_services)
  • Re: RDP between sites.
    ... plus also are there any ball park figures as to how much bandwidth RDP will user per session? ... In this case the print data stream is transmitted from server to client as well. ... Am i correct in saying that RDP uses an asymentrical type connection, in that the remote site will be downloading more bits than uploading. ...
    (microsoft.public.windows.terminal_services)
  • Re: office assistant (office 2003)
    ... as it's important to guarantee enough bandwidth for your ... display driver with our own that draws compresses graphics and draws them ... I did a test last week where using RDP 6.1 ... Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: Is C99 the final C? (some suggestions)
    ... >> and with the least perceived lag, given a limited amount of bandwidth? ... but bandwidth is also an issue. ... but the future is peer 2 peer. ... I can do no such thing with stack ...
    (comp.lang.c)