Estimated run time is way to big

Author	Message
[B@P] Daniel Send message Joined: 8 Sep 17 Posts: 99 Credit: 402,603,726 RAC: 0	Message 8 - Posted: 9 Sep 2017, 14:42:12 UTC BOINC shows that estimated time to completion for new tasks is about half a year. This is way too big, real time for my machine is about one day. Please correct this. ID: 8 · Rating: 0 · rate: / Reply Quote

Natalia Volunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Help desk expert Send message Joined: 11 Aug 17 Posts: 103 Credit: 1,973,929 RAC: 15	Message 11 - Posted: 9 Sep 2017, 16:24:40 UTC - in response to Message 8. BOINC shows that estimated time to completion for new tasks is about half a year. This is way too big, real time for my machine is about one day. Please correct this. Dear Daniel, estimated time like half a year is abnormal. Could you please check if this situation is like the ones suggested in this thread? ID: 11 · Rating: 0 · rate: / Reply Quote

[B@P] Daniel Send message Joined: 8 Sep 17 Posts: 99 Credit: 402,603,726 RAC: 0	Message 14 - Posted: 9 Sep 2017, 17:21:10 UTC - in response to Message 11. BOINC shows that estimated time to completion for new tasks is about half a year. This is way too big, real time for my machine is about one day. Please correct this. Dear Daniel, estimated time like half a year is abnormal. Could you please check if this situation is like the ones suggested in this thread? No, this is different thing. I checked task properties and found following numbers. When you divide 2nd by 1st and change units to days, you will get 178 days. Looks that estimated task size is specified incorrectly on server. Estimated app speed: 3,25 GFLOPs/sec Estimated task size: 50 000 000 GFLOPs ID: 14 · Rating: 0 · rate: / Reply Quote

mmonnin Send message Joined: 8 Sep 17 Posts: 22 Credit: 19,171,868 RAC: 12,035	Message 16 - Posted: 9 Sep 2017, 20:08:29 UTC I agree with Daniel. The original ETA was 164 days. Yes, Days. Even at 92% it still shows 15 days to completion. That is different from reaching 100% and still crunching. That also happened to me. Since the ETA was well past the deadline, BM went into panic mode and it paused other work. This is on a 3570k. ID: 16 · Rating: 0 · rate: / Reply Quote

Conan Send message Joined: 8 Sep 17 Posts: 44 Credit: 11,209,448 RAC: 3,511	Message 19 - Posted: 10 Sep 2017, 0:14:38 UTC My first WU on my AMD computers was 4,400+ hours estimated run time, but came down fairly quickly as it crunched. The second one downloaded showed about 3,000 hours. So the time is coming down as BOINC get to know how long they run. I know this can upset BM, however given time BM will get over it, you just have to wait for BM to catch up. Conan ID: 19 · Rating: 0 · rate: / Reply Quote

[B@P] Daniel Send message Joined: 8 Sep 17 Posts: 99 Credit: 402,603,726 RAC: 0	Message 20 - Posted: 10 Sep 2017, 10:19:54 UTC Last modified: 10 Sep 2017, 10:26:46 UTC I know that BOINC will eventually learn how long tasks are really are, and start showing correct time for given PC. But initial runtime estimate provided by server also should be close to real runtime. Looks that estimated task size provided by server should be around 280k GFLOPs, this will translate to ~1day on my machine, what is close enough to real runtime. ID: 20 · Rating: 0 · rate: / Reply Quote

Natalia Volunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Help desk expert Send message Joined: 11 Aug 17 Posts: 103 Credit: 1,973,929 RAC: 15	Message 22 - Posted: 10 Sep 2017, 15:13:35 UTC Dear all, thanks for comments. I will change the WU template settings in the following day. ID: 22 · Rating: 0 · rate: / Reply Quote