News for hackers. Stuff that matters.

A comment on Improving Firefox Responsiveness on macOS. Parent comment

Re:Improving Firefox Responsiveness on macOS by hvis on Monday October 10, 2022 @07:02PM (#33157424)
To quote the article:

  Did they work? Yes! Performance on lightly loaded systems was about the same as OSSpinLock but on loaded ones, they provided massively better responsiveness. They also did something extremely useful for laptop users: they cut down power consumption as a lot less cycles were wasted having the CPUs spinning on locks that couldn’t be acquired.
To no one's surprise, one has to use Apple's undocumented APIs to be able to match Safari's power use.
[ Parent | on HN ]
Re:Improving Firefox Responsiveness on macOS by saagarjha on Monday October 10, 2022 @08:23PM (#33157989)
This conclusion does not have sufficient supporting evidence in the blog post.
[ Parent | on HN ]
Re:Improving Firefox Responsiveness on macOS by jabedude on Monday October 10, 2022 @09:18PM (#33158338)
Odd that you’re being downvoted. If the article had shown that Safari or the system allocator used this locking strategy then that would be evidence, otherwise the person you responded to is just making things up
[ Parent | on HN ]
Re:Improving Firefox Responsiveness on macOS by azinman2 on Tuesday October 11, 2022 @02:30AM (#33160110)
Memory allocation is one of many differences between the browsers.
[ Parent | on HN ]
Re:Improving Firefox Responsiveness on macOS by jhatax on Tuesday October 11, 2022 @11:37AM (#33164660)
Or implement their own locks and support structures to eke out performance [1]. Hat tip to @pizlonator.

1. https://webkit.org/blog/6161/locking-in-webkit/

[ Parent | on HN ]