Direct answer
NVMe describes a storage interface/protocol. For server behavior, measured latency, throughput and contention matter more than the label on the SSD.
How to check it
- Use
lsblk -o NAME,MODEL,ROTA,TRAN,SIZE,MOUNTPOINTSto identify the drive that actually stores world region files. - If sysstat is installed, sample
iostat -xz 1 5during chunk generation, backups or world saves; inspect utilization and await with care. - Capture an MSPT profile and note whether slowdowns correlate with synchronous file work versus worldgen CPU usage.
What to change
lsblk -o NAME,MODEL,ROTA,TRAN,SIZE,MOUNTPOINTS
# Optional (sysstat package):
iostat -xz 1 5- Move a copy of the same world to the proposed drive and test the same save or loading workload.
- Avoid using headline sequential read/write speeds as a substitute for realistic small I/O latency.
- Before migration, stop writes and take a verified full backup; ensure mount paths and file permissions are preserved.
Software and version notes
Compatibility and safety
In virtual machines the disk exposed as NVMe may still be backed by shared or network storage. Some VPS systems hide transport details and limit IOPS independently of the device.
Verify the result
Compare world save durations, observed disk latency and tick spikes; a faster drive should show a reproducible benefit in the affected workload.