I have noticed this over the last few days on more than one PC. When The WU starts it jumps from 0% to just less than 50 % but the length to completion does not change from the approximate 4.1 to 4.5 hours.

Is there a reason?

---

And here we go some more.....WORK?

I see this too.
And then having done so the progress only slowly goes up from there.
When running I've only seen them between 50% (just started) and ~56% (when actually about 80% done in terms of the final time).

But this is not a new happening:

http://numberfields.asu.edu/NumberFields/forum_thread.php?id=49&postid=404

I see this too.
And then having done so the progress only slowly goes up from there.
When running I've only seen them between 50% (just started) and ~56% (when actually about 80% done in terms of the final time).

But this is not a new happening:

http://numberfields.asu.edu/NumberFields/forum_thread.php?id=49&postid=404

Somehow I missed Viking69's original post. Thanks for answering Gordon!

I see this too.
And then having done so the progress only slowly goes up from there.
When running I've only seen them between 50% (just started) and ~56% (when actually about 80% done in terms of the final time).

But this is not a new happening:

http://numberfields.asu.edu/NumberFields/forum_thread.php?id=49&postid=404

Hi Gordon,

thats normal I guess, the decic WU´s I computed are allways started at 50,000 %, and needs some houres to reach the 100%.
Note thats this in not an error, possible the must pre-compute the WU (e.g. loading the WU-preferences)

I see this too.
And then having done so the progress only slowly goes up from there.
When running I've only seen them between 50% (just started) and ~56% (when actually about 80% done in terms of the final time).

But this is not a new happening:

http://numberfields.asu.edu/NumberFields/forum_thread.php?id=49&postid=404

Thank you Gordon, the link was very helpful in explaining the process of computation.

---

And here we go some more.....WORK?

FYI: Here's a CSV file of the progression (every 10 mins) as noted in BOINC. The first line is before it starts and the last line is once it has finished.
As you can see it starts at 50% done, and with <10 mins (<3%) to go it is still only reporting 65%.

Time,Task State,CPU used,Fraction done,Est. CPU left,Final CPU time
Tue May 20 19:32:46 BST 2014,UNINITIALIZED,0.000000,0.000000,23464.046263,0.000000
Tue May 20 19:42:46 BST 2014,EXECUTING,265.886100,0.502670,17400.060165,0.000000
Tue May 20 19:52:46 BST 2014,SUSPENDED,650.137200,0.502690,17205.181341,0.000000
Tue May 20 20:02:46 BST 2014,EXECUTING,1032.048000,0.502752,17010.064858,0.000000
Tue May 20 20:12:46 BST 2014,EXECUTING,1419.354000,0.505365,16758.002815,0.000000
Tue May 20 20:22:46 BST 2014,SUSPENDED,1807.555000,0.505396,16564.662820,0.000000
Tue May 20 20:32:46 BST 2014,SUSPENDED,2188.820000,0.505498,16369.458294,0.000000
Tue May 20 20:42:46 BST 2014,EXECUTING,2574.767000,0.508061,16122.194516,0.000000
Tue May 20 20:52:46 BST 2014,EXECUTING,2960.537000,0.508102,15929.411455,0.000000
Tue May 20 21:02:46 BST 2014,SUSPENDED,3344.121000,0.510715,15683.888881,0.000000
Tue May 20 21:12:46 BST 2014,EXECUTING,3732.466000,0.510776,15492.147992,0.000000
Tue May 20 21:22:46 BST 2014,EXECUTING,4113.001000,0.510828,15300.357428,0.000000
Tue May 20 21:32:46 BST 2014,EXECUTING,4500.635000,0.513446,15058.266494,0.000000
Tue May 20 21:42:46 BST 2014,SUSPENDED,4889.064000,0.513508,14867.670043,0.000000
Tue May 20 21:52:46 BST 2014,EXECUTING,5270.161000,0.516100,14629.190590,0.000000
Tue May 20 22:02:46 BST 2014,EXECUTING,5657.470000,0.516173,14438.764948,0.000000
Tue May 20 22:12:46 BST 2014,SUSPENDED,6043.750000,0.516255,14248.942726,0.000000
Tue May 20 22:22:46 BST 2014,SUSPENDED,6427.412000,0.518837,14014.326170,0.000000
Tue May 20 22:32:46 BST 2014,EXECUTING,6814.755000,0.518919,13825.228335,0.000000
Tue May 20 22:42:46 BST 2014,EXECUTING,7197.811000,0.521512,13592.896091,0.000000
Tue May 20 22:52:46 BST 2014,SUSPENDED,7584.926000,0.521615,13404.927744,0.000000
Tue May 20 23:02:46 BST 2014,EXECUTING,7970.413000,0.524207,13175.652242,0.000000
Tue May 20 23:12:46 BST 2014,EXECUTING,8356.578000,0.524320,12987.975652,0.000000
Tue May 20 23:22:46 BST 2014,EXECUTING,8740.823000,0.526892,12761.774589,0.000000
Tue May 20 23:32:46 BST 2014,SUSPENDED,9128.021000,0.527037,12575.396826,0.000000
Tue May 20 23:42:46 BST 2014,EXECUTING,9514.280000,0.529629,12351.649871,0.000000
Tue May 20 23:52:46 BST 2014,EXECUTING,9901.904000,0.532232,12129.078825,0.000000
Wed May 21 00:02:46 BST 2014,SUSPENDED,10290.660000,0.532417,11944.325745,0.000000
Wed May 21 00:12:46 BST 2014,EXECUTING,10674.920000,0.534979,11725.495723,0.000000
Wed May 21 00:22:46 BST 2014,EXECUTING,11058.630000,0.537612,11507.312829,0.000000
Wed May 21 00:32:46 BST 2014,EXECUTING,11445.400000,0.537828,11323.599939,0.000000
Wed May 21 00:42:46 BST 2014,SUSPENDED,11830.880000,0.540503,11107.953544,0.000000
Wed May 21 00:52:46 BST 2014,EXECUTING,12217.870000,0.543132,10894.618164,0.000000
Wed May 21 01:02:46 BST 2014,EXECUTING,12605.780000,0.545734,10683.057775,0.000000
Wed May 21 01:12:46 BST 2014,SUSPENDED,12989.590000,0.548440,10471.545863,0.000000
Wed May 21 01:22:46 BST 2014,SUSPENDED,13378.500000,0.551311,10260.469294,0.000000
Wed May 21 01:32:46 BST 2014,EXECUTING,13765.920000,0.554058,10052.662626,0.000000
Wed May 21 01:42:46 BST 2014,EXECUTING,14149.930000,0.559170,9817.932004,0.000000
Wed May 21 01:52:46 BST 2014,SUSPENDED,14538.380000,0.564514,9583.587308,0.000000
Wed May 21 02:02:46 BST 2014,EXECUTING,14925.590000,0.569905,9352.195612,0.000000
Wed May 21 02:12:46 BST 2014,EXECUTING,15312.600000,0.577933,9092.058926,0.000000
Wed May 21 02:22:46 BST 2014,EXECUTING,15700.410000,0.586467,8829.661215,0.000000
Wed May 21 02:32:46 BST 2014,SUSPENDED,16088.330000,0.599473,8518.496266,0.000000
Wed May 21 02:42:46 BST 2014,EXECUTING,16472.820000,0.618921,8130.064350,0.000000
Wed May 21 02:52:46 BST 2014,EXECUTING,16861.070000,0.659468,7456.127630,0.000000
Wed May 21 03:02:46 BST 2014,UNINITIALIZED,0.000000,0.000000,0.000000,17109.970000

It looks like you may have got this problem fixed. I noticed today that they were starting at 1% and appear to be progressing normally to 100%

Thanks for fixing it or at least attempting to.

It looks like you may have got this problem fixed. I noticed today that they were starting at 1% and appear to be progressing normally to 100%

Thanks for fixing it or at least attempting to.

Actually, I haven't changed anything. What you are probably seeing are WUs for a different data set. The 9x271 case is almost complete and work has been issued for 12x262 through 12x269 and 13x80 through 13x261. Whereas 9x271 had 1 congruence vector per WU, these newer cases have many congruence vectors per WU, which tends to average out the inconsistent times. When the 10x270 cases start, you will probably see the old behavior again (10x270 has 1 congruence vector).

It looks like you may have got this problem fixed. I noticed today that they were starting at 1% and appear to be progressing normally to 100%

Thanks for fixing it or at least attempting to.

Actually, I haven't changed anything. What you are probably seeing are WUs for a different data set. The 9x271 case is almost complete and work has been issued for 12x262 through 12x269 and 13x80 through 13x261. Whereas 9x271 had 1 congruence vector per WU, these newer cases have many congruence vectors per WU, which tends to average out the inconsistent times. When the 10x270 cases start, you will probably see the old behavior again (10x270 has 1 congruence vector).

I´m testing some Decic WU´s soon, and look at it.

EDIT: As you said, 10x270 are starting at 0,005%, an than after one second up to ~50%