There has been some limited mention of providing a GPU version of N-Body.

Is there any information on whether it will be CUDA or OpenCl?
Will it require good dual-precision performance?

This could be useful for GPU purchasing decisions, if or when the time comes.

I second this. I only run MW@H on my GPU, the CPU is reserved for WCG. And there seems to be a lot more development these days on n-body, so I assume it's more interesting to the project. I'd certainly like to contribute if such a client is feasible.

I third this.

I fourth this

Probably it's too much difficult to adapt nbody code for gpu.

Probably it's too much difficult to adapt nbody code for gpu.

My fault, my fault.
I found this old link to a research on nbody on GPU, so it seems feasible

Probably it's too much difficult to adapt nbody code for gpu.

My fault, my fault.
I found this old link to a research on nbody on GPU, so it seems feasible

I can only see the preface.

Probably it's too much difficult to adapt nbody code for gpu.

My fault, my fault.
I found this old link to a research on nbody on GPU, so it seems feasible

Yes, it's feasible, but extremely inefficient, it needs about as much time on GPU as on CPU while Separation is 50-60 times faster on GPU than on CPU. I don't think there are many, who would want to slow down their GPU output by that factor. It seems to be one of the thngs, that are not suitable for GPUs. It would be however great to get here the option "Run CPU versions of applications for which GPU versions are available" in the preferences, so anyone who wants, could limit CPU to n-Body only while running Separation on GPU.

---

It would be however great to get here the option "Run CPU versions of applications for which GPU versions are available" in the preferences, so anyone who wants, could limit CPU to n-Body only while running Separation on GPU.

+1. I've asked for this many times and am ignored. Einstein does it, it's possible.

In fact running seperation on a CPU is utterly pointless. They should remove it from CPUs altogether. People are wasting their computing time and electricity.

In fact running seperation on a CPU is utterly pointless. They should remove it from CPUs altogether. People are wasting their computing time and electricity.

Well, 32-bit computers can't run n-Body, but in general I agree, would be the best method to speed up n-Body research if needed.

---

In fact running seperation on a CPU is utterly pointless. They should remove it from CPUs altogether. People are wasting their computing time and electricity.

Well, 32-bit computers can't run n-Body, but in general I agree, would be the best method to speed up n-Body research if needed.

Anybody still running a 32 bit computer is hardly contributing much computing power. I've got some 12 year old machines that are 64 bit.

It would be however great to get here the option "Run CPU versions of applications for which GPU versions are available" in the preferences, so anyone who wants, could limit CPU to n-Body only while running Separation on GPU.

+1. I've asked for this many times and am ignored. Einstein does it, it's possible.

In fact running seperation on a CPU is utterly pointless. They should remove it from CPUs altogether. People are wasting their computing time and electricity.

Some people just want to run something to help and trying to run the NBody tasks on a pc without a gpu that can crunch, I know drivers probably not loaded, means stalls etc as they don't do the research to know they need an app_config file to limit the number of cpu cores means those people can run the Separation tasks with no problems

Some people just want to run something to help and trying to run the NBody tasks on a pc without a gpu that can crunch, I know drivers probably not loaded, means stalls etc as they don't do the research to know they need an app_config file to limit the number of cpu cores means those people can run the Separation tasks with no problems

Even a fast CPU is pointless to run on seperation. Running some outdated crap that needs cores limiting is not helping the science of seperation one bit. I've got a 12 year old quad core CPU, and it runs nbody with no adjustments. Leave the GPU stuff to the GPUs and put CPUs on stuff which can't do GPU.

means stalls etc as they don't do the research to know they need an app_config file to limit the number of cpu cores means those people can run the Separation tasks with no problems

Does n-Body not respect the "Use at most x% of the CPUs" setting?

---

means stalls etc as they don't do the research to know they need an app_config file to limit the number of cpu cores means those people can run the Separation tasks with no problems

Does n-Body not respect the "Use at most x% of the CPUs" setting?

I think it's the boinc scheduler that sorts that. And it's a very simplistic piece of crap that's easily confused. If you have 24 cores and say "use 15 cores", it will still get the full sized 16 core nbodies, because it's stupid.

Probably it's too much difficult to adapt nbody code for gpu.

My fault, my fault.
I found this old link to a research on nbody on GPU, so it seems feasible

The PDF version of this is $41. It seems to me that the the N body crunchers here, past and present, should be able to get a free copy, since we have skin in the game....

The PDF version of this is $41. It seems to me that the the N body crunchers here, past and present, should be able to get a free copy, since we have skin in the game....

Maybe that's how they get funding to run this place?

Maybe that's how they get funding to run this place?

Could be! LOL If that's the case, I think a urologist might say" My goodness! That's a pretty weak stream!"

Maybe that's how they get funding to run this place?

Could be! LOL If that's the case, I think a urologist might say" My goodness! That's a pretty weak stream!"

Interesting choice of analogy!