Message boards :
Number crunching :
Uploads slow and overtake the system
Message board moderation
Previous · 1 · 2
Joined: 15 Jun 12
Update Note: I have put a restriction of 20kbs in the system for Network Communication, which in turn places a 20kbs max per each reporting task, of which only two tasks try to report at a time on my system.
This seems to have improved things all around. It is now regularly getting tasks reported (albeit a bit slowly), and for the most part is not interfering with other things on my system (although it does occasionally). I can mostly watch videos or streamed tv without too many interruptions, as well as being able to communicate via email, messaging, and social media.
Additionally, on the tech problem solving front, I have noticed when watching both this capped stream of reporting tasks, and the un-capped stream of reporting tasks, that the measured internet throughput on Windows Task Manager was showing much higher pulses coming from BOINC than was being indicated within the BOINC app. So pulses being uploaded at times were many times what was being indicated in BOINC. Maybe that is what is interfering with other things in the system. So maybe a tech person could see if that is configured properly on how it is reporting, and if there is something causing those upload pulses?
Just a thought.
Joined: 1 Jan 07
I think that BOINC Manager displays an averaged speed, derived from "the position reached in the file, divided by the elapsed time since the start of the transfer" (or something like that). On these long-distance intercontinental links, it's not unusual for individual packets to be lost from the data stream. The internet TCP/IP protocol is designed to be tolerant of these known weaknesses: each packet has to be acknowledged by the receiver, and if no ack is received, the sender repeats the packet until it gets though.
This means that on big transfers like CPDN's, there can be temporary 'holes' in the received file, later patched by these resent packets. I think BOINC's indicated speed is based on the 'solid' part of the file, up to the first 'hole'. On the other hand, I think that Windows Task Manager will be indicating the instantaneous speed, including the resent packets. The difference may simply be down to the different measurement techniques,