David H. Durgee wrote:
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
Increasing parameters without making sure there is memory available,
usually decreases performance, so I always start with making sure there
is sufficient memory available.
Increasing memory buffers rarely causes problems.
I increased the network memory buffers from .8 to 32 MB, but what is 32
MB for a system with Gigabytes of memory? Nothing.
The 4 GB memory cache I configured is a maximum value, if I don't open
too many tabs, I will never use that 4 GB.
Disabling the disk cache actually decreases memory usage, since the disk
cache has its own memory cache, to cache disk reads and writes.
It would be wonderful if you could set up test environments to see what
the parameters do in which situation. However, I don't have the means to
do that. So instead I raise the size of buffers etc. based on the
experience of decades of performance tuning.
So far it works fine. Maybe I waste a couple of MB, but who cares. The
only big memory user is the memory cache, and as I explained, Seamonkey
will only use the memory it needs, no more.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
