• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

TAS-member thread for April 2009: Rosetta, Milkyway and SHA Collision

Alyx

Alyx

Golden Member
Well we are 8 days in and still no thread, so I'm making it! 🙂 I won't have time to do stats, I'm not sure who is keeping track. But we need somewhere to discuss at least!

We are doing Rosetta@Home until the 100M milestone, Milkyway@Home until the 10M milestone, and SHA Collision until the 1M milestone.

As of April 8th...
Rosetta@Home is at 99,742,115!
Milkyway@Home is at 9,129,654!
SHA Collision is at 447,380!


Now go out there and get crunching!
 
I collected the starting stats at the beginning of the month. I'll post an update as soon as I feel like doing one. 😉
 
I was having a great deal of trouble keeping the queue full of Milkyway@Home WUs until I enabled AQUA@Home. They are both working fine. AQUA has about 40K to reach 10M. Maybe we can get two 10Ms this month. Rosetta should be past 100M in two-three days. SHA-1 is a long way off. And very slow to increase.
 
Originally posted by: Rudy Toody
I was having a great deal of trouble keeping the queue full of Milkyway@Home WUs until I enabled AQUA@Home. They are both working fine. AQUA has about 40K to reach 10M. Maybe we can get two 10Ms this month. Rosetta should be past 100M in two-three days. SHA-1 is a long way off. And very slow to increase.
Click to expand...

I'm running MilkyWay at a high Resource Share and SHA-1 Collision at a very low Resource Share so that my computers "beg" for work from MilkyWay whenever it's available, then switch to SHA-1 Collision when they need something to do. With the intermittent work problems at MilkyWay, it's working out to about 3:1 ratio of points between MilkyWay and SHA-1. Considering the fact that MilkyWay gives a LOT of points, I would guess my computers are spending about 60-70% of their time on SHA-1.
 
AQUA@Home has passed the 10M milestone. I am finishing 7 WUs and re-cranking up SHA to run along side Milkyway@Home.
 
SHA is very slow, I've got it set to high on all my machines yet its only getting a few points a day... 🙁 Time to reduce the number of active projects I guess.
 
I've passed 100k for Milkyway; I'm considering stopping that project and concentrating mainly on SHA Collision. But before I do that, I would like to know how the rest of you feel about it. I wouldn't want anyone to feel betrayed.

Rex
 
Rex, no risk for that ... you crunch for the TeAm, for TAS at your heart's delight ...

In MilkyWay@Home we need about 450 000 cobblestones to reach our goal, in SHA Collision Search we need about 200 K to reach the goal.
In MilkyWay we produce about 55 - 60K per day, will reach the goal within 8 - 9 days.
In SHA Collision Search we produce approx 50 - 60K per day and will reach the goal within 7 - 8 days.

When we reached our goals, we have helped the TeAm to reach 100 000 000 credits in Rosetta@home, 10 000 000 credits in MilkyWay@home and 1 000 000 credits in SHA Collision Search.

A good month ... 😉
 
Originally posted by: rabrittain
I've passed 100k for Milkyway; I'm considering stopping that project and concentrating mainly on SHA Collision. But before I do that, I would like to know how the rest of you feel about it. I wouldn't want anyone to feel betrayed.

Rex
Click to expand...

There's no requirement that you have to even work on the same project(s) that TAS is doing in any given month. We just do it as a fun way to get a variety in our crunching and (for me) to get regular stats updates. As Captain Jack Sparrow would say, the project of the month is "more of a guideline than a rule anyway".

SHA-1 needs help to reach the goal, so I don't think anyone would be upset at you switching over. I plan to keep working on both MilkyWay and SHA-1 until the end of the month in the (almost useless) hope that I'll get enough work to pass 1 million total points before then, so I'll do my best to take up the slack if you do switch. 🙂
 
Originally posted by: petrusbroder
In MilkyWay@Home we need about 450 000 cobblestones to reach our goal....

In MilkyWay we produce about 55 - 60K per day, will reach the goal within 8 - 9 days.
Click to expand...
Milkyway is very close to forking off the GPU crunching into a possible sub-project. I'm not sure whether the scoring will be joint or separate but if the latter my current ~35k ppd will likely drop down to ~12k ppd. If they don't split it and I can keep my GPU's fully fed I should be at a solid 55k ppd instead. 🙂

-jim

 
Less than 100 000 cobblestones to go in SHA-1 Collision Search Graz! 😀
We will pass that milestone within 35 - 37 hours. :beer:

That will be the second goal TAS has reached - only one more goal to go: 10 000 000 cobblestones im MilkyWay@home.
There some 369 000 cobblestones are needed - approximately 6.5 more days of crunching! WTG TeAm!
 
The goal in SHA-1 Collision Search Graz is reached: just now the TeAm has 1 020 060 cobblestones. Well done! :beer: :cookie: :thumbsup:
The goal in Rosetta@home was reached quite a few days ago. :beer: :cookie: :thumbsup:

Now we need to reach the goal in MilkyWay@Home: 10 000 000 cobblestones. We have 256929 cobblestones to crunch ...

I'll switch most of my comps over to that project ... 🙂
 
Thanks for the update, Peter!

I just lost a quad due to temperature issues. It was one of the two that somewhat worked with Milkway. I just reached my personal goal of 250K and have switched to Poem and Docking for the remainder of the month.

I don't ever want to see Milkyway again. It has been my nemesis!

Crunch on, everyone. I'll see you next time.
 
Originally posted by: petrusbroder
The goal in SHA-1 Collision Search Graz is reached: just now the TeAm has 1 020 060 cobblestones. Well done! :beer: :cookie: :thumbsup:
The goal in Rosetta@home was reached quite a few days ago. :beer: :cookie: :thumbsup:

Now we need to reach the goal in MilkyWay@Home: 10 000 000 cobblestones. We have 256929 cobblestones to crunch ...

I'll switch most of my comps over to that project ... 🙂
Click to expand...
Just a reminder for those of you perhaps new to crunching Milky Way. The optimized (and authorized 🙂) apps are sooo much more efficient than the stock apps. Even more so if you have an ATI HD38xx or HD48xx GPU. When crunching with the GPU BOINC will happily crunch another CPU-bound project simultaneously, so it's the best of both worlds.

get 'em here: http://www.zslip.com

-jim

 
Originally posted by: Philippart
do the gpu apps work on a HD3650 too? I have two of them ready to crunch!
Click to expand...
Not currently. Only the HD38xx and HD48xx cards.

That being said, I bought an HD3850 for ~$75 incl. shipping last month and it's capable of ~20k+ ppd if it can get enough WU's. The project is shortly to split into separate CPU/GPU work queues (and scoring) which is intended to make sure everyone has enough to crunch.

see: http://milkyway.cs.rpi.edu/milkyway_gpu/index.php

-jim

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top