Still got one refusing to complete but another four seem to have uploaded without isue.
Reply
Quote
I have two finished tasks that I haven't been able to get uploaded to the server all day for some reason.
Tried all the tricks that I know, but nothing has worked. Just keep getting retried. Counts are 11 and 14 attempts so far.
I also have two tasks from different computers that refuse to upload is there a way to rectify this or should they just be aborted?
Reply
Quote
I have two finished tasks that I haven't been able to get uploaded to the server all day for some reason.
Tried all the tricks that I know, but nothing has worked. Just keep getting retried. Counts are 11 and 14 attempts so far.
I also have two tasks from different computers that refuse to upload is there a way to rectify this or should they just be aborted?
Don't abort them. They can be aborted from the server if that becomes necessary. They do not interfere with new WUs DLing so we can keep on crunching.
Reply
Quote
Thanks for reply.
Reply
Quote
So what magic rabbit did you pull out of your hat @valterc?
I see that both my stalled uploads cleared out sometime today after I last checked this morning.
!Yay! In time to before deadline.
Reply
Quote
Nice work Valter! Mine have all ULed and back to normal :-)
Reply
Quote
Why is the number of Queued genes/isoforms greater than the number of genes/isoforms? Was something added to the project? Source: science status page
Reply
Quote
valtercProject administrator
Project tester
Send message
Joined: 30 Oct 13
Posts: 624
Credit: 34,677,535
RAC: 0
Why is the number of Queued genes/isoforms greater than the number of genes/isoforms? Was something added to the project? Source: science status page
Well, there is something wrong with it.... I will check this out.
Reply
Quote
It is looking like the original count of genes/isoforms was/is wrong. I believe we still have at least 5 days if not 7 more days of work left to crunch. The queued number seems to be the more accurate count. Work seems to be coming in descending alphabetical order based on gene name and it takes about 1 day to 1 1/2 days per letter of the alphabet, currently finishing up the 'F' series. The status page will show over 100% (probably 101% to 102%) by the time all the genes have been completed.
Reply
Quote
It is looking like the original count of genes/isoforms was/is wrong. I believe we still have at least 5 days if not 7 more days of work left to crunch. The queued number seems to be the more accurate count.Provided that this is right, there are 888 genes left ("queued"-"executed"=88374-87486). At the present rate of 90.40/day it will take 9.823 days (9 days, 19 hours, 45 minutes and 8 seconds) to complete. It will take much longer than that, given that the timeout is 5 days, and there will be some workunits stuck on inactive hosts. The work availability will be sporadic after 10 days from now.
The status page will show over 100% (probably 101% to 102%) by the time all the genes have been completed.The percentage is the fraction of the "executed" and the "# genes / isoforms".
Now it's 87486 / 87554 = 0.999223336... = 99.92%
Provided that the "executed" will go over the "# genes / isoforms" to reach the "queued" it will be:
88374 / 87554 = 1.0093656486... = 100.94%
Reply
Quote
One "gene" / "isoform" is how many work units ?
Also to collect the last few days of results, I recommend to up the parallel sending of work units from 2 to 3 workers, reducing the amount of stale work units, that get stuck on unresponsive hosts.
Reply
Quote
valtercProject administrator
Project tester
Send message
Joined: 30 Oct 13
Posts: 624
Credit: 34,677,535
RAC: 0
Yep, there is obviously something wrong in the table. Some genes, in the past, were "expanded" with different parameters (so there are duplicates in the gene list), other ones were expansions with no real gene inside (no gene seed, we call them "empties"). The overhead should be something around 1000.
Anyway the situation right now is that ALL the genes were put into the queue and yes, the order is lexicographical descending, the last one will be A2LD1
Reply
Quote
The number of queued is rising (it's 88856 now), so we may reach 102% in the end :)
Reply
Quote
valtercProject administrator
Project tester
Send message
Joined: 30 Oct 13
Posts: 624
Credit: 34,677,535
RAC: 0
The number of queued is rising (it's 88856 now), so we may reach 102% in the end :)
Yes, this counts also the "other" genes, it would be rather complicated to fix it now, that 2% more should be considered as a "necessary overhead" ;)
Reply
Quote
Can you accelerate "gene_work_generator" anyhow ?
The amount of tasks up for grabs is always zero, meaning that people have more workers than your TN-GRID servers can generate.
This is especially important now, where WCG project is down and Rosetta is out-of-work-units (again).
Reply
Quote
Can you accelerate "gene_work_generator" anyhow ?
The amount of tasks up for grabs is always zero, meaning that people have more workers than your TN-GRID servers can generate.
This is especially important now, where WCG project is down and Rosetta is out-of-work-units (again).
But that would just mean that TN-Grid would go dormant in (say) 8 days instead of 10.
Better the effort was put into bringing forward the next set of gene expansions than accelerating this set.
Reply
Quote
valtercProject administrator
Project tester
Send message
Joined: 30 Oct 13
Posts: 624
Credit: 34,677,535
RAC: 0
Can you accelerate "gene_work_generator" anyhow ?
The amount of tasks up for grabs is always zero, meaning that people have more workers than your TN-GRID servers can generate.
This is especially important now, where WCG project is down and Rosetta is out-of-work-units (again).
At this time, with our hardware resources, this is the best we can do...
Reply
Quote
So what's the situation? Can we expect a limited amount of new work from this point on? Or are we left to guess what's to become?
Reply
Quote
Looks like we will finish up this group of work in the next 12 to 24 hours. I hope Denis has a group to distribute while waiting on new work here.
Reply
Quote
You be interested to know that I can't access Denis at Home from Ukraine, it's website is blocked
Reply
Quote