Brian Nitz wrote:
> Rich,
>
> I'm working on a on an updated Sun Ray Optimization guide for Solaris 
> Nevada builds.  Even though SRSS+NV isn't a supported configuration,  
> I'm glad to hear that others are using Sun Ray on Nevada builds.  Here 
> are a few things I would recommend:
>
> - Make sure the xscreensaver hacks are disabled. 
>     Since it's possible some of your users have Xscreensaver hacks 
> enabled in their home directory, they may be consuming considerable 
> resources even when they are away from their desk and their session is 
> detached from a DTU.  the easiest way to prevent graphical hacks from 
> running on your server is:
>          mv /X11/lib/xscreensaver/hacks /X11/lib/xscreensaver/hacks.disabled
>
> - Turn off tracker file indexing (This came into the builds before 
> proper kernel file monitoring was available, so the fall back is a 
> particularly inefficient file change polling mechanism.)  To disable:
>
>     Select preferences->Sessions
>     Uncheck all items containing the word "Tracker".
>
>     If you want to disable tracker for everyone, remove these files:
>         /etc/xdg/autostart/tracker
>
>
> FireFox Memory consumption settings:
> By default, Firefox 2.0 will allow its memory cache to grow very large 
> (several Gigabytes!) and keep things such as closed tabs in the cache... 
> just in case the user should want to unclose or retrieve a tab.  Each 
> user can change the default cache behavior as follows:
>
>     * Create or edit a user.js file in $HOME/.mozilla/firefox/*/
>     * Add the following lines to user.js:
>
> user pref("browser.cache.memory.enable",true); user 
> pref("browser.cache.memory.capacity", NNNN);
> True enables the cache and NNNN represents the maxiumum browser memory 
> capacity.
>
>
> If you would like to make these changes system wide, make the following 
> changes:
>
>     * Edit /usr/lib/firefox/greprefss/all.js and add these lines:
> pref("browser.cache.memory.enable",true); 
> pref("browser.cache.memory.capacity", NNNN);
> True enables the cache and NNNN represents the maxiumum browser memory 
> capacity.
>
>     * Remove any user specific browser cache settings in individual 
> user.js files.
>
>
>
>
> Please let me know if these help.
> _______________________________________________
> desktop-discuss mailing list
> desktop-discuss at opensolaris.org
>   
Thanks for the tips, they're useful for a regular desktop as well.

James

Reply via email to