Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 10
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1491 times and has 9 replies Next Thread
ravenigma
Cruncher
USA
Joined: Oct 3, 2012
Post Count: 46
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Longer Work Units

I've seen a dramatic increase in processing times lately. Previously I was seeing 30 minutes to 1.5 hours per task, now I'm seeing 4 to 6 hours!

I'm sure this is due to a difference in what we're actually crunching. I'm just curious what that is.

Currently running tasks from batch 6484. 4+ hours on i7-3770k @ 4.2GHz. AMD Phenom II 965 @ 3.4GHz running at about 5.5 to 6 hours. Both are in Win7 x64.

Thanks!
----------------------------------------

[Aug 5, 2014 12:11:22 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Speedy51
Veteran Cruncher
New Zealand
Joined: Nov 4, 2005
Post Count: 1265
Status: Recently Active
Project Badges:
Reply to this Post  Reply with Quote 
Re: Longer Work Units

I am running tasks from batch 6451 in 6.7 hours & batch 6450 in 6.72 hours. This is on a first gen I 7 stock 3.33 GHz running at a slightly overclocked of 3.43 GHz also on 64 bit Windows 7. On a slight side note are you achieving your over clock of 3.42 on air cooling? Mine is on air with a Prolimatech Megahalems Rev. B cooler
----------------------------------------

----------------------------------------
[Edit 1 times, last edit by Speedy51 at Aug 5, 2014 5:42:58 AM]
[Aug 5, 2014 5:39:16 AM]   Link   Report threatening or abusive post: please login first  Go to top 
l_mckeon
Senior Cruncher
Joined: Oct 20, 2007
Post Count: 439
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Longer Work Units

On my old Q6600 they're running about 9 hours. I hope they don't get any longer, but I'll continue to crunch whatever they send me.
----------------------------------------
[Edit 1 times, last edit by l_mckeon at Aug 6, 2014 1:22:55 AM]
[Aug 6, 2014 1:22:11 AM]   Link   Report threatening or abusive post: please login first  Go to top 
uplinger
Former World Community Grid Tech
Joined: May 23, 2005
Post Count: 3952
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Longer Work Units

The length of MCM1 work units are not split up by us. There are multiple variables that the researchers use to gather the proper data they need. This causes the work units to swing in runtime length. As for what exactly was changed, that I can not help with.

Thanks,
-Uplinger
[Aug 6, 2014 1:35:30 AM]   Link   Report threatening or abusive post: please login first  Go to top 
ravenigma
Cruncher
USA
Joined: Oct 3, 2012
Post Count: 46
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Longer Work Units

I am running tasks from batch 6451 in 6.7 hours & batch 6450 in 6.72 hours. This is on a first gen I 7 stock 3.33 GHz running at a slightly overclocked of 3.43 GHz also on 64 bit Windows 7. On a slight side note are you achieving your over clock of 3.42 on air cooling? Mine is on air with a Prolimatech Megahalems Rev. B cooler


Speedy, the AMD chip is on air and the Ivy Bridge @ 4.2GHz is on self-contained liquid cooling (Antec H2O 920 with Gentle Typhoon fans in push/pull config).
----------------------------------------

[Aug 6, 2014 2:50:50 AM]   Link   Report threatening or abusive post: please login first  Go to top 
ravenigma
Cruncher
USA
Joined: Oct 3, 2012
Post Count: 46
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Longer Work Units

The length of MCM1 work units are not split up by us. There are multiple variables that the researchers use to gather the proper data they need. This causes the work units to swing in runtime length. As for what exactly was changed, that I can not help with.

Thanks,
-Uplinger


Thanks, Uplinger, for commenting on this thread. I posted out of curiosity more than anything else and was just hoping someone from the MCM project might respond. We crunchers are always appreciative to know what's going on and I thought such a drastic swing in crunching times might have some interesting information to go along with it. As always, I'm happy to keep on crunching, regardless. The science is more than worth it.
----------------------------------------

[Aug 6, 2014 6:00:25 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Longer Work Units

On my old Q6600 they're running about 9 hours. I hope they don't get any longer, but I'll continue to crunch whatever they send me.

From 6463 to 6482 there was a skip up of another 50 minutes on the diminutive 4770 at 3.7ghz. According history that's still an hour short of the averages seen in the late december-march time-frame. Looks like we were spoiled with relative short runtimes in recent months.
[Aug 6, 2014 8:03:19 AM]   Link   Report threatening or abusive post: please login first  Go to top 
cubes
World Community Grid Tech, Mapping Cancer Markers and Help Conquer Scientist
Canada
Joined: Mar 3, 2007
Post Count: 58
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Longer Work Units

ravenigma, the time difference you noticed is the result of another shift in the search parameters. We have temporarily shifted our search back to signatures in the size range of 10-20 biomarkers. These new work units should run closer to 5 hours on average. Previously, the MCM project was exploring longer (21-25) and shorter (5-9) signatures, and the run-times were more variable, and generally shorter.

We'll be sure to announce major changes to work units or the search strategy in general. For now, we're still working on lung cancer, and still considering a broad range of biomarkers. We're slowly building up to an optimizing phase where we'll narrow the search considerably.

As always, thank you for your donated compute cycles and your interest in the project.

Christian A. Cumbaa
Research Associate, Princess Margaret Cancer Centre
[Aug 7, 2014 1:19:21 PM]   Link   Report threatening or abusive post: please login first  Go to top 
vlado101
Senior Cruncher
Joined: Jul 23, 2013
Post Count: 226
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Longer Work Units

ravenigma, the time difference you noticed is the result of another shift in the search parameters. We have temporarily shifted our search back to signatures in the size range of 10-20 biomarkers. These new work units should run closer to 5 hours on average. Previously, the MCM project was exploring longer (21-25) and shorter (5-9) signatures, and the run-times were more variable, and generally shorter.

We'll be sure to announce major changes to work units or the search strategy in general. For now, we're still working on lung cancer, and still considering a broad range of biomarkers. We're slowly building up to an optimizing phase where we'll narrow the search considerably.

As always, thank you for your donated compute cycles and your interest in the project.

Christian A. Cumbaa
Research Associate, Princess Margaret Cancer Centre



Thank you for letting us know.
----------------------------------------

[Aug 7, 2014 2:43:23 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Speedy51
Veteran Cruncher
New Zealand
Joined: Nov 4, 2005
Post Count: 1265
Status: Recently Active
Project Badges:
Reply to this Post  Reply with Quote 
Re: Longer Work Units

Thanks for the update Christian. I would just like to report that batch 7134 is running in the 6.5 to 7.7 hours. This is on a first gen I 7 980 X stock speeds of 3.33 slightly overclocked to 3.43 GHz
----------------------------------------

[Aug 30, 2014 2:23:27 AM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread