False sharing

In computer science, false sharing is a performance-degrading usage pattern that can arise in systems with distributed, coherent caches at the size of the smallest resource block managed by the caching mechanism. When a system participant attempts to periodically access data that is not being altered by another party, but that data shares a cache block with data that is being altered, the caching protocol may force the first participant to reload the whole cache block despite a lack of logical necessity.^[1] The caching system is unaware of activity within this block and forces the first participant to bear the caching system overhead required by true shared access of a resource.

By far the most common usage of this term is in modern multiprocessor CPU caches, where memory is cached in lines of some small power of two word size (e.g., 64 aligned, contiguous bytes). If two processors operate on independent data in the same memory address region storable in a single line, the cache coherency mechanisms in the system may force the whole line across the bus or interconnect with every data write, forcing memory stalls in addition to wasting system bandwidth. In some cases, the elimination of false sharing can result in order-of-magnitude performance improvements.^[2] False sharing is an inherent artifact of automatically synchronized cache protocols and can also exist in environments such as distributed file systems or databases, but current prevalence is limited to RAM caches.

#include <atomic>
#include <chrono>
#include <iostream>
#include <latch>
#include <thread>
#include <vector>

using namespace std;
using namespace chrono;

int main()
{
	vector<jthread> threads;
	const int hc = jthread::hardware_concurrency();
	constexpr int testLimit = 256; // for simplicity up most that many elements
	for (int nThreads = 1; nThreads <= hc && nThreads <= testLimit; ++nThreads)
	{
		// precise measurement by starting all threads simultaneously
		latch sync(nThreads);
		// some individual piece data for each individual thread
		struct { atomic_char mightBeShared; } globaldata[testLimit];
		// mitigation: occupying a full cache line
		//	e.g. under the assumption that a cache line consists of 64 bytes
		//	struct alignas(64) { atomic_char mightBeShared; } globaldata[testLimit];
		// sum of all threads execution times
		atomic_int64_t nsSum(0);
		for (int t = 0; t != nThreads; ++t)
			threads.emplace_back([&](int i)
				{
					sync.arrive_and_wait(); // sync beginning of thread execution on kernel-level
					auto start = high_resolution_clock::now();
					for (size_t r = 10'000'000; r--;)
						globaldata[i].mightBeShared.fetch_add(1);
					nsSum += duration_cast<nanoseconds>(high_resolution_clock::now() - start).count();
				}, t);
		threads.clear(); // join all threads
		cout << nThreads << ": " << (double)(nsSum / (1.0e7 * nThreads)) << endl;
	}
}

This code shows the effect of false sharing. It creates an increasing number of threads from one thread to the number of physical threads in the system. Each thread sequentially increments one byte specific for that thread (i.e. not shared between them). The higher the level of contention between threads, the longer each increment takes, despite the fact that each thread is only incrementing its own piece of the global data. Those are the results on a Intel Core i7 12th generation system with 6 performance and 8 efficiency cores yielding 20 threads:

As one can see, concurrent access by those threads requires about 50 times more computing time than with mitigation where it approximately doubles.

There are ways of mitigating the effects of false sharing. For instance, false sharing in CPU caches can be prevented by reordering variables or adding padding (unused bytes) between variables. However, some of these program changes may increase the size of the objects, leading to higher memory use.^[2] Compile-time data transformations can also mitigate false-sharing.^[3] However, some of these transformations may not always be allowed. For instance, the C++ programming language standard draft of C++23 mandates that data members must be laid out so that later members have higher addresses.^[4]

There are tools for detecting false sharing.^[5][6] There are also systems that both detect and repair false sharing in executing programs. However, these systems incur some execution overhead.^[7][8]

• Easy Understanding on False Sharing
• C++ today blog, False Sharing hits again!
• Dr Dobbs article: Eliminate False Sharing
• Be careful when trying to eliminate false sharing in Java