On 12/26/2016 02:03 PM, Wolfgang Rosenauer wrote:

Unfortunately I cannot answer that question. The main reason is that I do not share the same experience. For me everything seems to work just fine w/o a different to previous versions.

Wolfgang

Same here, FF 50.1.0 is running blazing fast, so the experience isn't shared either. It sounds like the problem lies elsewhere. Even when testing FF under 42.2 on a 6-7+ year old laptop, it ran snappy. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

James Knott composed on 2016-12-26 22:43 (UTC-0500):

How many windows do you have open? I generally run 15-20 or so. Regardless, performance is much worse than on 13.1. Even then, I'd have to kill Firefox occasionally as it would bog down after a while.

Window count could conceivably have something to do with it. Most multi-tasking people I think are multi-tab users, not multi-browser window users. That goes particularly for Mozilla.org devs. So there may not be much testing involving many open windows. Is the FF of which you complain built with GTK3, or with GTK2. If ~49 or newer the default is GTK3, so about:buildconfig should say GTK2 if built with GTK2, or include no GTK string if built with GTK3 and ~49 or newer. Maybe which GTK makes a difference. FF ESR is still built with GTK2. Does it help to start FF using -safe-mode or with a virgin profile? ISTR you are a user highly in favor of and equipped to use IPV6. Maybe IPV6 is part or root of your observations? Here all booting is done with ipv6.disable=1 on kernel cmdline. Current, recent and pre-release Gecko versions here all behave about the same WRT to responsiveness. My most used FF is 45.6ESR, which currently has an estimated 38 open tabs, while I have other Gecko browser windows open with as many as an estimated 60+ tabs. Total Gecko browser window open count is currently 5 on this 42.1. Slowdowns only seem to occur when Facebook pages are open, but they clear up on their own given time. My SM browser history in which I visit FB is 52,428,800 bytes ATM, about 2.5 times the default allocation. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/27/2016 02:16 AM, Felix Miata wrote:

ISTR you are a user highly in favor of and equipped to use IPV6. Maybe IPV6 is part or root of your observations?

Why do so many people seem to think there's a problem with IPv6. As I mentioned in another note, I have been running it for 6.5 years and not had a problem with it. I access many IPv6 sites and I wouldn't know they were IPv6, if I didn't use the ShowIP browser add-on. What happens when you try to access a site is you get a DNS record that may contain an IPv4 A record, an IPv6 AAAA record or both. If both IPv6 is preferred. Beyond that, there is no difference between using IPv4 & IPv6. In an earlier note, I provided this link, showing IPv4 & IPv6 performance were virtually the same: http://results.speedtest.xfinity.com/result/1457254644.png This test was run on Chromium. It wouldn't even run on Firefox. Clearly it's not IPv6 that's causing the problem, but some issue with Firefox, including perhaps the implementation of it in 42.2 or at least my installation of 42.2. I have even tried reinstalling Firefox. BTW, this is on an Intel i7 quad core CPU with hyperthreading and 16 GB of memory, so it isn't exactly an anemic computer. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

about: performance Typo:

about:performance omit the space!

On 12/27/2016 09:19 AM, James Knott wrote:

On 12/27/2016 05:24 AM, Florian Gleixner wrote:

...

How many windows do you have open? I generally run 15-20 or so. Regardless, performance is much worse than on 13.1. Even then, I'd have to kill Firefox occasionally as it would bog down after a while.

You can check, which tab/window eats up your cpu. open a new tab and enter:

about: performance

in the address line.

When I do that, I see: "MemChaser may currently be slowing down Firefox". I'll try disabling that, to see what happens. I also get the slowing down message on a couple of web sites, but I've had those sites open since long before I installed 42.2.

Firefox seems to be running better, since disabling MemChaser, and top shows it's using about half the CPU & memory it was before. However, that Xfinity speed test site still won't work in it, though it runs fine in Chromium. It used to be OK before updating to 42.2. Perhaps I should just reinstall 42.2 from scratch. I had updated from 13.1. If I do that, I might as well switch to UEFI. Any issues with that? My /home is on a separate partition and the rest of my system can be recreated. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/27/2016 01:57 PM, Patrick Shanahan wrote:

...

Firefox seems to be running better, since disabling MemChaser, and top shows it's using about half the CPU & memory it was before. However, that Xfinity speed test site still won't work in it, though it runs fine in Chromium. It used to be OK before updating to 42.2.

* James Knott [12-27-16 12:33]: [...] try http://speedof.me/

it is only html5, no flash

[....]

Both speedtest & Xfinity have HTML5 versions. While better than flash, they're still not as good as with Chromium. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 27.12.2016 15:26, Carlos E. R. wrote:

On 2016-12-27 11:24, Florian Gleixner wrote:

...

You can check, which tab/window eats up your cpu. open a new tab and enter:

about:performance

in the address line.

Now, this is a wonderful addition! I wanted it for ages.

It tells me that there is an amazon tab that is taking 9% of the CPU.

It lacks some features, though. For example one button to jump to it. When You have a hundred tabs open, finding a particular one becomes "difficult".

You can close or reload the tab from "about:performance". One would also want a button to "freeze" a tab. Leave it open, but deny it to update.

It could also pinpoint which components of that page are the worst. Perhaps a video, a banner... and allow to stop it. Or filter it out for ever.

I use a adblocker not especially to block ads. It makes most websites faster, because - loading ads from overloaded ad-farms - flash - javascript monsters - video - .... slows down some websites so heavily that it is no fun to surf there. Try it, and feel the speedup!

On 2016-12-29 11:19, Florian Gleixner wrote:

On 27.12.2016 15:26, Carlos E. R. wrote:

I use a adblocker not especially to block ads. It makes most websites faster, because - loading ads from overloaded ad-farms - flash - javascript monsters - video - ....

I use it for those very reasons. And to kill popup adverts or floating banners that impede reading. Unfortunately, some sites refuse to display if they detect an adblocker. I do not ban all adverts, only the nosy ones: I understand sites need the money, but not at the cost of impairing web experience. Add blocker tools also slow down browsers, because the procedure breaks optimizations by the browser: it has to read in sequence and examine before allowing to load other components. There is somewhere a very good explanation of this by a Chrome developer, maybe I can find the link. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

On 12/29/2016 05:19 AM, Florian Gleixner wrote:

I use a adblocker not especially to block ads. It makes most websites faster, because - loading ads from overloaded ad-farms - flash - javascript monsters - video - ....

slows down some websites so heavily that it is no fun to surf there. Try it, and feel the speedup!

Some adblockers also edit the html stream so as to remove the space taken up by the ads. This has the psychological effect of making the page appear to load faster. certainly eliminating the 'headline' banner adverts from the data stream speeds up the initial rendering. But realistically, some sites just have an awful lot of redundant/unused CSS to download, and very complicated structure for what is essentially, a not very complex page. Some of this is due to automated tools. You can sometimes recognise this by lots of whitespace in the html and/or lots of inline javascript. See, for example, https://www.cnet.com/news/ -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org