Re: Apparent timeouts

On Fri, 26 Jan 2024 at 17:39, Dale R. Worley <[email protected]> wrote:
>
> Tõivo Leedjärv <[email protected]> writes:
> > Viv's analysis of the issue is completely accurate. It is just a symptom of
> > the GUI thread not getting sufficient run time and thus appearing "frozen",
> > yet the actual syncing is continuing behind the scenes.
>
> I don't know how the Unison GUI is structured, but from these symptoms
> it seems possible that the GUI thread doesn't run independently of the
> file-copying thread, but instead the GUI interaction only gets to run
> after each file is finished.  That would account for why the issue shows
> up only when copying very large files.

This is partially true. There is no full multi-threading but there is
cooperative threading and most file operations do update the GUI
rather frequently (users should experience the GUI as completely
smooth).

Still, there are a few operations which don't yield to other threads
periodically. Fingerprinting a file and deleting a dir tree are such
operations, if I'm not mistaken. Fingerprinting a large file can take
a very long time (even minutes) and this is most likely what John is
seeing.

> If that is the case, how much
> work would it be to arrange for the GUI interaction to not be blocked by
> copying really large files?

I think the only remaining operation really visibly blocking the UI
(the same happens both in GUI and TUI) is the fingerprinting. It's
reasonable that this is improved in a future release (most likely in
combination with a change of fingerprinting algorithm, so may not
happen any time soon).

-- 
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].