On Mon, Jan 25, 2016 at 10:06:22AM +0100, David Coppa wrote: > On Sun, Jan 24, 2016 at 7:47 PM, Adam Wolk <adam.w...@tintagel.pl> wrote: > > On Fri, 22 Jan 2016 22:46:39 +0100 (CET) > > Mark Kettenis <mark.kette...@xs4all.nl> wrote: > > > >> Firefox makes a lot of concurrent malloc(3) calls. The locking to > >> make malloc(3) thread-safe is a bit...suboptimal. This diff makes > >> things better by using a mutex instead of spinlock. If you're running > >> Firefox you want to try it; it makes video watchable on some machines. > >> If you're not running Firefox you want to try it; to make sure it > >> doesn't break things. > >> > >> Enjoy, > >> > >> Mark > >> ' > > > > Applied to a Jan 15h snapshot sources. Youtube is not fully 'watchable' > > on firefox but feels significantly better. I can also now watch full > > screen youtube videos on chromium 1920x1080 with no stutter (lenovo > > g50-70). > > > > Generally gnome 3 feels a bit snappier especially on first load, > > bringing up the menu searching for 'terminal' leads to a faster > > rendering of the results. This might be just 'imagined' by me. > > > > On a more measurable front. I ran the octane benchmark against firefox > > post and before the patch. It resulted in a slight improvement from > > 12486 to 12826 score [1]. > > Besides performance related issues, the problem we saw in the past was > firefox using a huge amount of CPU resources with no apparent > reasons...
I've seen the same behavior on Linux. Probably not 100% related to the OS. -- Juan Francisco Cantero Hurtado http://juanfra.info
