> Le 28 déc. 2017 à 15:04, Richard Hipp <d...@sqlite.org> a écrit : > > On 12/28/17, Richard Hipp <d...@sqlite.org> wrote: >> >> Running multiple copies of the new fossil-stress.tcl script >> (https://www.fossil-scm.org/fossil/file/tools/fossil-stress.tcl) from >> a linux box against a windows laptop confirms that the "fossil server" >> command on Windows sometimes latches up. > > Preliminary findings are that this latch-up is the result of an > adverse interaction with built-in anti-virus software on Win10. You > *might* have more success by disabling anti-virus on your server - if > you dare. We'll try to figure out a way to fix the problem in fossil, > in the meantime.
Confirmed that server on macOS, client on Windows (server 2016 and server 2012 R2) is OK. Server and client on same Windows box, through localhost is comparable (just slightly slower) to server macOS and client Windows. I'll dig in the source code over the week-end. Generally, there are subtle TCP window issues to take into account when configuring sockets on various Windows versions, along side with setting up the 'just-right' buffer sizes on those sockets to get it right and not have traffic stalling unexpectedly. Been there in our own projects. I'll experiment with the fossil code here. Familiarizing with winhttp.c for now. -- Best Regards, Meilleures salutations, Met vriendelijke groeten, Olivier Mascia _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
