Hey has anyone updated the page speed macro? I can't seem to get it to work on 1.02.

"invalid macro definition" is the error message on startup

thanks,
seraphim

Seraphim,

Just had the same thought. Had to find a new location for it, as the old no longer exists.

I'm trying the following, but not sure if it is working or not.

============================================================

MENUS

# ----- Layers

%ifplugin layers

CloseLayer{
layers(Close,Close Laye&r\tCtrl+F4)
layers(CloseAll,Close All La&yers\tCtrl+Shift+F4)
layers(CloseAllOther,Close O&ther Layers\tShift+F4)
-
macros(ToggleSpeed)
}

&Layers{
%ifplugin macros
macros(Layers,&Options...)
-
%endif
layers()
}

%endif

# ----- Sessions



==============================================================




MACROS

EnginesSync{
$SearchEngineURL=getpref(STRING,$SearchEngine); $SearchEngineName=getpref(STRING,$SearchName); $n=0; while($n!=10) &EngineLoop;
setcheck("macros(SearchLock)",getpref(BOOL,$sl));
setcheck("macros(Keyword)",getpref(BOOL,$kw));
setcheck("macros(ToggleSpeed)", getpref(BOOL, "network.http.pipelining") == true ? true:false);
# Support for K-Meleon 0.9 engine macros:
&EngineSync;
}
EngineLoop{
setcheck("macros(SE".$n.")",getpref(STRING,$se.$n.".url")==$SearchEngineURL ?true:false); $n=$n+1;
}
#--------------------

# PAGESPEED MACRO

# TOGGLE PAGESPEED

ToggleSpeed{
menu = "Enable Page Load Speed-Up"
getpref(BOOL, "network.http.pipelining") == true ? &DisableSpeed:&EnableSpeed;
&Sync;
getpref(BOOL, "network.http.pipelining") == true ? $warn = "enabled":$warn = "disabled";
Alert("Page Load Speed-Up has been ".$warn."!");
}

# ENABLE PAGESPEED

EnableSpeed{
# TURN ON TIMER BASED REFLOW MANAGEMENT
setpref(BOOL, "content.notify.ontimer", true);

# SETS THE ALLOWED TIME BETWEEN REFLOWS IN MICROSECONDS
setpref(INT, "content.notify.interval", 100);

# SET THE NUMBER OF REFLOWS TO DO BEFORE WAITING FOR THE REST OF THE PAGE TO ARRIVE
setpref(INT, "content.notify.backoffcount", 200);

# ENABLE IMPROVED PIPELINING
setpref(BOOL, "network.http.pipelining", true);
setpref(BOOL, "network.http.pipelining.firstrequest", true);
setpref(INT, "network.http.pipelining.maxrequests", 100);
setpref(BOOL, "network.http.proxy.pipelining", true);

# INCREASE MULTI-THREADED DOWNLOAD PERFORMANCE
setpref(INT, "network.http.max-connections", 60);
setpref(INT, "network.http.max-connections-per-server", 32);
setpref(INT, "network.http.max-persistent-connections-per-proxy", 16);
setpref(INT, "network.http.max-persistent-connections-per-server", 8);

# REMOVE PAINT DELAY WHEN LOADING
setpref(INT, "nglayout.initialpaint.delay", 0);

# DISBALE KEEP-ALIVE
setpref(BOOL, "network.http.keep-alive", false);
setpref(BOOL, "network.http.proxy.keep-alive", false);
}

# DISABLE PAGESPEED

DisableSpeed{
setpref(BOOL, "content.notify.ontimer", false);
setpref(INT, "content.notify.interval", 1000000);
setpref(INT, "content.notify.backoffcount", 5);
setpref(BOOL,"network.http.pipelining", false);
setpref(BOOL,"network.http.pipelining.firstrequest", false);
setpref(INT, "network.http.pipelining.maxrequests", 4);
setpref(BOOL, "network.http.proxy.pipelining", false);
setpref(INT, "network.http.max-connections", 24);
setpref(INT, "network.http.max-connections-per-server", 8);
setpref(INT, "network.http.max-persistent-connections-per-proxy", 4);
setpref(INT, "network.http.max-persistent-connections-per-server", 2);
setpref(INT, "nglayout.initialpaint.delay", 250);
setpref(BOOL, "network.http.keep-alive", true);
setpref(BOOL, "network.http.proxy.keep-alive", true);
}

#--------------------

N

i just went into the browser configs and manually changed all the settings. what you have should work. i dont know why it wasnt working when i was doing it. Somewhere there was a bracket missing and i didnt want to try to figure out where it was.

you should be able to go to the browser config and check some of those settings and if they are changed then it is working. it is a pretty noticable difference in page rendering when it is working.

seraphim

Seraphim,

Are you saying that what I posted here worked for you?

(I'll double check my settings to see if there is a bracket missing now.)

N

nah, the macro just changes settings in pref.js so i just did it manually which has the unfortunate downfall of being more time consuming to turn on/off but i dont really turn it off so it isnt a big deal for me. If KM is starting fine you should be able to check if Page Speed is on by typing about:config in the URL bar and then searching for network.http and making sure that even just a couple of those settings (ie network.http.keep-alive = false).

Seraphim

I have another quick ? as I have been out of the loop for awhile (Baghdad 1+ year). Is or when will KM be 64bit compatible?

Thanks,
Seraphim

Seraphim,

Can't say if KM will be 64bit compatible or not. There are problems down the road with the Gecko engine as FF developers have cut off some of the codes required to keep KM backwards compatible with W9x.

Hope others who understand this better will jump in here and give a better explanation than I can.

N

I would like to learn more about these parameters. I have tested both Firefox and K-M with and without those alleged speed-improving parameters and I notice no difference in web page rendering speed.

I am on a broadband connection, but I saw no improvement several months ago when I was on dial-up. I simply never see any difference.

I do not doubt that some people see a significant difference, otherwise these recommendations would hardly flourish throughout the web. I wonder, however, why I never see any difference, both with dial-up and broadband. Curiouser and curiouser.

Peabody,

This set of tweaks is from Johnny Sim-Bravenboer and I don't know if he is still around or not or whether he or anyone else has worked on officially porting it over to either KM 1.02 or KM 1.1. Or even if they still work or not. (I don't know much here at all!)

As for whether or not they do anything to speed up KM...that is the 64 thousand dollar question. Someone better qualified than I should be able to answer that.

<sigh>

N

you have to add


-
macros(Default, Set As Default Browser...)

after

-
macros(ToggleSpeed)

in the menus.wasnt that hard to figure out being i dont know a thing bout programin and it didnt take me long to figure it out.