Firefox

Warning

This post is more than a year old. Information may be outdated.

This improvement was achieved via a slight change in how locking is implemented within Firefox's memory allocator.
Putting a thread to sleep has significant performance implications and, thus, is not always the best option.
it might be advantageous to let a thread spin briefly if the lock it's trying to acquire is only held briefly.
It can result in higher performance and lower power consumption, as spinning costs less than sleeping.
As you might have guessed by now, OSSpinLock offered excellent performance on a lightly loaded system but behaved poorly as the load ramped up.
This problem with OSSpinLock was known within hence its deprecation

Backlinks14

Comments0

No comments yet. Be the first to share your thoughts.

Comments