# How to speed up repository sync-to

**URL:** <https://kopia.discourse.group/t/how-to-speed-up-repository-sync-to/1451>\
**Category:** General Topics\
**Created:** [October 2, 2022, 2:32pm UTC](https://kopia.discourse.group/t/how-to-speed-up-repository-sync-to/1451 "2022-10-02T14:32:46Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![stpr](https://avatars.discourse-cdn.com/v4/letter/s/b3f665/32.png) [@stpr](https://kopia.discourse.group/u/stpr)\
**Post date:** [October 3, 2022, 3:41am UTC](https://kopia.discourse.group/t/how-to-speed-up-repository-sync-to/1451/2 "2022-10-03T03:41:18Z")

</div>

Just my 2c here, not an expert in this, but the issue _might_ be with rclone and WebDav. I have used WebDav in the past, and I had lots of headaches with it around speed. Having said that, see [Kopia sync-to rclone using webdav](https://kopia.discourse.group/t/kopia-sync-to-rclone-using-webdav/294) where I think the issue is very similar to yours. There is some bottlenecks around Kopia/rclone/WebDav, and the TLDR is that more work needs to be done. As a workaround, you could in theory do something like the poster in the other thread: which is have a timer/cron to run a shell script to `rsync` the local repo to remote and perhaps get a speed boost. The rsynced repo should behave identical to the original or the sync-to repo, so you shouldn’t get into any trouble.

---

_[View the full topic](https://kopia.discourse.group/t/how-to-speed-up-repository-sync-to/1451)._