On 02/11/15(Mon) 13:21, David Coppa wrote: > On Fri, Oct 23, 2015 at 2:01 PM, Martin Pieuchot <m...@openbsd.org> wrote: > > On 22/10/15(Thu) 21:40, Amit Kulkarni wrote: > >> On Thu, Oct 22, 2015 at 12:26 PM, David Coppa <dco...@gmail.com> wrote: > >> > >> > On Thu, Oct 22, 2015 at 3:45 PM, Ed Ahlsen-Girard <eagir...@cox.net> > >> > wrote: > >> > > I have noticed a performance hit since the switch was flipped. Firefox > >> > > stays at the top of top most of the time, and its CPU percentages have > >> > > spiked to 175% if multiple tabs were being opened. dmesg below the sig. > >> > > >> > Can you try if the attached patch is an improvement? > >> > > >> > >> Hi, > >> > >> This CPU spike is present with October 11 packages (Firefox 41.0.1) on > >> amd64, so it will be difficult to isolate the performance impact of the W > >> ^X vs the existing situation. > > > > FWIW I found that firefox is (ab)using pthread_mutex_trylock(3) a lot > > resulting in a storm of sched_yield(2) triggering a lot (dozen to > > hundreds of thousands) of IPIs on my x220. > > > > I tried to look at the source code but couldn't figure out where the > > call of pthread_mutex_trylock(3) are coming from. Firefox is just a > > monster. > > > > I'm sorry but I agree that if nobody is taking care of this regression > > it will be really hard to measure the impact of the W^X change. > > > > Martin, > > Has this problem manifested itself with firefox-41 or was it already > present with 40.x ?
I don't remember, I can try to figure out but I'd be happy if somebody else would do it 8)
