Hello, I did a small prstat -U lookup on our servers.
We have a bit more than a stripped-down kiosk session which would only run Xsun and uttsc - we also have a CDE window manager and my FLButselector variant of the three-button selector. An idle session thus takes about 25-35Mb of RAM, while a session with a single uttsc connection takes about 40Mb (of which my bash wrapper uttsc-direct seems to hog up 3Mb), a 2-uttsc session takes 66Mb. An admin's session with 4 uttsc's and a number of dtterm terminal shells takes a whopping 140Mb. One stray Xsun process consumed 800Mb though. Strange... So I guess a 100Mb estimate may give a good headroom for double or triple expansion in a certain scenario of one uttsc and no window managers in a kiosk session. This was stat'ed on a SPARC SRSS 4.0 (running on a Netra X1, with its 500MHz US-II CPU being okay for the task of at least 10 uttsc sessions to Windows with lags noticeable, but well under 1 second - except for certain bugs with MS Office and animated websites' terminal performance). All desktops run at 1280*1024. Thursday, February 5, 2009, 6:51:13 AM, Craig wrote: CB> You can go with a conservative number of 100 MB per active session if CB> doing the SRWC Kiosk descriptor or CAM without a windowing manager. CB> The only thing that will really differ is the Xsun/Xnewt process if you CB> have screens that are larger than 1280x1024. In reality, 60 is probably CB> good for that number, where as multihead instances or large resolutions CB> will consume more. Just do a prstat -u $USER where $USER is an active CB> kiosk/CAM user ID. -- Best regards, Jim Klimov mailto:[email protected] _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
