Apex 9
Cores by the dozen, memory in the hundreds of gigabytes, storage in the tens of terabytes. For the job that stopped fitting on anything smaller.
Kansas City, Missouri
- Processor
- 32 Cores
- Dual Xeon E5-2683v4 256GB 2x4TB SSDs Preconfig · 64 threads · 3 GHz
- Network
- 1 Gbit unmetered
- 5 usable IPv4 · /64 IPv6
What it will handle
The specification above is what is in the machine. This is what that is worth, with the sums shown.
- PassMark CPU Mark
-
—
Not on file
-
Not on file
- No processor on this listing to look up.
- Requests a second
-
4,000
/s
-
Estimate
- At 8 ms of processor time per request across 32 cores, and nothing else on the silicon. Your own figure is the one that counts.
- Monthly transfer
-
324 TB
-
Worked out here
- A 1 Gbit port sending flat out for thirty days. A ceiling, not a quota — nobody is asked to reach it.
- Application workers
-
510
-
Estimate
- At 512 MB each, from 256 GB with a gigabyte held back for the system.
A sensible choice for
-
Sole tenancy — no neighbours on the silicon
-
CI runners and parallel builds
-
A database primary with room to cache
-
Game servers and real-time workloads