[FreeNX-kNX] Minimum bandwidth req's
Hristo Benev
hristo.benev at waveroad.ca
Fri Feb 23 14:31:42 UTC 2007
Igor Manassypov wrote:
> In my tests I have no audio, and I was trying to scroll a pdf document.
> The test line is roughly 400 kbps upstream, and the session was really
> slow. I wonder if there are any settings you can tune?
>
> On Fri, 2007-02-23 at 12:00 +0100, freenx-knx-request at kde.org wrote:
>
>> Send FreeNX-kNX mailing list submissions to
>> freenx-knx at kde.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://mail.kde.org/mailman/listinfo/freenx-knx
>> or, via email, send a message with subject or body 'help' to
>> freenx-knx-request at kde.org
>>
>> You can reach the person managing the list at
>> freenx-knx-owner at kde.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of FreeNX-kNX digest..."
>>
>>
>> ________________________________________________________________
>> Don't forget to check the NX Knowledge Base:
>> http://www.nomachine.com/kb/
>> Please also check the FreeNX Wiki+FAQ for hints.
>> http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>> ________________________________________________________________
>>
>>
>>
>> Today's Topics:
>>
>> 1. Re: Minimum bandwidth req's (Jo-Erlend Schinstad)
>> 2. Re: Memory leak in nxagent, with patch (Dimitar Paskov)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Thu, 22 Feb 2007 18:39:42 +0100
>> From: "Jo-Erlend Schinstad" <joerlend.schinstad at gmail.com>
>> Subject: Re: [FreeNX-kNX] Minimum bandwidth req's
>> To: "User Support for FreeNX Server and kNX Client"
>> <freenx-knx at kde.org>
>> Message-ID:
>> <bc66a2e50702220939j64efaa63j8283365012848a2f at mail.gmail.com>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>> On 22/02/07, Igor Manassypov <imanassypov at cicore.com> wrote:
>>
>>> >From your experience, what are the minimum bandwidth requirements for
>>> near-realtime response from nxserver? I cant figure that part out, I
>>> need to calculate how many concurrent clients can a particular line
>>> sustain.
>>>
>>>
>>> Thanks!
>>>
>>>
>>> -igor
>>>
>> Wow, that was one large post. Well, a friend of mine told me he was
>> using nx via gprs, which is about 30kbps, I think. It's abit difficult
>> to answer your question, other than the standard "it depends". Because
>> it does, depend on what you'll be using nx for. Nx uses advanced
>> caching and compression techniques, which makes nx really fast. Do you
>> use audio? One way, or both ways? That requires bandwidth. Do you only
>> use applications with more or less static appearance? That won't
>> require alot of bandwidth, because it's cached on the client. I've
>> used tree concurrent connections on a 384kbps upstream line, and that
>> went very well. That was without audio. I could probably have added at
>> least two clients without problems. If I were you, I'd monitor the
>> clients bandwidth usage while connected to the server. Do the things
>> your users will be doing and see for yourself. Divide your available
>> bandwidth by the peak bandwidth usage from the test, and you'll have
>> the smallest number of clients you can have.
>>
>> Good luck :)
>> Jo-Erlend
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Fri, 23 Feb 2007 11:11:41 +0200
>> From: Dimitar Paskov <pascoff at nola7.com>
>> Subject: Re: [FreeNX-kNX] Memory leak in nxagent, with patch
>> To: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>
>> Message-ID: <200702231111.41668.pascoff at nola7.com>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> I forgot to mention, I use nxclient 1.5.0-141, nxagent Version 1.5.0 and
>> freenx 0.5 ... I haven't tried with different versions of the client and the
>> server and I didn't try the patch yet ... What is the meaning of
>> this "backing store" option, what does it change and how it affects the
>> problem with memory leak?
>>
>>
>>>> Yes, you are right, when I close the session (or kill nxagent which is
>>>> the same) and open a new one everything is ok ... the problem is that I
>>>> don't want to close the session every time the memory of the client is
>>>> full ... I
>>>> just want to kill the application which "fills" the memory or better just
>>>> flush the cache and continue to work ...
>>>>
>>> Well did it occur also with older version like 1.4.0?
>>>
>>> Have you tried the memleak patch and see if it fixes the problem.
>>>
>>> Have you tried to disable the backing store of your local Xserver?
>>>
>>> cu
>>>
>>> Fabian
>>> ________________________________________________________________
>>> Were you helped on this list with your FreeNX problem?
>>> Then please write up the solution in the FreeNX Wiki/FAQ:
>>> http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>>> Don't forget to check the NX Knowledge Base:
>>> http://www.nomachine.com/kb/
>>>
>>> ________________________________________________________________
>>> FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>>> https://mail.kde.org/mailman/listinfo/freenx-knx
>>> ________________________________________________________________
>>>
>> ------------------------------
>>
>> ________________________________________________________________
>> Were you helped on this list with your FreeNX problem?
>> Then please write up the solution in the FreeNX Wiki/FAQ:
>> http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>> ________________________________________________________________
>> FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>> https://mail.kde.org/mailman/listinfo/freenx-knx
>> ________________________________________________________________
>>
>> End of FreeNX-kNX Digest, Vol 30, Issue 26
>> ******************************************
>>
>
> ________________________________________________________________
> Were you helped on this list with your FreeNX problem?
> Then please write up the solution in the FreeNX Wiki/FAQ:
> http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
> Don't forget to check the NX Knowledge Base:
> http://www.nomachine.com/kb/
>
> ________________________________________________________________
> FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>
PDF is considered as IMAGE so much of the technics used to accelerate X
are not used it is simply image transfer.
In my tests if I set NXclient to WAN it could jump to 800K when reading
PDF setting it to d-up drops down to 300K, but quality drops too.
Note: I tested in LAN environment.
But if you use it for text editing; e-mail reading the average BW used
is around 64-100K.
In addition you can play with image compression settings.
Hristo Benev
http://hbcom.info
More information about the FreeNX-kNX
mailing list