Joel, memory is certainly one limiting factor, but CPU is often the more important constraint on a SunRay. With a hundred users on a box if specifc apps start eating CPU, it doesn't take long to grind the box into the ground. Browser loading pages with poorly written javascript, java applet that's misbehaving, looping flash animation ... are just some of the things that can cause this to happen [check out bugzilla and look for memory issues to see how many are related to poorly designed pages].
The browser would appear to be the biggest hog on the system with regard to memory consumption. If the user has 20-30 tabs open with plenty of graphics on them, you can see heap usage for the browser going over 100 Meg without any problem. Ideas have been knocked around to make the browser more efficient, from having it not store images in memory for hidden tabs, to improving how it allocates pixmaps on the xserver and/or having direct support in xorg for compressed pixmaps, but no one is currently working on implementing any of these ideas. JR Joel Buckley wrote: >>>Eric Boutilier wrote: >>> >>>Ok, but seriously, why minimize a user desktop? >>> >>> >>> > >The limiting factor on SunRay2 deployment is Memory >use on per User Desktop. 60 SunRay User Desktops >managed on a single SunRay Server appears to be typical... > >The top memory consumption programs are: > >- Xorg >- Mozilla >- Firefox >- Thunderbird >- StarOffice >- Gnome-Terminal > >In the target audience for SunRays, what are the primary >applications utilized on SunRays? > >Any reductions in Memory consumption of the above applications >results in a direct ability to scale SunRay User Desktops on a >single SunRay Server instance. > >Joel. > > >_______________________________________________ >desktop-discuss mailing list >desktop-discuss at opensolaris.org > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/desktop-discuss/attachments/20060518/e93986d0/attachment.html>
