ThreadTweak — a technical mod for optimizing and tuning CPU thread priorities in Minecraft

ThreadTweak — a technical mod for optimizing and tuning CPU thread priorities in Minecraft

ThreadTweak is a small technical mod for Minecraft that exposes the settings for how the game distributes work across CPU cores: the number of worker threads in key pools and the priority of each. In vanilla, these values are hardcoded and the same for everyone — which isn't always optimal for a specific system or alongside active background software. All parameters are saved in the threadtweak.json file and applied after restarting the game.

What exactly the mod changes

The tool acts on two levels: the size of worker pools and thread priority.

Size of worker pools — this is the number of separate threads the game divides parallel tasks into upon launch and at certain moments during the game session: texture atlas stitching, old world migration, some chunk operations. In vanilla, this size is automatically tied to the number of CPU cores with an upper limit. In practice, some tasks scale poorly — multiple threads don't work faster than one, and the overhead for coordination between them only grows.

Thread priority — a scale from 1 to 10 that Java passes to the operating system as a recommendation on who to give CPU time first. The standard priority of all Minecraft threads is 5. Lowering the priority of background pools usually doesn't noticeably slow down the game, but frees up resources for other processes: browser, voice chat, video recording software. Raising it above 5 rarely gives a boost — the OS will still divide CPU time among active applications, and synchronization between the game's own threads may become less stable.

When the setting provides real benefit

There aren't many scenarios where manual control of pools and priorities noticeably changes the experience, but they are specific:

• Playing alongside streaming or recording. On systems with 4–6 cores, OBS and Minecraft compete for the CPU. Lowering the priority of the main and io Worker to 2–3 reduces micro-stutters in the video without visible FPS loss in the game.

• Weak or old processors. With 2–4 physical cores, vanilla scatters worker threads across all available ones, causing the main game thread to periodically lose time. Limiting threadCount.main to 1–2 removes some of this noise.

• Multi-core CPUs with background load. On systems with 12+ threads, where compilation, torrents, or backups are running in parallel, lowering priorities makes Minecraft a "quiet neighbor" that doesn't eat up all the OS scheduler's performance.

Without such conditions, tweaking gives an effect within the margin of FPS measurement error.

Mod configuration

The configuration can be tweaked directly in the config/threadtweak.json file. The format is standard JSON, opens with any text editor.

If the file is missing, it is created automatically upon the first game launch after installing the mod.

Config file parameters

The config contains two groups: threadCount (pool size) and threadPriority (thread priority). All values are integers.

Conclusion

ThreadTweak fills a narrow niche — manual control over pools and thread priorities for cases when the standard Java scheduler gets in the way. In a simple single-player game without background applications, the FPS gain will be within the margin of error. The mod makes real sense on weak processors, during parallel streaming or recording, or when the system is constantly busy with other resource-intensive processes. By itself, it doesn't speed up the game — it only redistributes resources among threads, so there's no reason to expect a magical boost effect from it.