Data Center Server Requirements and IOPS Table Guide

Data Center server requirements are mostly about planning the right rack space, the right company connection counts, and the right contract targets before you sign. The numbers are straightforward once you separate physical sizing from IOPS requirements: rack parts use U sizes, while contract requirements use the listed value multiplied by 1.000 IOPS.

I would treat the Req* column as the minimum you should hit before accepting a contract, and the Max column as the upper end shown in the reference data. Several later entries are still unknown, so the safest approach is to build around the confirmed companies first and leave room for expansion.

What the numbers mean

Req* is the minimum requirement. If you go below it, you take a monetary penalty. The source note is clear: the best practice is to set up the requirement before signing the contract.

The IOPS table is shown in thousands. That means every listed number needs the multiplier applied:

• 348 = 348.000 IOPS
• 120 = 120.000 IOPS

For planning, read the raw number as the actual contract target in thousands of IOPS, then multiply by 1,000 if you are comparing against total capacity.

Rack and component sizing cheat sheet

The physical layout is fixed and simple:

That makes rack space the first hard limit to check. Big servers consume more than twice the space of small servers, so a mixed build can fill a rack much faster than the server count alone suggests.

Server room layout and capacity

The reference layout lists the following room configurations:

• 16 x Column
• 4 x Row (5 Server each)
• 3 x Row (4 Server each)
• 64 x 5 Server = 320 Server
• 48 x 4 Server = 192 Server
• 512 server total

Use these as planning anchors rather than assuming every setup supports the same density. The important point is that the room can scale across different row and column layouts, with a listed ceiling of 512 servers total.

Ports and preinstalled connections by company

The port requirements vary by company, and some later entries have unknown values. The confirmed entries are:

A few practical takeaways from the port list:

• The first nine companies use the same basic port mix: 4x SFP+/SFP28 and 2x RJ45
• Companies 10 through 16 switch to 4QSFP+ & 16x SFP+/SFP28
• From company 17 onward, several port entries are still unknown
• The Rep. column appears to track the company reference number rather than a separate gameplay system

Contract IOPS requirements by server type

All values below are shown in thousands and need the 1.000 IOPS multiplier applied.

How to use the Data Center server requirements and IOPS table

The cleanest way to plan is to choose the company and server type first, then build to the required minimum before signing anything.

1. Find the company in the contract table.
2. Read the Req* value for the server type you want.
3. Multiply that number by 1,000 IOPS if you are checking the real capacity figure.
4. Leave headroom up to the listed Max value when the maximum is known.
5. Verify the port type and preinstalled count before committing to a layout.

I would prioritize the confirmed companies first, especially the ones with both Req* and Max filled in. Once a row shows ?, treat it as incomplete planning data and avoid guessing around it.

Quick planning notes

• Req* is the minimum contract target, not a comfortable target.
• Values are listed as IOPS in thousands, so the multiplier matters.
• The rack is 47U, which makes server size planning just as important as contract planning.
• Small servers are 3U; big servers are 7U.
• Patch panels and switches also take space: 2U and 1U.
• Some company entries and many later server requirements are still unknown, so only the confirmed rows should be used for exact planning.