Save 10%Pay yearly on any plan. 6% half-yearly, 3% quarterly. Help centreWhatsAppTelegram TeamsOpen a ticket

Multi-Threading Servers: What Threads Are and How Many You Need

A multi-threading server is a dedicated machine for software that runs many tasks at once. What a thread is, which work gains, and how to size it.

3 min readBy Swati

Reviewed by the AmazingRDP technical team

Multi-threading servers explained

Work that runs many tasks at once needs many threads. See the multi-threading servers. See Multi-Threading Servers from $109.99

The earlier version of this page said that "multi-threading RDP" makes a Remote Desktop connection smoother. It does not; the name describes something else. A multi-threading server is a dedicated machine with a processor that offers many threads, for software that does many things at the same time. This page explains what that means and how to tell how many threads your work can use.

Cores and threads

  • A core is one processing unit inside the processor.
  • A thread, in hardware terms, is one stream of work a core can carry. Most current cores carry two, so a processor with 6 cores shows 12 threads to the operating system, and one with 16 cores shows 32.
  • The second thread of a core is not a second core. It lets the core use idle moments and adds roughly a fifth to a third more throughput, depending on the work.

Task Manager on Windows shows both figures under Performance, CPU: "Cores" and "Logical processors".

Which work gains from many threads

Gains a lotGains little
Many independent tasks side by side: dozens of browser profiles, bots, scrapers, test runsOne program that works in a single thread, as many older tools and scripts do
Video encoding and rendering with software that uses all coresWork that waits for a slow disk or a slow website, not for the processor
Compiling large projectsWork limited by memory
Several virtual machines or containersLight office and browsing use

The test is simple. Run your work and watch the processor graph per core. If all cores are busy, more threads will help. If one core is at its limit and the rest idle, you need faster cores, not more: see the fastest server processors.

How many?

  1. Count what runs at once. Twenty automation tasks that each keep a core half busy need about ten cores' worth.
  2. Add memory to the sum. Threads are useless if memory runs out first. A browser profile or a small virtual machine can take 1 to 2 GB each; twenty of them need that many gigabytes before the processor matters.
  3. Leave a margin of a quarter for the system and for peaks.
  4. Measure, then adjust. Estimates of parallel work are usually wrong in one direction or the other: see monitoring with htop on Linux or Task Manager on Windows.

Our multi-threading servers, in short

  • Whole dedicated machines in Europe; nothing is shared.
  • Five builds, from 6 cores and 12 threads to 16 cores and 32 threads, with 64 or 128 GB of memory and two NVMe drives each.
  • Full administrator access, Windows (evaluation edition) or Linux, and a control panel of your own.
  • Setup in 3 to 4 hours when the build is in stock; otherwise up to 24 hours, rarely 48 to 72.
  • 7-day refund. Moving to a bigger build is a new order, since it is a different machine.

The builds and their prices are on the multi-threading servers page.

Why a whole machine and not a VPS?

On a virtual server the cores are shares of a processor that other customers use too. For a few hours of load that is fine. Work that keeps every thread busy all day is exactly what shared hosts are not built for, and it is what a dedicated machine is for: the threads are yours whether you use them or not. See how hypervisors work for the background.

Get the most out of the threads

  • Check that your software is allowed to use them. Many programs have a setting for the number of workers or threads, with a low default.
  • Expect less than double: doubling the threads rarely doubles the output. Parts of every job cannot be split.
  • Keep the two drives in mind. Mirrored, they protect against one failing; separate, they give more space. Decide before you fill them.
  • Stay inside the usage policy. Plenty of threads do not change what is allowed: no mining, no scanning or attacking other systems, no bulk messaging. The policy says where the lines are.

One big processor or two?

All these builds are single-processor machines, which is the simpler and usually faster arrangement for this kind of work: see single or dual processors, and the notes on the Ryzen 9 5950X and the EPYC 7502P for what individual processors are like.

Questions

What is a multi-threading server?

A dedicated server chosen for its high number of processor threads, for software that runs many tasks in parallel.

What is the difference between cores and threads?

A core is a physical processing unit. Most cores carry two threads, so the system sees twice as many logical processors as cores.

Does multi-threading make Remote Desktop faster?

No. It helps programs that run many tasks at once on the server. The Remote Desktop connection itself is not affected.

How many threads do I need?

Count the tasks that run at the same time and how busy each keeps a core, add a quarter as margin, and check that memory is enough for all of them.