Faster syncing?

hi, I'm trying the trial and the syncing is restricted to 30 seconds after the last input. That's way too slow and in practice it feels more like a couple minutes. On logseq it's 2 seconds after last input, and from last input to propagation it's about 10-15 seconds. On AnyType, it's almost instantaneous, from last input to propagation to new deviceit's about 2 seconds.

i'm considering the lifetime subscription, but I'd like to know if we can get faster syncing. For right now it's way too slow. I also noticed that if I type something on one page on one device, and then type somethingin the same document from another device, it completely overwrites the page, instead of actually merging.

    Related articles

    7 Reply

    Welcome to here!

    Here we can learn from each other how to use SiYuan, give feedback and suggestions, and build SiYuan together.

    Signup About
    Please input reply content ...
    • 88250

      Hello, if you want to sync at demand, try to press F9 to toggle sync. If multiple devices are online, the config item Settings - Cloud - Sync perception could enhance auto sync experience, thanks.

    • MiscReply
    • MonkCanatella

      So it's not up for consideration? If I just sync everytime I finish typing something it will have the same effect. I think you will find it's not resource heavy if you're only syncing the changes made and not the entirety of the database. It should be about as resource heavy as a chat app sending messages back and forth

      1 Reply
    • MonkCanatella 1

      I understand. However I strongly encourage you to consider allowing more rapid syncing, especially for only text updates. SiYuan is my favorite PKMS that I have encountered, but logseq and anytype and many others that aren't catered towards collaboration still have very rapid syncing.

      I understand if there's a lot of work to be done to change the syncing infrastructure, but if the paid offering is syncing and it has such severe limitations, it really makes it a poor value proposition. I highly encourage to be open to more robust syncing and improvements to syncing in general

    • 88250

      Yes, the current synchronization mechanism will not consider changes for the time being.

      This is not quite like chat messages. Data synchronization also needs to consider external changes (for example, on the desktop, users may use other applications to change asset files, such as editing pictures), so we choose the incremental file snapshot solution. Before synchronization, it is necessary to traverse the file system to generate snapshots. If it is too frequent, it will cause a certain waste of system resources. In addition, each synchronization needs to download the snapshot index from the cloud, and network traffic will also be used.

      In summary, we will not consider reducing the synchronization interval for the time being, unless the user manually triggers the synchronization, thank you.

    • Visit all replies