GPU version fix

Author	Message
Sergei Chernykh Project administrator Project developer Send message Joined: 5 Jan 17 Posts: 534 Credit: 72,451,573 RAC: 0	Message 779 - Posted: 27 Mar 2018, 17:45:25 UTC Last modified: 27 Mar 2018, 18:56:15 UTC There was a serious bug in GPU version: https://github.com/SChernykh/Amicable/commit/3470ed855d244100f37b0b7ab4c912d2b9365a93 Unfortunately, it skipped some numbers in an unpredictable way for "large primes" work units for the last ~~20 days~~ 9 days. I'll have to reissue all such work units to cover everything missed. The GPU versions for all platforms are already updated. Sorry for the mess, but it's good that the bug is fixed relatively early, because it was hard to notice. ID: 779 · Rating: 0 · rate: / Reply Quote

Kellen Send message Joined: 14 Nov 17 Posts: 70 Credit: 1,000,005,236 RAC: 0	Message 780 - Posted: 27 Mar 2018, 18:13:12 UTC - in response to Message 779. Well, I'm glad this was caught early! 20 days is a lot better than 200 days :) Is this bug the reason for the semi-random work unit runtimes lately? ID: 780 · Rating: 0 · rate: / Reply Quote

Sergei Chernykh Project administrator Project developer Send message Joined: 5 Jan 17 Posts: 534 Credit: 72,451,573 RAC: 0	Message 781 - Posted: 27 Mar 2018, 18:48:44 UTC - in response to Message 780. Is this bug the reason for the semi-random work unit runtimes lately? Yes, it was running random percentage of a work unit instead of full 100%. ID: 781 · Rating: 0 · rate: / Reply Quote

Sergei Chernykh Project administrator Project developer Send message Joined: 5 Jan 17 Posts: 534 Credit: 72,451,573 RAC: 0	Message 782 - Posted: 27 Mar 2018, 18:54:36 UTC Last modified: 27 Mar 2018, 19:00:48 UTC Good news: I was able to narrow down the invalid work units range to only last 9 days after further analysis of this bug. ID: 782 · Rating: 0 · rate: / Reply Quote

Speedy Send message Joined: 6 Jun 17 Posts: 83 Credit: 201,069,888 RAC: 14,238	Message 826 - Posted: 7 May 2018, 23:20:01 UTC - in response to Message 782. Good news: I was able to narrow down the invalid work units range to only last 9 days after further analysis of this bug. This is great news. Is there a way to tell if we are running old work units or have we caught up with processing old work? ID: 826 · Rating: 0 · rate: / Reply Quote

Sergei Chernykh Project administrator Project developer Send message Joined: 5 Jan 17 Posts: 534 Credit: 72,451,573 RAC: 0	Message 827 - Posted: 8 May 2018, 5:17:36 UTC - in response to Message 826. We caught up more than a month ago, it's all new work now. ID: 827 · Rating: 0 · rate: / Reply Quote

Speedy Send message Joined: 6 Jun 17 Posts: 83 Credit: 201,069,888 RAC: 14,238	Message 828 - Posted: 8 May 2018, 5:32:35 UTC - in response to Message 827. We caught up more than a month ago, it's all new work now. So we did pleased to hear that you got all the results you needed rechecked ID: 828 · Rating: 0 · rate: / Reply Quote

Duce-HK Send message Joined: 12 Feb 17 Posts: 5 Credit: 13,360,228 RAC: 0	Message 1103 - Posted: 13 Mar 2019, 6:41:20 UTC Last modified: 13 Mar 2019, 6:43:49 UTC Почему у меня три параллельных здадания считаются на opencl_nvidia? В BOINC_data\projects\sech.me_boinc_Amicable нет каких либо .XML конфигов, ибо до запуска я переместил config в архив На сайте в настройках ничего похожего также не нашел. Вторая трабла это низкая загрузка ядра GPU. Назначил affinity на первые 4 ядра CPU, чтобы шел буст - без толку. Попробую перезапустить на макс. core_weight... ID: 1103 · Rating: 0 · rate: / Reply Quote

Duce-HK Send message Joined: 12 Feb 17 Posts: 5 Credit: 13,360,228 RAC: 0	Message 1104 - Posted: 13 Mar 2019, 10:21:13 UTC Да И какие дрова советуете для Amicable? может в 373.06 дело ID: 1104 · Rating: 0 · rate: / Reply Quote