On Sat, Feb 29, 2020, 23:07 Manoj Patil <[email protected]> wrote:
> Dear, > > Thank For your appreciation . > > The only thing that I noticed is that there is no compression between the > server and the client. > Meaning that full sized base64 encoded PNG images are send to the client, > which causes a high network load. > No. PNG is compression, and an average of ~86 Kbps is not high network load. There is some overhead from base64, but that overhead is all but nullified by (1) the gzip compression that is generally automatically applied to WebSocket and (2) the speed that browsers can process that base64 data compared with alternative mechanisms that lack the overhead. > i am try to find out why more bandwidth is required for 600 connection and > how to reduced it. > > My Observation is--- > > we observe that in my colleague company those people used Microsoft > remote desktop Web client (using activex) for 1200 connection in 10 Mbps > for huge transaction. and > An average of 8 Kbps per connection sounds unlikely for any form of steamed graphical data. > we used Xrdp+wine+Guacamole with 600 connection with 50 Mbps bandwidth . > > what protocol they are used ( Microsoft remote desktop Web client ) is > taking less bandwidth compare with Guacamole. > >From measurements of real-world use of the live demo environment deployed by my day job, I see the opposite of this. The overall bandwidth used between the users' browsers and the Guacamole servers is significantly less than the bandwidth used by RDP between guacd and the Windows servers. - Mike
