Downloads use the basic HTTP "GET" and that transfers one file, with no additional "downloader" CGI. The download server is a plain vanilla web server.
Uploads use a "PUT" with a simple CGI to process it. In both cases, the processing is very lightweight. Contacts to the scheduler are more complex, they involve access to the database and a bunch of lookups. The scheduler PUT sends an XML file which is immediately processed and returns a response immediately. There is a fixed cost in CPU to open a connection to the database and look up the host record -- the cost of reporting two sessions in the XML is pretty low. In other words, it's worth doing for the scheduler. For uploads and downloads less so. To really take advantage of your idea, you'd want to be able to deal with transactions that die in the middle: if I'm uploading two work units, and it quits just after the first one, you'd need a way to handle that -- otherwise your bigger, longer connections are less likely to finish under extreme load. My ultimate goal is not to address "heavy" loads, but to address the kind of load that happens after an extended outage, or long bumpy period where the load is so high it crushes the servers. If we've got that handled, the merely heavy case will handle itself. -- Lynn erbenton wrote: > Re-read what i wrote, i think you misunderstood what i was saying. > When you have a bunch of files in the "Ready to Report" state and you > click on > the "project update" button they seem to upload all at once vs the > Transfer tab where > they seem to upload 1 at a time > > > > _______________________________________________ > 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.
