Inaccurate estimation of times Universe@Home

Author	Message
Marcin Send message Joined: 18 Nov 15 Posts: 2 Credit: 10,967 RAC: 0	Message 760 - Posted: 18 Nov 2015, 18:10:11 UTC Last modified: 18 Nov 2015, 18:21:56 UTC I see the estimated time is completely inaccurate. ULX 0.01: estimated - 312:11:23, actual time - 1:34:39 BHspin 0.03: estimated 00:31:59, actual time - 1:58:12. Ether my host is a crushing monster for ULX and a lazy snail for BHspin or something is wrong with the time estimation. :) ID: 760 · Rating: 0 · rate: / Reply Quote

Krzysztof Piszczek - wspieram ... Project administrator Project developer Project tester Send message Joined: 4 Feb 15 Posts: 847 Credit: 144,180,465 RAC: 0	Message 761 - Posted: 18 Nov 2015, 19:24:35 UTC - in response to Message 760. I see the estimated time is completely inaccurate. ULX 0.01: estimated - 312:11:23, actual time - 1:34:39 BHspin 0.03: estimated 00:31:59, actual time - 1:58:12. Ether my host is a crushing monster for ULX and a lazy snail for BHspin or something is wrong with the time estimation. :) It's something wrong with... manager (I suspect)... I have four hosts with modern CPU's (E3-1230v2 Windows, E5 2x6 core - Debian, i7 950 - Debian, E3-1225 Debian). All of the hosts shows for ULX expected time from 0s to... 22'000... days... For the same rsc_fpops_est value... I have made loads of tests with rsc_fpops_est variable and non of them work correctly for all my hosts... If you have any idea how to set it correctly I will be appreciate if you share it with me ;) Krzysztof 'krzyszp' Piszczek Member of Radioactive@Home team My Patreon profile Universe@Home on YT ID: 761 · Rating: 0 · rate: / Reply Quote