You do get some increased throughput if the problem is dropped connections
and packets, and the distributed upload servers have sufficiently better
connections, and the link has to the final upload server has sufficient
bandwidth to handle the load if the connections are carefully controlled
(i.e. pull rather than push). A TCP/IP link that is completely saturated
will have a much lower throughput than the same link that has only 70% to
80% saturation.
jm7
David Anderson
<[email protected]
ey.edu> To
Sent by: "Lynn W. Taylor" <[email protected]>
boinc_dev-bounces cc
@ssl.berkeley.edu BOINC dev
<[email protected]>
Subject
07/21/2009 12:54 Re: [boinc_dev] Fw: Re: Optimizing
PM uploads.....
It's not a strong attraction, since no projects use them.
But possible factors are:
- increased availability
- political reasons, e.g. wanting to give colleagues or
partner institutions a role (this was the original CPDN motivation)
Increased through is a non-factor since, as you point out,
all data eventually has to get read by the (central) validator anyway.
-- DPA
Lynn W. Taylor wrote:
> I don't really understand the attraction to multiple, distributed upload
> servers.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
