On Wednesday 07 February 2007 21:24, [EMAIL PROTECTED] wrote: > > Running firefox as a local app is expensive! > > IMHO you need 512M ram (256M for firefox to cache in plus the ram to > > run the thin client and firefox app, java, flash etc) > > You need a processor to do the work, so 200MHz (ebox2300) and 500MHz > > (via EPIA) etc are out. > > Big processors need fans, make noise, void the beauty of the thin > > client. > > 512mb ram? 256 for cache? I seriously doubt I need that much. > Cache I can do away with by using squid.
I am talking about firefox's xserver cache, so it can't be done with squid, and it will kill your thin client *every time*. Quite ordinary sites use all the ram eg gallery in slideshow mode. On my site 127 photos eates 256M on the thin client. Every time picture 127 == dead client! Google is your friend. (firefox memory usage) James ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
