Alahndro

I've found some useful javascript tune-ups: The Last days I was forced to use an older machine for browsing while my main rig beside it was busy or unusable due to repairs or upgrades or whatever. Espescially I wanted to watch some youtube and found it being overloaded by the scripts. It wasn't even able to play 360p properly. Most of the time it ended in an endless spinning wheel until it failed with an error. That machine is able to play 1080 inside a native player. - CPU is a AMD sempron3000+ @ 1,8GHz. Single Core - Version: New Moon 28.10.7a1 (2024-06-28) It appeared that the javascript engine went completely bonkers. So I looked into the config to find some settings to play with and toggled the following entries: - javascript.options.parallel_parsing = false - javascript.options.wasm_baselinejit = true This made a HUGE diference! I don't know what the second option does but for me it is obvious that the parallel pre-loading and parsing and compiling overloads the CPU, precisely the caching of data and scripts. This parallel processing is helpful if you have at least 2 cores and some L3 cache, but it utterly destroys the pipelining of single-core CPUs. Of course this raises the latency a little bit, but it forces to process pages and scripts in a more serialized way. Now I can even switch the playback to 720p inside youtube, though with some framedrops but it can reach this level I also once found a site with palemoon x86 SSE2 and non-SSE2 compiled as deb-packages for linux. (Got dual-boot on this machine) Here it is much worse, obviously these miss some single-core tune-ups that roytam includes in his builds. Need to investigate that further

I just registered for this thread. First I want to express my highest respect and gratitude for the work you're doing in keeping older OSes alive and somewhat compatible to the modern web. I'm using you're builds many years on nearly all of my machines, mainly XP and also on older CPUs. Due to javascript demands I was forced this year to switch to edge on my main PCs using win7 to use some important sites. Just now I was greeted with the prospect of EOL for Edge on win7 and I find myself again hitting the obsolence wall. F**k M$. So back to the basics and this let me here again trying to find out what it would take to improve usability of your builds. I checked using F12 and found "CustomElements not defined" Long story short: What would it take to implement CustomElements in JS? More and more sites use it and let our browsers falter. Thanks so far.