Since some of you are complaining about the downloads of new tasks here is a solution that has worked for me and many others.

1) Download TCPOptimizer (sorry I don't have a link so maybe try google)
2) Run the program, at the bottom it says Choose Settings: Click on Optimal then click Custom and place a check mark next to "TimeStamps" then click Apply!
3) reboot and problem solved you should download nice and fast for every task.

Since some of you are complaining about the downloads of new tasks here is a solution that has worked for me and many others.

1) Download TCPOptimizer (sorry I don't have a link so maybe try google)
2) Run the program, at the bottom it says Choose Settings: Click on Optimal then click Custom and place a check mark next to "TimeStamps" then click Apply!
3) reboot and problem solved you should download nice and fast for every task.

Apply the Optimal then do Custom.

Since some of you are complaining about the downloads of new tasks here is a solution that has worked for me and many others.

1) Download TCPOptimizer (sorry I don't have a link so maybe try google)
2) Run the program, at the bottom it says Choose Settings: Click on Optimal then click Custom and place a check mark next to "TimeStamps" then click Apply!
3) reboot and problem solved you should download nice and fast for every task.

Alternatively (rather than using TCPOptimizer) if you're running Windows, see Richard Haselgrove's two easy methods http://setiathome.berkeley.edu/forum_thread.php?id=71002&postid=1344153 that set a Registry parameter to relieve WU download congestion on your PC. (Other posters recently pointed out that thread here, but apparently some posters haven't yet understood). Check it out, the Registry setting completely relieved WU download congestion for my 3 PCs.[/url]

---

Sabertooth Z77, i7-3770K@4.2GHz, GTX680, W8.1Pro x64
P5N32-E SLI, C2D E8400@3Ghz, GTX580, Win7SP1Pro x64 & PCLinuxOS2015 x64

Kudos: to Matt, Jeff, Eric, and anybody else who helped make the move. While Matt says some things are still throttled so the project comes up to speed slowly, things appear to be working well and uploads/downloads/scheduler requests seemto be going through much faster than they did up the hill. So far, so good.

Gripes: None worth mentioning.

---

Donald
Infernal Optimist / Submariner, retired

Minor gripe/inquiry:

My (and many people in my RAC range) score dropped by about 77,000 cobblestones just before the outage, and then came back after the outage: Wha Hoppen?

---

.

Hello, from Albany, CA!...

Gripes - none currently. I'm sure there are things to gripe about still but right now the kudos I have to give for the colo's transfer rates are just wow.

Kudos overshadow the gripes, and will likely continue to do so for the near future :)

Kudos: 294 Mbps

Gripes: What is a gripe?

---

gripe: i wish i could assign projects to particular number of processors. context switching is so 00's. :P

---

gripe: i wish i could assign projects to particular number of processors. context switching is so 00's. :P

Actually that can be done now.
http://boinc.berkeley.edu/wiki/Client_configuration#Application_configuration

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Kudos: Everyone involved in the colo transfer. It's hard to tell the xfer rate I'm actually getting since the downloads I've seen disappear too fast (that's NOT a gripe) but they appear to be 1500 KB/s or faster.
Gripes: Me, for thinking you guys didn't care about our xfer rates.

I'll be making another donation with my next paycheck.

---

Still waiting for my first download since the move. Saturday midnight and still waiting...

---

/eric

Still waiting for my first download since the move. Saturday midnight and still waiting...

Exit BOINC, restart it & post the startup log in a new thread. Then people might be able to help you.


EDIT- just had a look at your system, and you have 3 AP WUs all downloaded today. Depending on your resource share, and the size of your cache settings, given the minimal processing power of the system that is probably all the work the system can handle.

---

Grant
Darwin NT

Still waiting for my first download since the move. Saturday midnight and still waiting...

If restarting the manager doesn't work then set your other projects to no new tasks for a while and then you will likely get more work from this one.

Cheers.

Kudos: (1) to members & esp. Richard Haselgrove (his RegEdit methods) for the Windows TCP Fix prior to the more recent Colocation, and (2) to all who chose & implemented the Colocation move. I was at wits end about the WU Download choking & was ready to pull my plug from S@H Project prior to both of these kudo-worthy events.

Gripes: Only one ATM, see http://setiathome.berkeley.edu/forum_thread.php?id=71040&postid=1354413

---

Sabertooth Z77, i7-3770K@4.2GHz, GTX680, W8.1Pro x64
P5N32-E SLI, C2D E8400@3Ghz, GTX580, Win7SP1Pro x64 & PCLinuxOS2015 x64

Gripes: You could have a more detailed cpu information page. BOINC says I'm using a quadcore chip @ 2.40GHz when I'm running all cores @ 3.5GHz

Kudos: Keep up the good work i.e. server move/faster download of information.

---

10.7 billion ops/sec

Gripes: You could have a more detailed cpu information page. BOINC says I'm using a quadcore chip @ 2.40GHz when I'm running all cores @ 3.5GHz

Kudos: Keep up the good work i.e. server move/faster download of information.

Since some cores are now variable GHz even without overclocking them (like mine), I think it's best that they just classify them as the base core rate that the chips are advertised and sold at. I think I'm understanding that you have the quadcore 2.4 but you have it overclocked to 3.5?

That is correct.

---

10.7 billion ops/sec

Gripes: You could have a more detailed cpu information page. BOINC says I'm using a quadcore chip @ 2.40GHz when I'm running all cores @ 3.5GHz

Kudos: Keep up the good work i.e. server move/faster download of information.

They made the choice to list the default the default CPU info. Which is nice to have for comparison. The optimized apps record the actual CPU speed in stderr_txt.

     CPUID: AMD Athlon(tm) 64 X2 Dual Core Processor 5400+ 
     Speed: 1 x 3010 MHz 
     Cache: L1=64K L2=512K
  Features: MMX SSE SSE2 SSE3

Perhaps they will add that to the v7 SETI@Home applications.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[