Skip to content

docs: add JuiceFS WSLC performance workflow #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Ivanbeethoven merged 1 commit into from
Jul 28, 2026
Merged

docs: add JuiceFS WSLC performance workflow #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions docs/windows-wslc-testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -233,6 +233,27 @@ Each selected big profile should report `Errors = 0` and `GiB = 8`. With the S3
backend, `fio-bigwrite-rustfs-objects.json` and
`fio-bigread-rustfs-objects.json` must contain objects.

## JuiceFS fio through wslc-compose

The BrewFS repository also contains an equivalent JuiceFS test using Redis,
RustFS, a privileged FUSE container, and the same fio profile names:

```powershell
Set-Location "$Workspace\brewfs"
$env:WSLC_COMPOSE = $WslcCompose
$env:WSLC_COMPOSE_STATE_ROOT = "D:\wslc-compose-tests\juicefs-$RunId"

.\docker\compose-xfstests\run_juicefs_perf_wslc.ps1 `
-ArtifactsDir "D:\juicefs-artifacts\$RunId" `
-Tools fio-bigwrite,fio-bigread
```

JuiceFS is installed from its official CDN inside the test container. The
driver validates fio errors and transferred bytes and requires a nonempty
RustFS object report. See
`docker/compose-xfstests/juicefs-wslc-testing.md` in the BrewFS repository for
the smoke-size overrides, full profile set, artifact contract, and cleanup.

## Cleanup and troubleshooting

`down --volumes` removes project resources, but the SDK daemon remains alive
Expand Down Expand Up @@ -262,6 +283,9 @@ Common failures:
verify `Get-Service wslservice` reports `Running`.
- `SdkNotFound`: put the matching branch `wslcsdk.dll` directory first on the
current shell `PATH`.
- `/dev/fuse` exists but opening it returns `EPERM`: ensure the custom
`wslcsdk.dll` is beside `wslc-compose.exe`. Windows prefers that directory;
an older DLL masks out the privileged flag before the SDK call.
- `No such image` after a mirrored pull: use the current `wslc-compose` branch;
it resolves the image once so pulling and creating use the same reference.
- Image pull with no progress: check `curl.exe -I https://<registry-host>/v2/`.
Expand Down