Thanks to the help of Christophe Choquet we now do have an efficient GPU version of the Gamma-ray pulsar search application. This is meant to replace the Radio-Pulsar search as our main GPU application when we run out of Arecibo data to process. We have been testing this application versions on Albert@Home for a couple of weeks. The Windows build still doesn't work, and we're working on that. However, we are releasing the versions for Linux and OSX now on Einstein@home for Beta test to get a wider test bed and get an impression how it compares to the CPU version.
BM
Copyright © 2024 Einstein@Home. All rights reserved.
I suppose there's no way of
)
I suppose there's no way of running those without getting CPU tasks too? I'd like to avoid that, especially v1.05.
Observations: the percentage
)
Observations:
the percentage clock starts ticking (after a while) at about 2%; the WU is finished at below 6%, the counter then jumps to 100%. These figures differ when you run two GPU WUs concurrently (finish at around 9%). Still different figures applied with these apps at Albert: single GPU WU finished at about 12%
floyd_7 wrote:I suppose
)
You can just select the Binary Radio Pulsar Search (Parkes PMPS XT) application, since it doesn't have any tasks available anyway. And then select "Run test applications" of course.
It works for me, other than the fact that they were all erroring out after 10 seconds when they were running on my two GTX 960s running under Ubuntu 16.10. However, I now just have one task left running on one card, and it is doing OK after 7 minutes. So it seems that the problem is only when running on two cards.
Jim1348 wrote:And then select
)
If I'm not mistaken that enables all test applications no matter what. But I've disabled it again anyway since BOINC seriously overfetched. With an estimated run time of 2:08 hours and a 2 days cache I got 18 tasks every minute.
(Meant to write this as an edit to my previous post but then somehow got "no permission")
I'll try that later today. Need to be off now ...
I see this Einstein-version
)
I see this Einstein-version takes about 0,54x time compared to Albert-version, even though the estimated computation size was 105,000 GFLOP's for both kind of tasks. This was observed on a host with AMD/ATI card, Linux Mint 18, two tasks running parallel on both cases.
edit: Same observation also with a host with Nvidia card.
I've got some a bit strange
)
I've got some a bit strange WUs for windows machine with name:
Gamma Ray pulsar binary search #1 onGPUs 1.05(FGRPSSE)
However, they are purely CPU.
Same strange behavior here. I
)
Same strange behavior here. I got Gamma-ray pulsar binary search #1 on GPUs on windows host (while Bernd says it not ready for Win platform).
https://einsteinathome.org/task/593239043
And more interesting - this host not even have any GPU available to BOINC. But WU still running(on CPU of course) and looks fine so far:
Mad_Max wrote:Same strange
)
I believe a logical explanation for CPU version (FGRPSSE) also being offered under this application title could be that CPU versions help to gather further information for development. So they can compare results between CPU and GPU and fine-tune these applications etc. Those CPU versions for every platform existed first. They were the original 'form' of this thing. GPU versions saw the sunlight only later (except for the third giant... Windows platform... not yet).
Sorry for the
)
Sorry for the misunderstanding - currently we have CPU versions of FGRPB1G, too, to validate the GPU results.
BM
Mine are all set to not get
)
Mine are all set to not get any of these and yet I did get over 30 of them on the first one I check.
Didn't help my VB tasks at all