Files
ai-toolkit/toolkit
Booyaka101 0c8793ff47 fix: make pin_memory opt-in via dataset config (default off)
@zappazack found a real regression: pin_memory page-locks RAM that
NVIDIA's Windows driver wants for shared-memory VRAM-overflow fallback
when VRAM saturates. Page-locked pages can't be relocated, so the driver
falls back to PCIe thrashing - step times went from 1.5s to 20+s when
VRAM saturated on RTX 5090 + Qwen LoRA + 1024x1024.

The original "strict-improvement" claim was wrong. Convert to opt-in:

- Add `pin_memory: bool` field on DatasetConfig (default False)
- Only pin when both CUDA is available AND user opts in via config

Users with stable VRAM headroom can opt in for the transfer speedup.
Users at the VRAM ceiling stay safe with the default.

Refs #758.
2026-05-02 11:02:41 +08:00
..
2024-07-20 08:21:57 -06:00
2023-07-05 16:44:58 -06:00
2024-07-10 15:20:04 -06:00
2025-04-17 09:00:10 -06:00
2023-08-13 10:25:56 -06:00
2025-12-18 10:08:59 -07:00
2026-01-13 04:55:30 -07:00
2025-10-26 05:47:25 -06:00
2025-06-12 08:00:51 -06:00
2024-02-13 16:00:04 -07:00
2023-07-28 08:16:29 -06:00