By mswatcher
via smelser.net
Submitted: Feb 08 2012 / 10:51
Sharing across thread boundaries leads to increased preemptions, costly thread contention, and may introduce other less obvious expenses in L2 cache, and more
When working with shared state that is seldom or never updated, give each thread its own copy even at the expense of memory
Create thread affinity if the workload represents saga’s for object state, but keep in mind this may limit scalability within a single instance of a process
Where possible, isolating threads is ideal
Add your comment
