> Le 28 déc. 2017 à 15:42, Olivier Mascia <o...@integral.be> a écrit : > > I'll experiment with the fossil code here. Familiarizing with winhttp.c for > now.
I haven't yet come to bottom of it, but using IP (IPv4) in the URL (instead of name) changes it all!! There seem to be a high price paid in resolving the server name on each round trip (from client). This or, due to dual-stack being the norm on Windows, client connections loose time trying IPv6 (generally preferred by Windows when DNS reports both AAAA and A records for a name) before falling back to IPv4. My test now runs (the network portion, excluding rebuilding metadata and next things) within 50 seconds for all 250 round-trips and 102700 artifacts received. It was close to 1 hour and a half before. I'm further analysing http_socket.c (socket_open) following this discovery. -- 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
