Zombie67 does have quite a few invalid cpu-only tasks (~33 - 50% after a quick look). After finishing some FGRP5 I'll run some BRP4A cpu-only tasks for a while and see if I get similar results.
I'm still running the 23.5.0 kernel (Sonoma 14.5) and I think a lot of the mac crunchers have recently upgraded to 23.6.0 which is probably Sonoma 14.6.0 or 14.6.1. So far I haven't had a ton of invalid gpu tasks again, which was the case before upgrading to 23.5.0.
I am not seeing *any* valid CPU tasks for me. Telling the difference between CPU and GPU tasks is not easy, as the application name is almost, but not quite the same.
CPU: Binary Radio Pulsar Search (Arecibo,GBT,A) v2.08 arm64-apple-darwin
GPU: Binary Radio Pulsar Search (Arecibo,GBT,A) v2.08 () arm64-apple-darwin
The easiest way to tell the difference is the run time. On the GPU, it takes about 350 seconds. On the CPU, it takes about 1615 seconds. FWIW, it limit the number of CPU tasks running at a time to 4. That way the tasks are using only the p-cores.
Yep, for all samples I had a look at your result was the only CPU result. Your wingmen always produced GPU results. That's pretty striking. I didn't check the kernel versions used this time.
Hey zombie67 here is one of many valid cpu-only tasks from your tasks page: workunit 827147400 . This one happens to have been validated by another cpu-only task. And this one was validated by a gpu task: workunit 827147238.
The tasks page has a menu across the top where you can pick the status type (all, in progress, pending, valid, invalid, error). And sorting them by cpu time is how I find the cpu-only ones, which take much longer to run. So if you pick a type (valid or invalid) and sort by cpu time (twice to get it to list from highest to lowest), you should find the cpu-only tasks starting on page 1. I bookmarked a sorted page from my account to be able to get to it quickly.
I disabled the BRP4A Apple Silicon CPU version for the time being. It was mainly used to test validation against our GPU versions and that clearly doesn't yet work reliably. Since we won't release updates in the next few weeks, it doesn't make sense to waste CPU cycles on it. Also, since the GPU versions are available those are a better use on that platform while we still have other apps like FGRP for the CPUs available.
We'll get back to it as soon as time and resources allow.
Zombie67 does have quite a
)
Zombie67 does have quite a few invalid cpu-only tasks (~33 - 50% after a quick look). After finishing some FGRP5 I'll run some BRP4A cpu-only tasks for a while and see if I get similar results.
I'm still running the 23.5.0 kernel (Sonoma 14.5) and I think a lot of the mac crunchers have recently upgraded to 23.6.0 which is probably Sonoma 14.6.0 or 14.6.1. So far I haven't had a ton of invalid gpu tasks again, which was the case before upgrading to 23.5.0.
I am not seeing *any* valid
)
I am not seeing *any* valid CPU tasks for me. Telling the difference between CPU and GPU tasks is not easy, as the application name is almost, but not quite the same.
CPU: Binary Radio Pulsar Search (Arecibo,GBT,A) v2.08 arm64-apple-darwin
GPU: Binary Radio Pulsar Search (Arecibo,GBT,A) v2.08 () arm64-apple-darwin
The easiest way to tell the difference is the run time. On the GPU, it takes about 350 seconds. On the CPU, it takes about 1615 seconds. FWIW, it limit the number of CPU tasks running at a time to 4. That way the tasks are using only the p-cores.
Reno, NV Team: SETI.USA
Yep, all samples I had a look
)
Yep, for all samples I had a look at your result was the only CPU result. Your wingmen always produced GPU results. That's pretty striking. I didn't check the kernel versions used this time.
Einstein@Home Project
Hey zombie67 here is one of
)
Hey zombie67 here is one of many valid cpu-only tasks from your tasks page: workunit 827147400 . This one happens to have been validated by another cpu-only task. And this one was validated by a gpu task: workunit 827147238.
The tasks page has a menu across the top where you can pick the status type (all, in progress, pending, valid, invalid, error). And sorting them by cpu time is how I find the cpu-only ones, which take much longer to run. So if you pick a type (valid or invalid) and sort by cpu time (twice to get it to list from highest to lowest), you should find the cpu-only tasks starting on page 1. I bookmarked a sorted page from my account to be able to get to it quickly.
I disabled the BRP4A Apple
)
I disabled the BRP4A Apple Silicon CPU version for the time being. It was mainly used to test validation against our GPU versions and that clearly doesn't yet work reliably. Since we won't release updates in the next few weeks, it doesn't make sense to waste CPU cycles on it. Also, since the GPU versions are available those are a better use on that platform while we still have other apps like FGRP for the CPUs available.
We'll get back to it as soon as time and resources allow.
Thanks
Einstein@Home Project