Dirk Munk wrote: > The next item on the performance enhancements is pipelining. With > pipelining several several http requests are packed into one TCP packet. > > 1. network.http.pipelining = true > > 2. network.http.pipelining.maxrequests = 64 > > Up to 64 requests into one tcp packet, seems a bit much perhaps, but > remember that the network buffer sizes were increased to 32 MB. > > With all the changes I made so far, Seamonkey is unrecognisable fast now.
Have you done any testing to optimize these settings? I have often seen diminishing returns as parameters are increased. How much improvement do you see with halving your figures as an example? Perhaps that would suffice and leave more memory available for other parameter tuning. As I noted in an earlier post in this thread, it would be nice if someone could put together an article on tuning SeaMonkey for systems with more memory. This might need to be broken out by platform, as I am sure that Windows differs from Linux that differs from OS X. Dave _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
