You are right that the conditions are not the same everyday. That's why I asked because loadingtimes are never the same here and it is very difficult to find out the (small) differences with settings like these.
I will check the internet for testsites in the Netherlands as close as possible and try to find out the differences.
But when someone could tell me a little more it would be great ofcourse!!

Groeten!!!!

Fast Sjonny

You are right that the conditions are not the same everyday. That's why I asked because loadingtimes are never the same here and it is very difficult to find out the (small) differences with settings like these.
I will check the internet for testsites in the Netherlands as close as possible and try to find out the differences. May be forgotten but I am already using the settings but would like to 'finetune' them.
And euhhhh, when someone could tell me a little more it would be great ofcourse!!

Groeten!!!!

Fast Sjonny

RottweilerKing wrote:

A site someone else spoke of doing this image-loading delay on another forum was ]http://news.google.com

I have that problem with Google News, as well as with other similar sites. With any pipelining settings enabled, it can take 10-20 seconds for the images to finish loading. With no pipelining, the page/images load almost instantly. The only speed tweak I have enabled is nglayout.initialpaint.delay, and I have it set to 100.

Rob

I have tried to find out the difference with changing settings but I think for normal use the speedsettings are fine for me. Lower or higher values for the .interval then 100 seems to slow down a little (80-100-120 = 616-638-597 but changes everytime..)
Other settings for the .backoffcount the same.
Pipelining off is defenately slowing down also with pictures, with the paintdelay I had expected much difference but with reloading diff. pic's etc...
So, good work! ;-))
Jan.

I've found that

user_pref("network.http.keep-alive", false);
user_pref("network.http.proxy.keep-alive", false);

makes a huge difference for me. At least with my personal proxy. With these options at default values (true), I could see the KM was never opening more than 4 connections to my proxy server. Since it doesn't support keep-alive... The weirdest part is that no "network.http..." preference was set to 4.

Now KM is really opening as much connections as it can (my max is 30). And the overall performance (the fealing at least) is better.

So you have set them to false instead of true and KM is using more connections now? I'll give it a try ;-)))

Jan.

Marc - I can't find the two user prefs you mention. Did you create them yourself? Many thanks.

Fast Sjonny wrote:
> So you have set them to false instead of true and KM is using
> more connections now?

Exactly. At least that's what I saw on my linux firewall while looking at the connections opened by KM.


Brian wrote:
> Marc - I can't find the two user prefs you mention. Did you
> create them yourself?

Open "about:config" and filter on "network.http". You should see them in the list.

I'm on dialup. this one tweak makes a big difference. my one test site snaps into place instantly. try it to see if it works for you

===

disk cache - 32,768

my test site -

http://www.nvnews.net

it has graphics - animations - texts
==

my other tweaks =

memory cache - 3072 (I've 256mb of high speed ram - Win ME. unless you have windows 2000 / XP, 512 mb or above probably won't make much difference in speeding up your system)

user_pref("content.notify.ontimer", true);
user_pref("content.notify.interval", 25);
user_pref("content.notify.backoffcount", 50);
user_pref("nglayout.initialpaint.delay.", 1);
(I've tried - 4 - 8 - 16 - 50)

user_pref("network.http.max-connections", 48);
user_pref("network.http.max-connections-per-server". 8);
user_pref("max-persistant-connections-per-proxy", 8);
user_pref("network.http.max-persistant-connections-per-server", 4);
user_pref("network.http.keep-alive", false);
user_pref("network.http.proxy.keep-alive", false);

kerney