On Mar 26, 2018, at 2:15 PM, Svyatoslav Mishyn <[email protected]> wrote: > > Here are results of r.sh when stress.sh was run (and all RAM was used > on VPS): > 2018-03-26-19:34:08 time generation: 0.001s; load average: 10.909180 > 2018-03-26-19:34:11 time generation: 0.001s; load average: 10.909180 > 2018-03-26-19:34:14 time generation: 0.001s; load average: 12.918450 > 2018-03-26-19:34:15 time generation: 0.001s; load average: 12.918450 > 2018-03-26-19:34:18 time generation: 0.001s; load average: 14.767090 > 2018-03-26-19:34:22 time generation: 0.001s; load average: 14.767090 > 2018-03-26-19:34:24 time generation: 0.001s; load average: 16.547850 > > and against fossil-scm.org itself (only r.sh): > 2018-03-26-20:01:03 time generation: 0.003s; load average: 0.110000 > 2018-03-26-20:01:07 time generation: 0.004s; load average: 0.100000 > 2018-03-26-20:01:13 time generation: 0.003s; load average: 0.090000 > 2018-03-26-20:01:20 time generation: 0.003s; load average: 0.080000 > 2018-03-26-20:01:26 time generation: 0.003s; load average: 0.070000 > 2018-03-26-20:01:29 time generation: 0.003s; load average: 0.070000 > 2018-03-26-20:01:32 time generation: 0.003s; load average: 0.060000
I don’t see that you’ve factored out the TCP connection round-trip time. Even from one datacenter to another datacenter on the same continent across a fat Internet backbone, a TCP connection still takes at least half a millisecond. Across continents, it becomes tens or hundreds of ms, and when you involve the residential ISPs, it can be even longer. It is bad science to change more than one variable at a time. You’ve got a multiply confounded result set here. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
