How many Swing users fit on one server?

SwingBridge runs your Swing application on a server and shows it in a browser. Every user gets a session on that server, and every session costs memory. That cost is your server bill.

SwingBridge 1.3 shipped on 9 September and spent that release on memory optimization. On a 4 GB server with every user active, it fits 38 users.

Join Eftun Türkmen, who did the work, and Miikka Andersson for what went into the release, what the testing showed and how we ran it, and a first look at what we are working on for 1.4.

What you'll learn

• What changed in 1.3, and where the memory was going
• How 16-bit color and per-user screen sizing cut it further
• What HiDPI rendering costs, and what it buys
• How we ran the tests: the rig, the workload, and what we checked
• What we are working on next for 1.4