51)
Message boards :
Random stuff :
Amicable numbers divisible neither 2 nor 3.
(Message 1330)
Posted 20 Dec 2019 by Sergei Chernykh Post: Yes, and there is a lot of them. Smallest examples: X44 Walker&Einstein 2001 5480828320492525=5^2*7^2*11*13*19*31*17*23*103*1319 5786392931193875=5^3*7*11*13*19*31*37*43*61*809 X43 Chernykh 2015 445953248528881275=3^2*5^2*7*13*19*37*43*73*439*22483 659008669204392325=5^2*7*13*19*37*73*571*1693*5839 |
52)
Message boards :
Number crunching :
GPU version requirements for the search up to 10^20
(Message 1326)
Posted 13 Dec 2019 by Sergei Chernykh Post: Because GPU version has to store all prime numbers < 1011 and it can't use compact bit array as CPU version does. |
53)
Message boards :
Bug tracker :
badly WU?
(Message 1317)
Posted 5 Dec 2019 by Sergei Chernykh Post: Yes, looks like it. I'll have to split it into smaller WUs. |
54)
Message boards :
Number crunching :
GPU version: kernel size tuning and less UI lags
(Message 1314)
Posted 2 Dec 2019 by Sergei Chernykh Post: Yes, I'll adjust credit for these tasks. |
55)
Message boards :
News :
The search up to 10^21
(Message 1308)
Posted 16 Nov 2019 by Sergei Chernykh Post: It should work on 1GB GPUs, but I haven't tested it. You'll probably need to reduce kernel size to the minimum. |
56)
Message boards :
Number crunching :
GPU version: kernel size tuning and less UI lags
(Message 1305)
Posted 14 Nov 2019 by Sergei Chernykh Post: Probably because task size is 68*1012, 100 times more than usual. Task generator was definitely not perfect. |
57)
Message boards :
Number crunching :
GPU version: kernel size tuning and less UI lags
(Message 1303)
Posted 14 Nov 2019 by Sergei Chernykh Post: It doesn't get stuck: https://sech.me/boinc/Amicable/workunit.php?wuid=11804634 - another GPU finished it, you just had to wait a bit more. |
58)
Message boards :
Number crunching :
GPU version: kernel size tuning and less UI lags
(Message 1296)
Posted 10 Nov 2019 by Sergei Chernykh Post: It's not GPU lags in your case, you jut need more than 8 GB system memory to run GPU tasks. Your notebook is swapping and everything starts to lag. |
59)
Message boards :
Number crunching :
Missing Computers
(Message 1289)
Posted 2 Nov 2019 by Sergei Chernykh Post: If they weren't active for more than 90 days then they were deleted automatically. |
60)
Message boards :
News :
The search up to 10^20
(Message 1286)
Posted 1 Nov 2019 by Sergei Chernykh Post: Yes, it's complete. All previously known amicable numbers were found by the search (which was expected), and many new amicable numbers were found. |
61)
Message boards :
News :
The search up to 10^21
(Message 1281)
Posted 30 Oct 2019 by Sergei Chernykh Post: No, old tasks will just run out soon. You might abort tasks that use v3.01 GPU application, but it's safe to just leave them running without pausing/resuming. |
62)
Message boards :
News :
The search up to 10^21
(Message 1278)
Posted 30 Oct 2019 by Sergei Chernykh Post: Attention! There was a bug in GPU version for 1021 search that caused invalid results after resuming from checkpoint in some cases, so I had to fix it and restart the search from the beginning. |
63)
Message boards :
Bug tracker :
Constant Computation errors
(Message 1276)
Posted 29 Oct 2019 by Sergei Chernykh Post: Error -6 is CL_OUT_OF_HOST_MEMORY. Increase swap file size. You need 8.5 GB per each running GPU task. |
64)
Message boards :
Number crunching :
Problem with valid wus count on All Tasks page?
(Message 1274)
Posted 29 Oct 2019 by Sergei Chernykh Post: Yes, there are usually many amicable numbers found per task now because 1021 search started with the most fruitful ranges. |
65)
Message boards :
Number crunching :
Prime Numbers
(Message 1271)
Posted 28 Oct 2019 by Sergei Chernykh Post: If it takes 1 hour to compute prime table, you're doing something seriously wrong. It usually takes no more than 1 minute and is done on a single CPU core, then it starts using all CPU cores, so it's easy to notice how much time it takes. |
66)
Message boards :
News :
The search up to 10^20
(Message 1265)
Posted 27 Oct 2019 by Sergei Chernykh Post: I think it's different tasks every time. Some 1020 tasks time out after 3 days, new tasks are created, sent and it repeats. P.S. I was wrong, these tasks were stuck. |
67)
Message boards :
Number crunching :
Prime Numbers
(Message 1263)
Posted 26 Oct 2019 by Sergei Chernykh Post: I prefer not to store prime table on disc as it can get corrupt/overwritten either occasionally or maliciously. |
68)
Message boards :
News :
The search up to 10^20
(Message 1250)
Posted 25 Oct 2019 by Sergei Chernykh Post: I repeat: these 8 GB can mostly go into swap file without hurting performance. You don't need physical 8 GB RAM per task, OS will swap out unused parts of memory if you have not enough RAM. |
69)
Message boards :
News :
The search up to 10^21
(Message 1246)
Posted 25 Oct 2019 by Sergei Chernykh Post: The search up to 1021 has started! Over 50,000 new amicable pairs have been found in the first few days. Due to the huge size of search space, first stage of the search will only look for all amicable pairs where smaller number is of the form 3N*...*p where N > 0 and p < 1011. I expect that this will find 2-3 million new amicable pairs in a year or so. Note that system memory requirements are higher now because all prime numbers < 1011 need to be stored in memory for the search. |
70)
Message boards :
News :
The search up to 10^20
(Message 1245)
Posted 25 Oct 2019 by Sergei Chernykh Post: It doesn't require 8 GB all the time, you could increase your swap file and be fine with ~1.5 GB physical RAM per task. Now I'm not sure how to make BOINC run with more memory used than available. |
71)
Message boards :
News :
The search up to 10^20
(Message 1235)
Posted 23 Oct 2019 by Sergei Chernykh Post: Running GPU on 1021 is fine now. Even 1 task per GPU will get you almost 100% GPU load (except for when task starts), 2 tasks per GPU will guarantee you 100% load all the time. CPU usage of GPU tasks is low, so you can run CPU tasks on the same machine. |
72)
Message boards :
News :
The search up to 10^20
(Message 1233)
Posted 21 Oct 2019 by Sergei Chernykh Post: When can we expect more of the 10^21 tasks? As soon as 10^20 tasks run out or a bit before that for a smooth transition. |
73)
Message boards :
News :
The search up to 10^20
(Message 1230)
Posted 21 Oct 2019 by Sergei Chernykh Post: I pushed search limits for 1021 a bit further into large primes territory, so memory requirements are higher now (all primes up to 1011 are checked). CPU version requires 2.85 GB of system memory. GPU version fits in 1 GB on GPU, but requires 8 GB of system memory after refactoring. |
74)
Message boards :
News :
The search up to 10^20
(Message 1227)
Posted 19 Oct 2019 by Sergei Chernykh Post: There's literally only 310 such tasks for the entire search. lpp stands for "largest prime power" and when it's 2 or 3, you only get to check sqrt(N) or cuberoot(N) numbers. So we shouldn't bother with them at all. But they are also good for testing and finding bugs, so I added them for the beta test. |
75)
Message boards :
News :
The search up to 10^20
(Message 1224)
Posted 19 Oct 2019 by Sergei Chernykh Post: I've checked it. Tasks with "/lpp" in command line iterate over many more ranges than normal tasks and many of these ranges end up with 0 numbers for GPU. This is why it uses only CPU in the end and is at 100% - it counts only how many numbers to check on GPU. |
76)
Message boards :
News :
The search up to 10^20
(Message 1221)
Posted 19 Oct 2019 by Sergei Chernykh Post: Probably task_size parameter was calculated incorrectly, so it can count to 100% before the actual work is done. I'll check this task. |
77)
Message boards :
News :
The search up to 10^20
(Message 1219)
Posted 19 Oct 2019 by Sergei Chernykh Post: And there is a bug in OpenCL version: https://sech.me/boinc/Amicable/workunit.php?wuid=11571043 I reproduced it locally. Kernel size = 23 skips some numbers, kernel size = 21 works fine. But other work units might behave differently, i.e. kernel size 21 will skip numbers. P.S. Fixed in version 3.01. It was a bug introduced during refactoring, so 1020 search wasn't affected. |
78)
Message boards :
News :
The search up to 10^20
(Message 1218)
Posted 18 Oct 2019 by Sergei Chernykh Post: The work units with "/lpp" in command line are special ones, they're more hard on CPU, so 100% GPU load is not guaranteed. But there is only a few of them. And yes, new pairs: https://sech.me/ap/log/2019/2019-10-19/VOLUNTEERS%40BOINC.txt |
79)
Message boards :
News :
The search up to 10^20
(Message 1216)
Posted 18 Oct 2019 by Sergei Chernykh Post: If there is some task that doesn't finish on GPU, give me a link to it and I'll check it. And I see that there are already some new pairs found. |
80)
Message boards :
News :
The search up to 10^20
(Message 1211)
Posted 18 Oct 2019 by Sergei Chernykh Post: I've added applications for 1021, set it as a beta for now and added 1000 first work units for testing. We'll see how it goes. P.S. But all amicable pairs found during this test will be counted as usual. |
81)
Message boards :
News :
The search up to 10^20
(Message 1209)
Posted 17 Oct 2019 by Sergei Chernykh Post: Right now it takes 5-10 seconds to generate a task and it's a sequential algorithm - every next range must start where the previous range ended, and I have no way to determine range borders until I run a quick emulation of the search. I can split it into several parallel processes however - for example, N processes for ranges starting with 3N, but each process is also taking 8.5 GB of memory for storing prime numbers. I'll see if I can share these 8.5 GB between processes and run task generators on all 16 threads. P.S. I think that even now I'm able to generate tasks faster than the crunchers will be able to consume them, so it's not really a problem. |
82)
Message boards :
News :
The search up to 10^20
(Message 1207)
Posted 16 Oct 2019 by Sergei Chernykh Post: Yes, it was intentional. I need a bit more time to generate work units for 1021. Everything is ready, but task generation is sloooow.... I hope I'll be able to provide around 10,000 WUs next week when the new search starts. |
83)
Message boards :
News :
The search up to 10^20
(Message 1204)
Posted 14 Oct 2019 by Sergei Chernykh Post: Yes, I'll prepare CPU and GPU applications for 10^21 this week. GPU version will need a bit of refactoring because as of now it requires more than 8 GB of GPU memory for 10^21. I'll have to split workunits into 8 stages (1 GB each) for GPU. |
84)
Message boards :
Number crunching :
A few questions regarding my hardware.
(Message 1189)
Posted 29 Aug 2019 by Sergei Chernykh Post: I plan to add 1021 app before October, I just haven't figured out the optimal way to run 1021 search yet. I need to go through current search results and find the most juicy subsets of tasks to run first. I think something like "searching through all odd numbers with largest prime factor < 1011" can yield over a million new pairs in a year or two. |
85)
Message boards :
Number crunching :
Question About The Ranges Tested Multiple Times
(Message 1174)
Posted 19 Jun 2019 by Sergei Chernykh Post: Yes, it should move faster now, maybe 1020 will even finish before the end of this summer. |
86)
Message boards :
Number crunching :
Question About The Ranges Tested Multiple Times
(Message 1171)
Posted 19 Jun 2019 by Sergei Chernykh Post: Yes, it sends smaller batches to CharityEngine's computers because they're mostly unstable/unreliable. But it shouldn't send repeating tasks, I'll look into it. Edit: yes, there was a bug in the code. I forgot to move the batch from "unsent" to "sent" folder in this case. Thanks for noticing! But anyway, it didn't go completely to waste because it provided some more redundancy in the search up to this point. |
87)
Message boards :
Number crunching :
Maximum Prime Size for Large Prime Workunits
(Message 1146)
Posted 24 May 2019 by Sergei Chernykh Post: I've just checked "unsent WUs" directory on the server: there are 705,478 WU left right now. |
88)
Message boards :
Getting started :
Unable to add admin
(Message 1143)
Posted 23 May 2019 by Sergei Chernykh Post: Where exactly do you get this error? |
89)
Message boards :
Number crunching :
Maximum Prime Size for Large Prime Workunits
(Message 1137)
Posted 19 May 2019 by Sergei Chernykh Post: The largest prime will be 5E18 (1E20 / 20) because numbers of the form N*P where N < 20 and P is prime can't be amicable. |
90)
Message boards :
News :
GPU version bugfix release
(Message 1126)
Posted 8 Apr 2019 by Sergei Chernykh Post: GPU version is limited by CPU now, so it's not correct to compare two powerful GPUs here. You're basically comparing CPUs. |
91)
Message boards :
News :
GPU version bugfix release
(Message 1122)
Posted 8 Apr 2019 by Sergei Chernykh Post: GPU versions for all platforms were updated to fix "Error -58" computation error when resuming stopped task. |
92)
Message boards :
Bug tracker :
Computation Error Upon Suspension and Resumption of GPU WU
(Message 1121)
Posted 8 Apr 2019 by Sergei Chernykh Post: Yes, I fixed it a few minutes ago: https://github.com/SChernykh/Amicable/commit/806085804dc51e48aef2527cd18861ad3a986bc0 I'll update GPU versions today. |
93)
Message boards :
Number crunching :
Computation error
(Message 1119)
Posted 8 Apr 2019 by Sergei Chernykh Post: It looks like I fixed this error: https://github.com/SChernykh/Amicable/commit/806085804dc51e48aef2527cd18861ad3a986bc0 I'll test it some more and update GPU versions today. |
94)
Message boards :
Number crunching :
Computation error
(Message 1110)
Posted 1 Apr 2019 by Sergei Chernykh Post: I don't really know what causes error -58 (CL_INVALID_EVENT). It's triggered at this line: https://github.com/SChernykh/Amicable/blob/boinc-opencl-version-128-bit/Amicable/OpenCL.cpp#L1017 - but it's always set properly in the preceding call to clEnqueueNDRangeKernel on the last iteration of "for" loop. My guess is that OpenCL driver runs out of resources occasionally. |
95)
Message boards :
Number crunching :
Computation error
(Message 1099)
Posted 26 Feb 2019 by Sergei Chernykh Post: clEnqueueWriteBuffer returned error -5 This is CL_OUT_OF_RESOURCES error. Try to reduce kernel size in computing preferences: https://sech.me/boinc/Amicable/prefs.php?subset=project |
96)
Message boards :
Number crunching :
Computers list is gone?
(Message 1096)
Posted 22 Feb 2019 by Sergei Chernykh Post: You didn't lose credit, it's saved separately in your user account. |
97)
Message boards :
Number crunching :
GPU Utilization
(Message 1086)
Posted 17 Feb 2019 by Sergei Chernykh Post: Reduce kernel size, run as many WUs per GPU as possible. 8 WUs per GPU should be good enough to load it. |
98)
Message boards :
Number crunching :
Computing Preferences
(Message 1068)
Posted 21 Jan 2019 by Sergei Chernykh Post: I changed nothing server-side recently. Option to not use CPUs should be available on preferences page: https://sech.me/boinc/Amicable/prefs.php?subset=project |
99)
Message boards :
Random stuff :
Project Status Page
(Message 1066)
Posted 21 Jan 2019 by Sergei Chernykh Post: Both CPUs are still in that list. 15 Reference CPU: Intel Core i7-5960X (8 cores, 16 threads, 3.0 - 3.5 GHz) 1.236 2,537.0 |
100)
Message boards :
Number crunching :
Why are the RTX Graphics Cards now really Poor at running this Project.
(Message 1063)
Posted 19 Jan 2019 by Sergei Chernykh Post: Why are the tasks not just ran on the CPUs? Because they are GPU tasks? The actual search is still done on GPU, it just needs a list of prime numbers in given interval to proceed, and this is done on CPU. |
©2023 Sergei Chernykh