# SyteLine 10 Utility and Web Server Sizing Calculator

> Source: https://netray.co/tools/syteline-utility-server-sizing-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Turn named users, concurrency and your own per-session assumptions into a server count and RAM plan for the SyteLine 10 application tier.

## Category

syteline

## Erp

Infor SyteLine

## Audience

- ERP administrator
- Infrastructure architect
- IT manager

## Tool

**Kind:** calculator

**Inputs:**

#### Named users

**Key:** named

**Type:** number

**Default:** 150

**Min:** 1

**Step:** 5

**Unit:** users

#### Peak concurrency

**Key:** conc_pct

**Type:** slider

**Default:** 60

**Min:** 10

**Max:** 100

**Step:** 5

**Unit:** %

**Help:** Share of named users with an active session at the busiest time.

#### API and integration sessions

**Key:** api

**Type:** number

**Default:** 10

**Min:** 0

**Step:** 1

**Unit:** sessions

**Help:** IDO REST clients, ION, Factory Track, scheduled integrations.

#### Sessions per app server

**Key:** per_server

**Type:** number

**Default:** 75

**Min:** 5

**Step:** 5

**Unit:** sessions

**Help:** Planning assumption. Replace with your partner's figure, Infor's sizing guide for your release, or a load test.

#### RAM per active session

**Key:** mb_session

**Type:** number

**Default:** 60

**Min:** 5

**Step:** 5

**Unit:** MB

**Help:** Planning assumption. Measure IDO Runtime and web process memory under load.

#### Base RAM per server

**Key:** base_gb

**Type:** number

**Default:** 8

**Min:** 2

**Step:** 1

**Unit:** GB

**Help:** Operating system, IIS and idle services.

#### TaskMan and service reserve

**Key:** reserve_gb

**Type:** number

**Default:** 4

**Min:** 0

**Step:** 1

**Unit:** GB

**Help:** TaskMan, event, replication and other services on the server.

#### CPU cores per server

**Key:** cores

**Type:** number

**Default:** 8

**Min:** 1

**Step:** 1

**Unit:** cores

**Outputs:**

#### Concurrent sessions

**Key:** concurrent

**Expr:** named * conc_pct / 100 + api

**Format:** integer

#### Application servers

**Key:** servers

**Expr:** ceil(concurrent / per_server)

**Format:** integer

**Primary:** true

**Description:** Before adding one for redundancy.

#### RAM per server

**Key:** ram_per_server_gb

**Expr:** base_gb + reserve_gb + (concurrent / servers) * mb_session / 1024

**Format:** decimal

**Primary:** true

**Description:** Gigabytes per application server.

#### RAM per server, rounded to 8 GB

**Key:** ram_rounded_gb

**Expr:** ceil(ram_per_server_gb / 8) * 8

**Format:** integer

#### Total application tier RAM

**Key:** total_ram_gb

**Expr:** ram_rounded_gb * servers

**Format:** integer

#### Sessions per core

**Key:** sessions_per_core

**Expr:** concurrent / servers / cores

**Format:** decimal

**Description:** Compare with what your load test showed as comfortable.

**Chart:**

#### Servers and RAM per server vs named users

**Type:** line

**X:** named

**From:** 25

**To:** 1000

**Steps:** 40

**Series:**

- servers
- ram_per_server_gb

**Disclaimer:** Every ratio here is a planning assumption, not an Infor sizing figure. Replace the defaults with values from the Infor hardware sizing guidance for your SyteLine release or from a load test before buying hardware.

## Content

**Intro:** This calculator sizes the application tier of an on-premises SyteLine 10 (CloudSuite Industrial 10) installation: the utility server that runs the IDO Runtime and TaskMan, plus web and client servers. It takes your own per-session assumptions and shows server count and RAM as users grow.

**Sections:**

#### The server roles you are sizing

**Body:** A SyteLine 10 on-prem installation separates the database server (SQL Server) from the application tier. The utility server hosts the IDO Runtime Service, which executes IDO requests for every client, along with TaskMan for background tasks and the event and replication services configured in Service Configuration Manager. Web servers host the browser client and the IDO request endpoints used by REST clients. Report rendering may sit on its own server. Each of these is a role, not necessarily a separate machine: small sites run several roles on one server, and larger sites split them. This tool sizes the session-carrying tier; size SQL Server separately.

**Bullets:**

- Database server: SQL Server, sized on data and query load
- Utility server: IDO Runtime, TaskMan, event and replication services
- Web servers: browser client and IDO request endpoints
- Optional reporting server

#### Formula

**Body:** Concurrent sessions = named users x peak concurrency % / 100 + integration sessions. Servers = ceiling(concurrent / sessions per server). RAM per server = base RAM + service reserve + (concurrent / servers) x MB per session / 1024. The tool also rounds RAM up to the next 8 GB and divides sessions by cores so you can sanity-check CPU. None of these ratios is published here as an Infor number: sessions per server and MB per session vary with release, form mix, customisations and how much logic runs in IDO extension classes. Take them from Infor's sizing guidance for your release, your partner, or better, a load test on your own data.

#### Worked example

**Body:** 150 named users at 60% concurrency gives 90 sessions; add 10 integration sessions for 100. At 75 sessions per server you need 2 application servers, each carrying 50 sessions. RAM per server = 8 + 4 + 50 x 60 / 1024 = about 14.9 GB, rounded to 16 GB, so 32 GB across the tier, with about 6 sessions per core on 8 cores. Add one more server if you need to patch or survive a failure without users noticing. Swept to 1,000 named users, the chart shows the server count stepping up every 75 sessions while RAM per server stays fairly flat, which is the signature of scale-out sizing.

#### Common practice and gotchas

**Body:** Above roughly 100 concurrent users it is common practice, not a rule, to put SQL Server, report rendering and the utility services on separate machines so a heavy report or MRP run does not slow interactive users. Integration sessions are easy to forget: a chatty IDO REST client that opens a session per call can consume more than a dozen users. Count TaskMan load separately using the queue calculator, because background jobs run on the utility server whatever the interactive load. Finally, virtual machines with overcommitted memory distort every figure; reserve the RAM you size.

**Cta:** If you want users to ask SyteLine 10 questions in plain English without adding load to the IDO tier, we can run a private AI layer on your own servers against a read-only reporting copy.

**Faq:**

#### What is SyteLine 10?

**Answer:** SyteLine 10 is the on-premises and cloud release line of Infor CloudSuite Industrial (CSI) 10, built on the Mongoose framework with IDOs, a browser client and an all-in-one application database on SQL Server. Infor uses the names SyteLine and CloudSuite Industrial for the same product family.

#### What are the hardware requirements for CSI 10?

**Answer:** Infor publishes system requirements and sizing guidance per release, and those are the authority for supported operating systems, SQL Server versions and minimum hardware. This calculator does not replace them; it turns your chosen ratios into a server plan so you can compare scenarios and growth quickly.

#### What does the SyteLine utility server do?

**Answer:** The utility server runs the services that do the work behind the client: the IDO Runtime Service that executes IDO requests, TaskMan for background reports and utilities, and event and replication services. It talks to SQL Server for every request, so network latency between it and the database matters.

#### How many users can one SyteLine server support?

**Answer:** There is no single number. It depends on release, forms used, customisation and extension class logic, report load and hardware. Run a load test with your own scripts or use the figure from your partner's sizing, then enter it as sessions per server. Treat any number without a test behind it as a guess.

## Search terms

syteline 10 erp, syteline csi 10, infor csi 10, syteline 10, syteline server sizing, syteline utility server, csi 10 hardware requirements, syteline ido runtime

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json