rclone mount vs rclone bisync after Dropbox: the real latency, RAM and conflict numbers
说明与用途
用户可以通过将 rclone bisync 用于每日编辑(离线、低延迟)和 rclone mount 用于大型归档(无限可见容量)来替代 Dropbox。
问题
Users need to replace Dropbox’s desktop client with rclone while balancing latency, offline access, and disk usage.
结果
Users can achieve a Dropbox‑like experience by combining rclone bisync for daily edits (offline, low latency) and rclone mount for large archives (unlimited apparent capacity).
工作流
- 1. Decide which data set is "working set" (daily edited files) and which is "archive" (read‑only).
- 2. For the working set, schedule
rclone bisync(e.g., every 5 min) with--resyncon first run and resolve conflicts manually. - 3. For the archive, run
rclone mount remote:files ~/Cloud --vfs-cache-mode full(optionally cap cache with--vfs-cache-max-size). - 4. If multiple devices need access, expose the server folder via
rclone serve webdavor sync each device with bisync. - 5. Monitor cache size and network usage; adjust
--dir-cache-time,--transfers, and--check-accessfor metered or flaky connections.
证据
Neither one alone reproduces the Dropbox desktop client, and the honest answer is that you run both.
An rclone mount with --vfs-cache-mode full gives you a folder that looks complete in your file manager, but every first read of an uncached file costs a network round trip, and nothing is available offline until you have opened it.
rclone bisync gives you genuine local copies with local disk latency and true offline access, at the cost of a scheduled run, a mandatory first --resync, and conflict files you have to resolve yourself.
Split your data: bisync the working set you edit daily, mount the archive you only read.
- 记录日期: 2026-10-12T00:41:17.546Z