Build fluency in the vocabulary of keeping a thread's memory local to the CPU socket that's actually using it.
0 / 5 completed
1 / 5
At standup, a dev mentions that on a multi-socket server, each CPU can access memory physically attached to its own socket faster than memory attached to a different socket, and writing code that accounts for this difference is called what?
NUMA awareness, for non-uniform memory access, is exactly this: on a multi-socket server, each CPU can reach memory physically attached to its own socket faster than memory attached to a different socket, and NUMA-aware code deliberately allocates memory and schedules work to keep a thread's data on the socket local to the CPU running it. A hash collision is an unrelated hash-table concept about two keys sharing a bucket. This local-versus-remote memory-latency difference is exactly why NUMA awareness matters for performance-sensitive workloads on multi-socket hardware.
2 / 5
During a design review, the team pins each worker thread to a specific CPU socket and allocates that thread's memory from the same socket, specifically to avoid the extra latency of reaching memory attached to a different socket. Which capability does this provide?
Pinning threads to a socket and allocating their memory locally provides lower and more predictable memory-access latency, since keeping a thread's data on the same socket as the CPU running it avoids the extra latency of crossing an interconnect to reach memory attached to a different, remote socket. Memory-access latency being the same regardless of which socket data lives on would contradict the entire premise of non-uniform memory access that gives NUMA its name. This local-versus-remote latency gap is exactly why NUMA-aware pinning and allocation improve performance on multi-socket hardware.
3 / 5
In a code review, a dev notices a performance-sensitive service on multi-socket hardware lets the operating system freely migrate threads between sockets and allocates memory with no regard for which socket will actually run the thread using it. What does this represent?
This is a missed opportunity for NUMA awareness, since letting threads freely migrate between sockets while allocating memory with no locality consideration risks a thread frequently ending up on one socket while its data lives on another, paying the extra cross-socket latency on every access, when pinning threads and allocating memory locally would avoid that cost. A cache eviction policy is an unrelated concept about discarded cache entries. This ignore-memory-locality pattern is exactly the kind of avoidable latency a reviewer flags on multi-socket hardware.
4 / 5
An incident report shows a performance-sensitive service's memory-access latency was inconsistent and sometimes much higher than expected on multi-socket hardware, because the operating system freely migrated threads between sockets and memory was allocated with no locality consideration. What practice would prevent this?
Adopting NUMA awareness, pinning each thread to a specific socket and allocating its memory locally, keeps a thread's data on the same socket as the CPU running it, which directly addresses the inconsistent, sometimes-high latency described in this incident. Continuing to let threads migrate freely with no locality consideration regardless of the resulting latency variance is exactly what caused the inconsistency. This pinning-and-local-allocation approach is the standard fix for latency variance traced back to cross-socket memory access on multi-socket hardware.
5 / 5
During a PR review, a teammate asks why the team pins threads to specific sockets instead of just letting the operating system's scheduler freely balance load across every socket however it sees fit. What is the reasoning?
Free load balancing can move a thread to whichever socket has spare capacity without regard for where that thread's data actually lives, incurring the extra latency of remote-memory access whenever the thread ends up away from its data, while pinning threads to a socket trades away some of that scheduling flexibility in exchange for consistently local, faster memory access. The tradeoff is that pinning can leave a socket underutilized if its pinned threads are idle while another socket is overloaded. This is exactly why NUMA-aware pinning is favored for latency-sensitive workloads, while free load balancing remains simpler for workloads where memory locality matters less.
What does the "NUMA Awareness Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to numa awareness vocabulary through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.