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: 72
Posts: 72   Pages: 8   [ Previous Page | 1 2 3 4 5 6 7 8 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 16528 times and has 71 replies Next Thread
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: Mapping Cancer Markers - Temporarily disabled

Vinbeer, It is technically not at full speed, but within the next week we will be doing some changes to the work units and project weights. By this I mean we are going to reduce the size of the work units for FA@H-Vina and increase the MCM1 application weight to have it's runtime be more evenly split.

Thanks,
-Uplinger
[May 8, 2014 2:57:47 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Speedy51
Veteran Cruncher
New Zealand
Joined: Nov 4, 2005
Post Count: 1326
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Mapping Cancer Markers - Temporarily disabled

Thanks Uplinger, this sounds like a wonderful idea. I am not having any issues getting tasks
----------------------------------------

[May 8, 2014 5:47:26 AM]   Link   Report threatening or abusive post: please login first  Go to top 
johncmacalister2010@gmail.com
Veteran Cruncher
Canada
Joined: Nov 16, 2010
Post Count: 799
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Mapping Cancer Markers - Temporarily disabled

Excellent idea: thanks Uplinger

Vinbeer, It is technically not at full speed, but within the next week we will be doing some changes to the work units and project weights. By this I mean we are going to reduce the size of the work units for FA@H-Vina and increase the MCM1 application weight to have it's runtime be more evenly split.

Thanks,
-Uplinger

----------------------------------------


crunching, crunching, crunching.

AMD Ryzen 5 2600 6-core Processor with Windows 11 64 Pro.

AMD Ryzen 7 3700X 8-Core Processor with Windows 11 64 Pro (part time)


smile
[May 8, 2014 8:40:31 PM]   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: Mapping Cancer Markers - Temporarily disabled

Vinbeer, It is technically not at full speed, but within the next week we will be doing some changes to the work units and project weights. By this I mean we are going to reduce the size of the work units for FA@H-Vina and increase the MCM1 application weight to have it's runtime be more evenly split.

Thanks,
-Uplinger

Uplinger, how does resizing affect checkpointing? Got 2 running that had not done so for 4:50 hours, and this on a laptop. Less dockings, if that is what you're planning to do is not going to change that. It's a críme running these even size them down to just one job, task being a poor word choice in the log, in a task for the tablet. Unplug and poof 8-10 hours are gone. Have had multiple running 25-30 hours with 3 tasks in them according the result log, now one at 80% at 24:51 hours, and analysis shows getting 95% efficiency on average. Either the molecules to dock are made lighter for the androids to process or mid job interval checkpoint is introduced, not really appealing there large models being saved to internal memory on frequent basis. Something's gotta give, as a nightly on-charger crunch produces next to nothing now, a wholly unsatisfactory situation, not to speak of the pile of 195 fails seen on wingman, even my device has started to show them in series at times, all 4 fahv threads bombing.

Now running 7.3.17 and seen a signal 9, heartbeat and retry running to end and sitting in pending validation. No wingman yet that succeeded, so can't say if it's going the pending verification route and the eventual invalid.

So much for an off topic, on topic being, is it because the total work processed on the grid decreasing allowing you to increase share or is it that you've resolved the storage space and passthrough issue?
[May 9, 2014 11:48:21 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: Mapping Cancer Markers - Temporarily disabled

@ lavaflow

FYI on my old Q6600, MCM tasks checkpoint every 10 minutes and always have.
[May 10, 2014 12:32:49 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: Mapping Cancer Markers - Temporarily disabled

lavaflow,

Android does allow for mid job checkpoints. We will just be decreasing the average runtime. So if a work unit was estimated to take 5 hours, we will change that to 4 hours. This means putting a smaller number of jobs in a work unit.

As for bringing up the weight of MCM1, the researchers have taken steps to keep the size of the results lower. The decrease in the grid runtime overall does help, but runtime was not the driving factor for the file size issue.

Thanks,
-Uplinger
[May 12, 2014 3:48:17 PM]   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: Mapping Cancer Markers - Temporarily disabled

lavaflow,

Android does allow for mid job checkpoints. We will just be decreasing the average runtime. So if a work unit was estimated to take 5 hours, we will change that to 4 hours. This means putting a smaller number of jobs in a work unit.

As for bringing up the weight of MCM1, the researchers have taken steps to keep the size of the results lower. The decrease in the grid runtime overall does help, but runtime was not the driving factor for the file size issue.

Thanks,
-Uplinger

So assuming e.g. 1 task with 2 jobs in them can have 4 or more checkpoints in them? My concern is driven by the windows version as i´m watching. The longest has gone 5.5 hours without a checkpoint, <checkpoint_debug> flag activated. You force me into hibernating as the device is not on for that long, in fact it took 3 sessions to finish just one job, or one docking if that is synonymous, of the task. Cep2 is not an option on there, and mcm given the 16 hours seen on a 4770 is not an option either as chances are the 7 days wont be enough. Maybe faah would, but 9 out of 10 are fahv, you´re giving no workable choice, i'll be darned if sitting there micromanaging the part-time devices to cancel out any fahv to just do the faah. And another 30 hour set of 3 is heaving away on the tablet, 72.5 percent at 24:22 hours is one, the other 2 are at 80 percent for the same time. Do you like idle time or don´t you? You/wcg offer very little option but to just permanently skip to e.g. simap. Short, even on tablet, frequently check-pointing, no major progress loss on unplugging. This one running 1.5ghz.
[May 12, 2014 4:45:11 PM]   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: Mapping Cancer Markers - Temporarily disabled

Btw, if you have mastered mid job checkpointing, fahv is meant, is this going to get ported to the windows and other platform versions? That could a peace many.
[May 12, 2014 4:47:58 PM]   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: Mapping Cancer Markers - Temporarily disabled

lavaflow, we are looking into merging the changes for mid job checkpointing. Please remember a little bit of history on this though. Android was released when workunits for fahv did not have the flex parameter enabled, but ran long on android. The new work units released in the past few months have had the flex parameter which has extended the job sizes for FAHV. We will be doing a very in depth beta test for mid job check pointing when the work to port it to the CPU version is complete.

To give you some idea of changes in sizes, Here are some old datapoints:

T 0 A 6 C 24.5769
T 0 A 7 C 28.4571
T 0 A 8 C 32.5567
T 0 A 9 C 34.0878
T 0 A 10 C 35.596
T 0 A 11 C 39.5691
T 0 A 12 C 41.7936
T 0 A 13 C 45.3433

Here are some new ones:

T 0 A 6 C 1387.02
T 0 A 7 C 1631.96
T 0 A 8 C 1082.25
T 0 A 9 C 1448.57
T 0 A 10 C 888.318
T 0 A 11 C 1603.4
T 0 A 12 C 880.547
T 0 A 13 C 1185.96

C = cpu seconds
T = Torsions
A = Atoms

As you can see the new flex with the same atoms/torsions have a lot longer runtimes than what was normal only a few months ago.

Thanks,
-Uplinger
[May 14, 2014 2:57:51 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: Mapping Cancer Markers - Temporarily disabled

Thanks for the expansion. You'd be the winner getting mid-dock saves. Reading around, see you face resume issues, recreating the model and then compute on and then have this pass the validator and a quorum matching, if quorum is required. Right now, both tablet and laptop are off wcg as there's nothing to compute in fair time to even get one task a day to complete in a 'don't want to babysit' ambient. We should be free of concerns loosing umpteen hours of progress because we want to pick up and leave or power down for the devices not having to be on. Yes, all my devices still have a power switch, for the tongue in cheek.
[May 14, 2014 9:03:05 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 72   Pages: 8   [ Previous Page | 1 2 3 4 5 6 7 8 | Next Page ]
[ Jump to Last Post ]
Post new Thread