Prime95 Worker Setup: Workers and Threads Per Worker
Quick facts: In Prime95 30.19 build 20, stress and GIMPS work is organised into workers. Each worker is an independent job with its own window on Windows, its own settings, and its own result lines. In the Test menu and the Worker Windows dialog you control how many workers run and how many threads each worker uses. The right arrangement depends on your goal, testing the whole processor at once or isolating part of it, and on your processor’s physical cores and simultaneous multithreading, not on a copied number from someone else’s machine.
What a worker actually is
A worker is a slot that runs one assignment or one Torture Test instance. When a worker stops with an error, Prime95 can tell you which worker it was, and when workers are mapped sensibly to cores, that information helps you localise a problem. Workers share the machine’s total threads, memory bandwidth, and cooling. Adding workers does not create performance; it divides the processor’s capacity into separately managed pieces. For GIMPS participation, multiple workers can run different assignments in parallel. For stress testing, the common purpose of the worker layout is coverage and diagnosis: cover every logical processor for a full-system test, or run fewer workers to isolate whether a fault follows a particular core group or disappears when part of the processor is idle.
Threads per worker, in plain terms
The threads setting inside a worker tells that worker how many hardware threads to use for its computation. If you run one worker, giving it all of the machine’s logical threads lets a single test span the whole processor. If you run several workers, their thread counts should add up to no more than the logical thread total if your goal is an even full load; oversubscribing, asking for more threads in total than the processor has, makes the operating system juggle work and muddies both heat behaviour and error localisation. Physical cores matter more than logical threads for this program’s heavy arithmetic: two threads on one physical core share that core’s execution resources, so doubling threads does not double throughput. That is why experienced testers think in physical cores first and treat extra logical threads as coverage for completeness rather than as extra computing muscle.
| Goal | Worker approach | Why |
|---|---|---|
| Full-system stability check | One worker using all logical threads, or one worker per core group with threads summing to the total | Maximum combined load with a clear overall result |
| Isolating a suspect core area | Fewer workers, assigned and noted carefully | A stopping worker narrows where to look next |
| GIMPS throughput | Workers matched to physical cores, tested by output over time | Physical cores do the heavy arithmetic; measure rather than assume |
| Memory-focused test | Workers arranged to leave the memory amount you set in the Torture Test available | Large FFT and Blend need memory headroom to press RAM |
How to set workers on Windows
Open the Worker Windows dialog from the Test menu, the same dialog the current version may show when you enable PrimeNet in Test settings, and review each worker’s type of work and thread count before starting. For a first Torture Test, the program’s default arrangement is a sensible starting point; change it only with a reason you can write down. Before a long run, confirm three things: every worker you expect is actually running, the thread counts sum to the total you intended, and the Torture Test preset and memory setting are the ones you chose. A surprising number of confusing results are simply a worker that never started or a thread count left over from an earlier experiment in prime.txt. Because settings persist in prime.txt, a portable folder carries its worker layout to the next machine, where the core count may be different; recheck the layout on every new processor instead of trusting the travelled defaults.
Reading worker behaviour during a test
During the run, workers should progress steadily. If one worker stops with a rounding or hardware failure message while others continue, stop the whole test and record which worker stopped, its number, the preset, and elapsed time. That pattern is diagnostic gold compared with a whole-system freeze, because it ties the failure to the load that worker was running. If all workers stop or the machine restarts, the problem is more likely systemic: power, cooling, memory, or a setting that affects the whole processor. Do not immediately rerun hoping for a pass. Change one variable, such as restoring stock frequency or relaxing a memory profile, and repeat the same worker layout and preset so the comparison is clean.
A worked decision, without borrowed numbers
Suppose your goal is to find out whether one part of a processor is weaker than the rest after a full-system run stopped a single worker. Start by repeating the full layout once at completely stock settings; if the same worker area fails at stock, the issue is not your tuning. If stock passes, split the next run into fewer workers covering separate core groups, keeping total threads within the logical total, and run the same preset for the same duration on each arrangement. The arrangement that reproduces the failure has localised the search; the arrangements that pass have cleared their part of the processor under that test. Write each arrangement and outcome in your note as you go. This slow narrowing is slower than guessing, but it replaces guesses with evidence, and it is exactly what the worker system was designed to make possible.
Principles, not borrowed numbers
This guide gives no per-model worker table, because the program itself does not publish one and the correct layout follows from your processor’s core and thread counts and your testing goal. Count physical cores, count logical threads, decide whether the run is for coverage, isolation, or throughput, and write the layout in your test note. That short discipline makes results.txt far more useful when you later interpret it or ask for help.
Next steps
Set up the test itself with How to Use Prime95, then learn to read the outcome in Interpreting Prime95 Results. All guides are listed in the tutorials hub.