SQL Server on a Windows VPS in Tokyo: A Performance Tuning Playbook

This hands-on checklist helps you get predictable I/O and faster queries on a Japan-hosted Windows VPS.

1) Start with storage & layout

• Separate data, log, and tempdb to different volumes when possible.
• Size for IOPS/throughput, not just capacity; avoid thin-provisioning surprises.

2) Tame tempdb

• Use multiple equally-sized data files.
  As a start: up to 8 logical CPUs → same number of files; above 8 → start with 8 and test.
• Pre-size data/log to avoid frequent autogrowth; use sensible growth increments.

3) Enable Instant File Initialization (IFI)

Grant the SQL Server service account the Perform volume maintenance tasks right to accelerate data file growth/creation (log files excluded).

4) Windows Server power plan

Use High performance on database hosts to reduce CPU ramp-up latency under load.

5) Measure & iterate

• Capture a baseline: wait stats, top queries, file I/O stalls.
• Test queue depth and stripe sets vs. your plan’s NVMe profile.

Quick scripts

-- Show file stats
SELECT DB_NAME(vfs.database_id) AS db, mf.name, vfs.num_of_reads, vfs.io_stall_read_ms,
       vfs.num_of_writes, vfs.io_stall_write_ms
FROM sys.dm_io_virtual_file_stats(NULL, NULL) vfs
JOIN sys.master_files mf ON vfs.database_id = mf.database_id AND vfs.file_id = mf.file_id
ORDER BY (vfs.io_stall_read_ms + vfs.io_stall_write_ms) DESC;

-- Check tempdb files
SELECT name, size*8/1024 AS MB, type_desc FROM tempdb.sys.database_files;

Ask for our “Tokyo SQL starter” image with pre-tuned tempdb, IFI enabled, and a High-Performance power plan.