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.

however, it will really speed up 10^21 and allow getting to 10^22 much faster.

Here`s a strange 1, Amicable was running fine but then reinstalled win 10 (getting rid of bloated system, not changed anything in bios etc) and now getting "waiting on memory" message in Boinc status. Memory at 7% in task manager. Only way to get it running is to abort that task :( . Anybody any idea what i have done or failed to install yet?

Edit: ah think I found it, in Disk and Memory it was set to just use 50% when computer in use lol, woops

while 10^20 is finished by those who run GPU?

It is no new thread !!

Amicalble Numbers slow down about 30-40 % an THIS is the thread "Amicable Numbers slow down" !!!!

Does anybody know a reason for the slow down ??

I7-5960X is one of the reference CPUs here: https://sech.me/boinc/Amicable/gpu_list.php. Those numbers might be a bit outdated because they were measured for the search up to 2⁶⁴. I'll update them in a few days.

Feels like a new thread, mate. This is a little spammy and out place in this thread imo. :)

I am aware that tasks are a lot slower now but is anybody else having an issue receiving GPU work for Nvidia?

I am aware that tasks are a lot slower now but is anybody else having an issue receiving GPU work for Nvidia?

Good Day. Created the app_config.xml file as described, saved it as an xml file (using Word), verified name/extension was correct, placed in the amicable sub-directory of the Boinc projects parent directory, had the Boinc manager read the config file, and received this notice/message:

Missing <app_config> in app_config.xml

Also checked and saw only once instance of amicable tasks running, not two as I wanted, and verified utilization was still in the 65%-75% range

Any suggestions?

Thank you for any assistance or insights offered.

<app_config>
   <app>
      <name>amicable_10_20</name>
            <gpu_versions>
          <gpu_usage>.5</gpu_usage>
          <cpu_usage>1</cpu_usage>
      </gpu_versions>
    </app>
</app_config>

The GTX 1080 ti and RTX 2080 ti both have 11GB RAM, but only 4GB shows up in BOINC data ;)

Thank you for sharing this. I am running 2 tasks on my (aging!) 7970 as GPU utilization had dropped to ~93%.

Matt I had a look at your tasks. In terms of run-time am I correct in saying that you are returning 2 results roughly every 45 minutes on your 7970?

That is correct. GPU is a 7970 @ 985Mhz/1425mhz

Hi, for exemple i run now six task , also i try seven but system was bit laggy .
six task 0.16 about 9700mb average gpu ram usage totall..
but today if you have more gpu ram on your gf. card ,you can run more tasks

Thank you for sharing this. I am running 2 tasks on my (aging!) 7970 as GPU utilization had dropped to ~93%.

At the bottom of the Server Status, it shows the the runtime of the last 100 tasks --- 1.50 hours average, 0.07 hours minimum and 81.97 hours maximum.

Can the runtime be classified by CPU vs. GPU?

Can the runtime be classified even further, such as:
- CPU with 2 CPUs, CPU with 3 CPUs, CPU with 4 CPUs, etc.
- AMD/ATI GPU with 2 CPUs, AMD/ATI GPU with 3 CPUs, etc.
- NVIDIA GPU with 2 CPUs, NVIDIA GPU with 3 CPUs, etc.

I checked "good" and "bad" WUs in profiler, and got this for "good" WU:

InitialCheck128() = 22.36% of execution time
CheckPairInternal() = 72.05% of execution time

and this for "bad" WU:

InitialCheck128() = 83.53% of execution time
CheckPairInternal() = 15.37% of execution time

It looks like some number ranges require much more time to switch from slow 128-bit trial divisions to fast 64-bit code. There is nothing wrong with the code itself, it's just my assumption that all "large prime" ranges are the same turned out to be wrong. What's interesting is that OpenCL version doesn't suffer from this problem - probably because they're 32-bit natively and difference between 64 and 128-bit code is much smaller there.

OK. I've had enough! In the past, and for several months, I was processing 14-15 CPU work units per day at 6836.19 credits per unit. Then, around the 20 Oct, my performance dropped to 6-7 units per day. Then, around 19 Nov, my performance jumped back to 14-15 units per day. Then, a couple of days later, it dropped back to 5-6 units per day. Then, about Dec 6, it jumped back to 14-15 units per day for a few hours, then drop down to 1-2 units per day where it has remained. My repeated requested for assistance have come and gone and I am no longer going to donate my computer time and electricity for 1-2 units per day at 6836.19 credits per unit! Since all of this has occurred with no changes to my system hardware or software, I have to wonder if Amicable Numbers is suffering hacker attacks from idiots that are trying to get rich quick by gaming the crypto coin systems and creating issues for everyone else? But until I get word this issue is resolved, I am forced to abandon this project.

We caught up more than a month ago, it's all new work now.

Good news: I was able to narrow down the invalid work units range to only last 9 days after further analysis of this bug.

I7-5960X is one of the reference CPUs here: https://sech.me/boinc/Amicable/gpu_list.php. Those numbers might be a bit outdated because they were measured for the search up to 2⁶⁴. I'll update them in a few days.

I am curious to know if anyone knows how many more tasks there are for 2_64? Before it is finished

Approx. 83,000 work units left, or 4 weeks more work at current speed.

P.S. Server status page