NoMachine NX 1.5.0 is finally out! Including sources of the GPL'ed NX Core libraries. It also sports a new NX Server Manager interface (still Beta).
- Ever wanted to have a usable remote desktop access to your KDE workstation even when thrown back to a modem dialup link? -- You should have used NX-1.3 or NX-1.4 or FreeNX already in the last 2 years!
- Ever wanted to be able to detach from your remote X session, and re-attach to it later? Or just recover a session lost by a network cut-off? Or move a remote X session to a different local workstation? -- You should be using NoMachine NX 1.4.0 or FreeNX already!
- Ever wanted to have sound come with your remote X session? -- NX-1.4 and FreeNX were here for you already since quite some time.
- Want to work on your home KDE Linux workstation from the office while sitting in front of your Windows notebook? -- You must have missed it: this works wonderfully already since a long time.
- Ever wanted to resize your remote NX session window by just dragging the window border with the mouse? -- Or toggle to fullscreen mode and back with a keyboard shortcut? NX-1.5.0 now brings this feature to your fingertips.
- Need to access from Linux remote Windows Terminal Sessions, but don't like the poor 8-bit color depth of the session? -- Go for NX-1.5 (or FreeNX-0.4.2 with the NX Core libs 1.5.0).
- Don't like the primitive, proof-of-concept type kNX NX client application that is in kdenonbeta? -- Go hack on it and make it better. Or wait and see if Chris Cook's effort in his Google SoC project bears some new fruits in the next few weeks...
The FreeNX Team is also currently busy with a whole list of things: write a release announcement for the 0.4.2 bugfix release, fight the SVN troubles plaguing our Berlios repository getting ready for release the 0.5.0 version which will sport seamless printing powers and a nifty new nxfish utility (derived from KDE's fish:// thingie).
Syndicate Blogs
LAN doesn't do NX justice
You really can't tell how great NX is till your trying to connect from a connection thats no faster than a 56k modem (6kb/s = high speed my ass), I used this to login to my home machine and it worked great! (I may of also gotten sound if I hadn't mangled arts's config right before leaving on the trip)
I only wish my town had public wireless in the town square area so I could use NX more.
I wish someone would do a benchmark to show how many concurrent clients different speed systems could handle, like how many clients doing things an old 500 mhz celeron could handle, an average new desktop, and maybe a higher end system.
Benchmarking Recipe
...show how many concurrent clients different speed systems could handle...
----
What you are asking is not very much NX-specific.
You want to know how many concurrent user sessions a specific system can handle.
Well, with NX this is more easy to find out than without. Just run not one, but two, five, 10, 20 sessions concurrently from the same NX client, possibly even as the same user. Yes, that is possible. Yes, your client will have many session windows to handle. (And yes, you can possibly hose up some of your personal desktop settings if you assume you had saved a special option to your ${KDEHOME} in a session you are about to close -- and later you close another session which remembered a different setting...)
As a rule of thumb you can try to verify these figures: after the first KDE user session is up and running, any additional session consumes...
...50-100 MHz of CPU,
...50-100 MByte of RAM and
...50-100 kBits/sec of network bandwidth.
Assuming your "avarage new desktop" is a 3 GHz P4, 1024 MByte machine connected 100 MBit/sec (available here for under 600 EUR), this should make it possible to let at least 10 people run concurrent sessions, maybe 20. RAM being the bottleneck here -- upgrade to 2 GByte (for additional 150 EUR) and you should be good for 20-40 concurrent sessions.
Benchmarks...
I wish someone would do a benchmark to show how many concurrent clients different speed systems could handle
----
Why don't you run one yourself?