#RocksDB Continuous Flush Loop – High Disk Usage & Stutter

1 messages · Page 1 of 1 (latest)

junior fable
#

Heavy constant disk writes (~10–30 MB/s) when at sea

Game: Windrose
Situation: Sailing / open sea
Disk: NVMe (Samsung 980 Pro)

Observed:

  • Constant write activity (~10–30 MB/s)
  • Disk usage ~70–80%
  • Pattern: periodic spikes (buffer/flush behavior)
  • High disk latency (~10–15 ms on NVMe)

Source:

  • Writes come from:
    AppData\Local\RS\Saved\SaveProfiles...\RocksDB...\Worlds...*.log

Notes:

  • Behavior seems tied to world simulation at sea
  • Looks like aggressive DB flushing / autosave loop

Impact:

  • Potential SSD wear
  • Possible performance issues on lower-end drives

Hypothesis:
There seems to be a consistent issue around world persistence (RocksDB) causing:

  • High disk usage client-side
  • Potential world corruption / restart loops server-side

Reposting from support for visibility

Capture_decran_2026-04-18_210556.png
steel cairn
#

Thanks for the report, we'll look into it! Can you provide your client and server logs(if playing online)?

arctic stumpBOT
#
BUG REPORTING GUIDE

Please share your game logs, game saves, crash dumps, and DxDiag. These are essential for diagnosing and fixing bugs.

HOW TO FIND LOGS

Game logs are located here:
C:\Users\%USERNAME%\AppData\Local\R5\Saved\Logs

Server logs are located here:
R5\Builds\WindowsServer\R5\Saved\Logs

To get there, open Steam, find Windrose in your library, right-click it, then go to Manage → Browse local files. From there, archive the files in the Logs folder and share them with us.

Please name your logs in a way that describes the problem, for example: Crashedwhile_fighting_Dodo.log

HOW TO FIND SAVES

Your saves are located here:
C:\Users\%USERNAME%\AppData\Local\R5\Saved\SaveProfiles
Please close the game before archiving your saves!

If you are playing on a dedicated server:
• Stop both the client and the dedicated server.
• Find and archive your server logs and world save.

Dedicated server logs are located here:
R5\Saved\Logs

Dedicated server saves are located here:
R5\Saved\SaveProfiles

To get there, open Steam, find Windrose Dedicated Server in your library, right-click it, then go to Manage → Browse local files (or go to the folder where your Windrose Dedicated Server is stored).

Please close the dedicated server before archiving your saves.

HOW TO FIND CRASH DUMPS

If crashes are involved, please share crash dumps:

Game client dumps (if play offline)
%LOCALAPPDATA%\Local\R5\Saved\Crashes
%LOCALAPPDATA%\Local\R5\.sentry-native

Server dumps (if you self-host from game client)
SteamLibrary\steamapps\common\Windrose\R5\Builds\WindowsServer\R5\.sentry-native
SteamLibrary\steamapps\common\Windrose\R5\Builds\WindowsServer\R5\Saved\Crashes

Dedicated server dumps
Windrose Dedicated Server\R5\.sentry-native
Windrose Dedicated Server\R5\Saved\Crashes

HOW TO FIND DXDIAG

Please also include your DxDiag report. This is your PC specifications in .txt format:

• Press Win + R.
• Type dxdiag and press Enter.
• When the tool opens, click Save All Information.
• Save the .txt file and attach it to your report.

Any additional screenshots and/or videos are HIGHLY appreciated!

junior fable
#

i played solo/offline.
Here is all the log/crash/config file in one zip.
For futher log, i'll go in a coop game, il will send you the same zip file if i've got the same "problem".

📎 Windrose-Log-El_Serda.zip
steel cairn
#

Thanks, we'll look into it.

junior fable
junior fable
#

same thing in coop on a freind server:
1MB/s max on land, but 10-20MB/s spike on sea.

junior fable
#

Bus interface Load go full when write on disk spike... 😉

image.png image.png
junior fable
#

Sea write 🤣

image.png
#

in the meantime 🤣

image.png
junior fable
#

Same problem with write on the disk 😉

🧪 Local System Environment (Fedora)

🖥️ System

  • OS: Fedora Linux 43 (KDE Plasma Desktop Edition)
  • Session: KDE (Wayland)
  • Kernel: 6.19.11-200.fc43.x86_64
  • CPU: Intel Core i7-10700K (8 cores / 16 threads)
  • RAM: 31 GiB
  • Swap: 8 GiB (zram)
  • Storage: Btrfs on /home (~444.5 GB)
  • Boot: EFI + /boot (ext4)

🎮 GPU / Drivers

  • GPU: NVIDIA GeForce RTX 3080 (GA102, 10 GB)
  • Kernel driver: nvidia
  • NVIDIA driver version: 580.142
  • VBIOS: 94.02.42.00.F7

🧱 Graphics / Vulkan Stack

  • vulkan-loader: 1.4.341.0 (x86_64 + i686)
  • vulkan-tools: 1.4.341.0
  • mesa: 25.3.6
  • mesa-vulkan-drivers: 25.3.6 (x86_64 + i686)
  • mesa-libGL / EGL / gbm: 25.3.6
  • nvidia-libs: 580.142 (x86_64 + i686)
  • nvidia-cuda-libs: 580.142

🔍 Vulkan Runtime State

  • Vulkan Instance: 1.4.341
  • GPU0: NVIDIA GeForce RTX 3080
  • API Version: 1.4.312
  • Driver: NVIDIA proprietary 580.142
  • GPU1: llvmpipe (Mesa CPU fallback — expected)
  • Warnings: dzn / display warnings present but non-blocking

🕹️ Steam Setup

  • Package: steam-1.0.0.85-5.fc43.i686
  • steam-devices: 1.0.0.101^git20260123.e0ab314-7.fc43
  • Previous Snap version: removed

✔️ Status

  • Steam RPM correctly detects:
    • Vulkan
    • RTX 3080
    • GPU topology

🧪 Valve Runtime / Proton

  • Runtime: SteamLinuxRuntime_sniper

  • Runtime version: 3.0.20260218.209091

  • pressure-vessel: 0.20260218.0

  • Proton: Proton Experimental

  • Prefix version: 10.1000-200

Fedora 43 (Wayland)
→ Steam (RPM)
→ SteamLinuxRuntime Sniper
→ Proton Experimental
→ NVIDIA Vulkan 580.142
→ RTX 3080

image.png
#

80FPS, on RTX 3080, with Epic setting with some on Medium, not bad ! (DLSS Quality).