2 ms·
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
by hvis 4y ago
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.
- saagarjha 4y agoThis conclusion does not have sufficient supporting evidence in the blog post.
- jabedude 4y agoOdd 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
- azinman2 4y agoMemory allocation is one of many differences between the browsers.
- jhatax 4y agoOr 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/ https://webkit.org/blog/6161/locking-in-webkit/