On GPUs these tasks run way too short (down to a minute), this would stress our servers as well as e.g. your download rate too much. No, CPU only.
BM
So if the runtime for these WUs is too short, may be it will be good idea to crunch them inside without sending out to the world stressing servers and freeing up our CPUs for Gamma-Ray pulsar search?
P.S. Oh, I found an answer myself. It is a rather big bundle of WUs that cannot be crunched on ATLAS only even with it's new GPUs.
Ok.
Then comes another question: why not to use WU packs like it was sometimes ago with BRP?
why not to use WU packs like it was sometimes ago with BRP?
Actually the BRP5 WUs already are "bundles" of 3, or recently, 2 micro-tasks.
As for BRP4 since yesterday I'm already working on setting up a BRP4 GPU App to help us get through the new Arecibo data. This will use bundles of 16 or 32 BRP4 tasks.
As for BRP4 since yesterday I'm already working on setting up a BRP4 GPU App to help us get through the new Arecibo data. This will use bundles of 16 or 32 BRP4 tasks.
When the BRp4 tasks with this new set up begin to role out, let us know.
As for BRP4 since yesterday I'm already working on setting up a BRP4 GPU App to help us get through the new Arecibo data. This will use bundles of 16 or 32 BRP4 tasks.
Hi Bernd,
Do you plan to add GPU App selection to project preferences so that we may control which GPU apps run on our hosts? Without it monitoring and keeping tabs on host performance will be even more of a nightmare...
As for BRP4 since yesterday I'm already working on setting up a BRP4 GPU App to help us get through the new Arecibo data. This will use bundles of 16 or 32 BRP4 tasks.
As for BRP4 since yesterday I'm already working on setting up a BRP4 GPU App to help us get through the new Arecibo data. This will use bundles of 16 or 32 BRP4 tasks.
Any update on that?
We already sent out 2/3 of the new data to the CPUs last week. I guess by the time we have the GPU App set up there will be not much data left to process.
Binary Radio Pulsar Search (Arecibo): means CPU only
Binary Radio Pulsar Search (Perseus Arm Survey): means GPU only
Binary Radio Pulsar Search (Arecibo, GPU): is a bit ambiguous.
Does (Arecibo, GPU) mean CPU + GPU or does it mean GPU only?
i currently have a host that is set to crunch both Arecibo and Perseus Arm Survey BRP tasks, but on GPU only...and so my E@H preferences currently are as follows:
Quote:
Binary Radio Pulsar Search (Arecibo): yes
Binary Radio Pulsar Search (Perseus Arm Survey): yes
Gravitational Wave S6 LineVeto search (extended): no
Gravitational Wave S6 Directed Search (CasA) : no
Gamma-ray pulsar search #2: no
Run CPU versions of applications for which GPU versions are available: no
i'd like to join the CPU-only Arecibo BRP race, and to do that i'd obviously have to enable CPU crunching and edit my application selections as follows:
Quote:
Binary Radio Pulsar Search (Arecibo): yes
Binary Radio Pulsar Search (Perseus Arm Survey): yes
Gravitational Wave S6 LineVeto search (extended): no
Gravitational Wave S6 Directed Search (CasA) : no
Gamma-ray pulsar search #2: no
Run CPU versions of applications for which GPU versions are available: yes
but here's the thing - i really only want to crunch Arecibo BRP tasks on the CPU, and restrict Perseus Arm Survey BRP tasks to the GPU only. it doesn't look to me like there is a way to do that...unless Arecibo BRP tasks automatically run on CPU only, and Perseus Arm Survey BRP tasks automatically run on GPUs only. could someone please confirm, deny, or at least elaborate?
Oh wow , i need to get my
)
Oh wow , i need to get my eyes checked ! thanks
RE: RE: Does this data
)
So if the runtime for these WUs is too short, may be it will be good idea to crunch them inside without sending out to the world stressing servers and freeing up our CPUs for Gamma-Ray pulsar search?
P.S. Oh, I found an answer myself. It is a rather big bundle of WUs that cannot be crunched on ATLAS only even with it's new GPUs.
Ok.
Then comes another question: why not to use WU packs like it was sometimes ago with BRP?
RE: why not to use WU packs
)
Actually the BRP5 WUs already are "bundles" of 3, or recently, 2 micro-tasks.
As for BRP4 since yesterday I'm already working on setting up a BRP4 GPU App to help us get through the new Arecibo data. This will use bundles of 16 or 32 BRP4 tasks.
BM
BM
RE: As for BRP4 since
)
When the BRp4 tasks with this new set up begin to role out, let us know.
RE: As for BRP4 since
)
Hi Bernd,
Do you plan to add GPU App selection to project preferences so that we may control which GPU apps run on our hosts? Without it monitoring and keeping tabs on host performance will be even more of a nightmare...
Gord
RE: As for BRP4 since
)
Any update on that?
RE: RE: As for BRP4 since
)
We already sent out 2/3 of the new data to the CPUs last week. I guess by the time we have the GPU App set up there will be not much data left to process.
BM
BM
Goodee, I still have a job!!
)
Goodee, I still have a job!!
Hi Bernd, In the project
)
Hi Bernd,
In the project preferences,
Binary Radio Pulsar Search (Arecibo): means CPU only
Binary Radio Pulsar Search (Perseus Arm Survey): means GPU only
Binary Radio Pulsar Search (Arecibo, GPU): is a bit ambiguous.
Does (Arecibo, GPU) mean CPU + GPU or does it mean GPU only?
Gord
i currently have a host that
)
i currently have a host that is set to crunch both Arecibo and Perseus Arm Survey BRP tasks, but on GPU only...and so my E@H preferences currently are as follows:
i'd like to join the CPU-only Arecibo BRP race, and to do that i'd obviously have to enable CPU crunching and edit my application selections as follows:
but here's the thing - i really only want to crunch Arecibo BRP tasks on the CPU, and restrict Perseus Arm Survey BRP tasks to the GPU only. it doesn't look to me like there is a way to do that...unless Arecibo BRP tasks automatically run on CPU only, and Perseus Arm Survey BRP tasks automatically run on GPUs only. could someone please confirm, deny, or at least elaborate?
TIA,
Eric