Mozilla Firefox 26 Is Shipping Today With Fun Features

[madbiologist]

Note that once the gstreamer 1.0 support is available in Firefox you'll need gstreamer-vaapi 0.5.3 or later, which is currently not available in any Ubuntu version.

[tga.d]

Yes, see https://bugzilla.mozilla.org/show_bug.cgi?id=861266

Also, note that TLS 1.1 was disabled for Firefox 26 because a last-minute compatibility issue was found with https://mymedicare.gov. See comment 67 in https://bugzilla.mozilla.org/show_bug.cgi?id=733647 for more details. If you don't use that site and you want to use TLS 1.1 you can go to about:config and change the value of security.tls.version.max from "1" to "2".

I'd recommend just going ahead and changing it to "3", which makes TLS 1.2 the max version. It's already planned for inclusion in FF27, and I've been using it for months now without issues outside of the mymedicare bug (https everywhere enabled, so if there was a major issue I probably would have noticed by now).

https://bugzilla.mozilla.org/show_bug.cgi?id=861266

[chris200x9]

Because generally your running jobs have occasional stalled time when they are waiting on something (like I/O) and not doing any actual work - and your +1 job can fill in nicely on all x cores whenever that happens. Suspending jobs shouldn't really take any extra time, so the idea is to make sure that the pipeline is always full and your CPU is always busy with something, rather than risk it running dry for short times. You limit it to +1 instead of more than that, to avoid excessive unnecessary swapping which doesn't gain you anything but can kill caches, etc.

The exact optimal number varies based on both the project you are compiling and the details of your hardware, but the +1 is a good general starting point.

Wrong! http://blogs.gentoo.org/ago/2013/01/...-optimization/

[smitty3268]

Wrong! http://blogs.gentoo.org/ago/2013/01/...-optimization/

I very specifically noted that the optimal number varies based on what you are compiling and what kind of hardware you are using, so this is basically just a confirmation of what i said. You need to test it yourself to see what's optimal. core + 1 is a good place to start, nothing more.

I'd imagine you could get very different results on a big c++ project versus a c project, for example, and with or without an SSD.

I’m just saying, ${core} + 1 is not the best optimization for me and the test confirms the part:“but this guideline isn’t always perfect”

[madbiologist]

... it (H.264) should be working on Ubuntu 12.04 LTS "Precise Pangolin" which has gstreamer 0.10 but not gstreamer 1.0. See https://launchpad.net/ubuntu/+source/gstreamer0.10 and https://launchpad.net/ubuntu/+source/gstreamer1.0 - As Ericg said in comment #3, gstreamer 1.0 support is coming to Firefox soon...

I've got an Ubuntu 12.04.1 LiveCD here so I'll report back once I've booted it, installed the gstreamer plugins and updated Firefox.

Yay - it works! When using Firefox 26 on Ubuntu 12.04.1 with the gstreamer 0.10 plugins installed, I get this. When using Firefox 26 on Ubuntu 13.04 with the gstreamer 1.0 plugins installed, the top centre box (H.264) was red with an exclamation mark. Also, when using Firefox 26 on Ubuntu 12.04.1 with the gstreamer 0.10 plugins installed, if I go to about:config and set media.mediasource.enabled to true, I get this.

I'm guessing that the "MSE & H.264" box in the latter pic might become green with a tick once the fix/es for https://bugzilla.mozilla.org/show_bug.cgi?id=778617 and/or https://bugzilla.mozilla.org/show_bug.cgi?id=881512 land. Off-topic note: the demo hosted at http://bluishcoder.co.nz/2013/08/20/...n-firefox.html does work if media.mediasource.enabled is set to true.

[cliff]

Great

This is great I was able to watch some nice videos on vimeo, without flash finally!!
Way cool Mozilla!

[Ericg]

Because generally your running jobs have occasional stalled time when they are waiting on something (like I/O) and not doing any actual work - and your +1 job can fill in nicely on all x cores whenever that happens. Suspending jobs shouldn't really take any extra time, so the idea is to make sure that the pipeline is always full and your CPU is always busy with something, rather than risk it running dry for short times. You limit it to +1 instead of more than that, to avoid excessive unnecessary swapping which doesn't gain you anything but can kill caches, etc.

The exact optimal number varies based on both the project you are compiling and the details of your hardware, but the +1 is a good general starting point.

Thanks for replying Smitty