On Dec 28, 2017, at 6:11 AM, Olivier Mascia <o...@integral.be> wrote: > > *** time skew *** server is slow by 106.6 seconds
…snip… > I'll have a close look in the next weeks at the source code of the Windows > server feature of Fossil. The warning "*** time skew *** will certainly be > an interesting starting point. That has nothing to do with the Windows-specific parts of Fossil. It simply means your client and server clocks aren’t synchronized. One (or both?) of them isn’t getting a regular NTP update, or one of them is pointed at an NTP server that is itself desynchronized. Fossil reports this because the skew can be reflected in the file timestamps in such a way that it screws up build systems based on timestamps, which is most of them. > Our own software is actually much like Fossil: single process, multi-usages, > with its own HTTPS embedded server (using OpenSSL). (Albeit currently only > available on Windows, so we have good experience in that area of HTTP serving > on Windows using custom C/C++ code). The current Windows-specific parts of Fossil server use thread-per-connection, according to a recent mailing list message. As you know, that’s not ideal. For a maximum of 10 clients, it’s probably insignificant, but if you could rewrite it using WSAEventSelect() or similar, that would be more efficient. That might be really difficult, though, since the POSIX builds of Fossil server use fork() instead, which means the server code probably isn’t written in a way that would easily give you the data to ship in an event-driven manner. drh, I seem to recall messages about non-free()’d buffers in the Fossil server code, where the patch was rejected with the argument that the forked child is about to die anyway, so why bother freeing the buffer. That doesn’t really apply in a single-process server, as I expect applies on the Windows side. Will Fossil server leak memory on Windows? _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users