---
task: Tuning checks (read-only)
version: R1.03
source: IM 36K10J10-01EN §5.5.1; practiced on the test system 2026-09-30
status: verified (read-only checks)
---

# Tuning checks (read-only)

Checks whether CI Server needs tuning. Nothing here changes the system. Changing the limits
means editing setup files and restarting CI Server: ask the user first.

## Limits in setup files (`%TLS_ROOT_PATH%\tls\sup\`)

Read the active (non-`!`) lines:

| File | Keyword | Meaning | Test system |
|---|---|---|---|
| `dur.sup` | `dur_max_proc` | Max processes (default 250) | 250 |
| `dur.sup` | `pool_kbytes` | DUR message pool | 250000 |
| `itm.sup` | `pool_kbytes` | Item common memory pool | 650000 |
| `database_start.cmd` (`tls\com`) | `-u` / `-f` | Max database users (default 2K) / files (default 1,200) | not checked |

## Live values: automatic health snapshots

CI Server's system monitor (`smdmon`) writes debugger snapshots about every 10 minutes to
`%TLS_LOG_PATH%\smd_<node>_<debugger>_*.log` (e.g. `smd_UNLICENCED_LOW_itmdbg_all.log`).
Read the newest entries:

| File | What to check | Target (IM 36K10J10 §5.5.1) |
|---|---|---|
| `*_itmdbg_all.log` | `common size` / `free size` | Free above 10 %, usage below 75 % |
| `*_smdsnp_process.log` | Per process: `queue_size`, `queue_used`, `queue_high` | No requests waiting (`queue_used` 0); enlarge a queue that stays in use |
| `*_ismdbg_all.log` | `Total number of lock collisions`, users, files | Collisions not rising above 250/s; entries below 80 % of max users |
| `*_smdsnp_process.log` | Number of processes | Well below `dur_max_proc` |

Test system (2026-09-30): common memory 665.6 MB, free 665.3 MB; queues empty; 3 lock
collisions in total.

## Not yet practiced

Debug launchers (`jwuipoi_debug`, `jhmiset_debug`, …), interactive debuggers (`itmdbg`,
`opcdbg`, `eqpdbg`, …), and per-process debug settings; see
`knowledge/manuals/IM36K10J10-01EN.md` §5.5.2.