On Tuesday 21 August 2007 14:27, freenetwork at web.de wrote: > >Using the median insteed of the mean solves that problem... Moreover > >really high ping times are not possible because there is a timeout. > > If above assumtions are correct, one could say that: > - in every ping time the local node has to a remote peer not only the local load characteristica (cpu/mem/hd load) but also the remote load is incorporated and the network between them: > - - local load because of local work like cpu-using programs (parallel runing boinc, etc) > - - remote load because of all the above > - - connection load like network congestion due to ISP/LAN traffic or bandwidth > > Also we have different setups: > - a) two nodes running on the same computer > - - here local and remote load are effectively the same so a "doubled load" on one computer and none on the other > - b) two nodes running on distinct computers but over a very highspeed network (=LAN) > - c)two nodes running on distinct computers and around half the globe (normal usage) > > let's draw these up: > > _________ |___a)___ |___b)___ |___c)___ > local load |2x |1x |1x > remote load |none |1x |1x > network load |none |small |1x > > As the average ping time is used to determine the local load > - the network load is irrelevant > - the remote load is irrelevant > > Therefore the local load can safely be calculated from the _smalles ping time of all peers_ and not an average of these because > - for a) the determined local load actually would be doubled because on one computer there are two nodes running that affect each other with their own generated load > - - irrelevant as this would not create a lower ping time as the normal scenario c) > - for b) the ping time can be used as b) incorporates the local load (+ extra load from remote but not network) > - - the lowest ping time would account for local and remote load > - for c) the ping time can be used as c) incorporates the local load (+ extra load from remote and also the network) > - - the lowest ping time would account for local and remote load and also the network load, so the ping times are actually higher than they need to be as the network has a large impact to the ping time that's understood as "local load" > > > Am I way off here? :)
Yes. The lowest ping will account for the network load of the node you are directly connected to because it happens to be on the same computer, or on the same LAN. If the NATed internet connection is temporarily overloaded, *this will not show up* on the lowest ping time. AIMD may well detect this, but AIMD does not directly affect the number of requests we accept. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20070822/bc740f0b/attachment.pgp>
