Questions and Answers :
Windows :
More Bandwidth? Downloads seem much faster...
Message board moderation
Author | Message |
---|---|
Enzeder Send message Joined: 30 Jan 01 Posts: 6 Credit: 56,862,055 RAC: 18 |
Downloads the last few days (maybe since the last maintenance) seem much faster. It's awesome. I've been afraid to mention it in case I jinx things. But why do so few tasks download? I have the following set in preferences: Maintain enough tasks to keep busy for at least: 0.5 days (max 10 days). ... and up to an additional: 0.5 days On a 2nd gen i7 I end up with only 2 tasks waiting in the queue (in addition to the 8 running). Regular 6.03 tasks take about 4 hours, so I don't see how that equals ½ to 1 days worth of work. Shouldn't there be between 96 and 192 hours of work either running or waiting to run? PS: In case it makes a difference, the PC is only running SETI. |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
New download servers; AstroPulse isn't being split and sent (8MB tasks); SETI@Home "shorties" aren't being sent out = good bandwidth. I'm not sure about the cache though, it has changed significantly since BOINC v7, but I was under the impression that it is total cache, not per CPU. So .5 + .5 = 1 full day (24 hours) of work, including what is currently running. |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
I'm not sure about the cache though, it has changed significantly since BOINC v7, but I was under the impression that it is total cache, not per CPU. So .5 + .5 = 1 full day (24 hours) of work, including what is currently running. That's correct. So 8 * 4 hours = 32 hours, is more than a day's worth of work. The cache won't be added to until it falls below the minimum work buffer value (0.5 days, or 12 hours). Yes, that means that there is a possibility that one or more cores are idle before work request. |
Enzeder Send message Joined: 30 Jan 01 Posts: 6 Credit: 56,862,055 RAC: 18 |
New download servers; AstroPulse isn't being split and sent (8MB tasks); SETI@Home "shorties" aren't being sent out = good bandwidth. Cool. Good to know. Thanks. I'm not sure about the cache though, it has changed significantly since BOINC v7, but I was under the impression that it is total cache, not per CPU. So .5 + .5 = 1 full day (24 hours) of work, including what is currently running. Hmmm. That's awkward, but also good to know. Pity they can't be tied to cores, or set per PC. I have some PC's with 2 cores, and others with 24... |
BilBg Send message Joined: 27 May 07 Posts: 3720 Credit: 9,385,827 RAC: 0 |
or set per PC... Why not? It can: 1) by local preferences 2) by "separate preferences for home", etc. I have some PC's with 2 cores, and others with 24... It doesn't matter (because you don't need "cache per core") 10+10 days set for my slower CPU is 2-4 tasks 7+7 days set for my faster CPU is ~50 tasks 1 day of work for fast GPU may be 1000 tasks You need to just set the calendar days. You say to BOINC: "I want "reserve" tasks on-board to keep this machine with work for XX days" BOINC knows how many tasks are completed per day by this computer so knows what means "1 day work" for it. It doesn't matter how the computer completed those 10 or 1000 tasks per day. (e.g. using 24 cores for only 1 hour a day, or 1 fast GPU running all the time) I suspect you run this computer for 8 hours/day or you use it for other CPU heavy programs. (your Computers are hidden so we can't check CPU time vs Run time) Â - ALF - "Find out what you don't do well ..... then don't do it!" :) Â |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.