You do know you can turn each kind off individually in the settings...right?

Run only the selected applications MilkyWay@Home: yes
MilkyWay@Home N-Body Simulation: no

But that doesn't select between single-core and multi-core N-Body, does it?

Yes it does, if you unselect the "N-Body Simulation" units you won't get any more multi-core wu's, on the other hand if you unselect the "MilkyWay@Home" units then you won't get any more single core wu's.

Yes it does, if you unselect the "N-Body Simulation" units you won't get any more multi-core wu's, on the other hand if you unselect the "MilkyWay@Home" units then you won't get any more single core wu's.

OK, it looks like I had both selected. I will try just the N-Body. Thanks.

cpu and gpu is too much wats...need to choose something one.

You do know you can turn each kind off individually in the settings...right?

Run only the selected applications MilkyWay@Home: yes
MilkyWay@Home N-Body Simulation: no

But that doesn't select between single-core and multi-core N-Body, does it?

Yes it does, if you unselect the "N-Body Simulation" units you won't get any more multi-core wu's, on the other hand if you unselect the "MilkyWay@Home" units then you won't get any more single core wu's.

No, it does not. With "MilkyWay@Home: yes", you will get single core MilkyWay@Home WUs (they are all single core), but not single core MilkyWay@Home N-Body Simulation WUs.

---

cpu and gpu is too much wats...need to choose something one.

You can choose that already in your MilkyWay@Home preferences.

---

You do know you can turn each kind off individually in the settings...right?

Run only the selected applications MilkyWay@Home: yes
MilkyWay@Home N-Body Simulation: no

But that doesn't select between single-core and multi-core N-Body, does it?

Yes it does, if you unselect the "N-Body Simulation" units you won't get any more multi-core wu's, on the other hand if you unselect the "MilkyWay@Home" units then you won't get any more single core wu's.

No, it does not. With "MilkyWay@Home: yes", you will get single core MilkyWay@Home WUs (they are all single core), but not single core MilkyWay@Home N-Body Simulation WUs.

By definition here at MW N-Body wu's are multi-core wu's.

By definition here at MW N-Body wu's are multi-core wu's.

No, there's also a single core N-Body application, see applications page.

---

By definition here at MW N-Body wu's are multi-core wu's.

No, there's also a single core N-Body application, see applications page.

Hmm I did not know that.... Thanks!!!

cpu and gpu is too much wats...need to choose something one.

Always GPU. Way more processing power for the inputted energy. Downside is it is harder to code applications for it.

Another 4+ hour "Server can't open database" issue again. Please increase our WU limits.

Also, how about changing the scheduled communication time between request from 1m30s to something higher? Won't that help with the amount of hits the server is also taking on? If we can have more WU downloaded, it doesn't need to try and connect every 1m30s.

So how about doubling the 600 limit for GPUs to 1200?

Here is the thing happening with the database flickering between on and off everyday for many hours at a time.

With 200 WUs per GPU, I run out of work in <2 hours.
The database usually goes offline for longer than this amount of time, putting effectively my computer on a crunching break multiple times per day.

I would strongly encourage you to either improve the stability of your servers, increase the limit of GPU WUs we can have stored to a much higher amount (600WUs per GPU, for example). Another suggestion would be to increase the work you put in each WU. That way they would run for longer on GPU and the lower limit you now have in place would be adequate. If your database gets crunched by too many requests, maybe you could implement a higher time between requests, now it is every 90 seconds, what about every 10 minutes or something higher to reduce the load on your end.

I really hope you will improve this situation.

I really hope you will improve this situation.

I have concluded that if they are smart enough to map the galaxy, then they must be smart enough to know that by limiting the work units, they will lose the fastest machines to other projects (especially in view of all the server outages).

My guess is that they are getting enough work done with the slower machines to satisfy their needs. It may take time to analyze the results, for example, which can't be sped up further. So if that does not work for you, probably finding another project is the best solution. They all have their limits somewhere; there is not an infinite supply of work. We just need to move around to accommodate what they can supply at any given time.

I really hope you will improve this situation.

I have concluded that if they are smart enough to map the galaxy, then they must be smart enough to know that by limiting the work units, they will lose the fastest machines to other projects (especially in view of all the server outages).

My guess is that they are getting enough work done with the slower machines to satisfy their needs. It may take time to analyze the results, for example, which can't be sped up further. So if that does not work for you, probably finding another project is the best solution. They all have their limits somewhere; there is not an infinite supply of work. We just need to move around to accommodate what they can supply at any given time.

I agree the new "Do You Feel Lucky? (GFN World Record))" workunits at PrimeGrid, suggested for high end gpu's only, takes about 2 days on a 1080Ti and you get almost 1 million credits for each one. And they will make as many as they have people willing to crunch them. For cpu workunits they have some that take over 100 days!!

Hey Everyone,

Sorry that things have been bad for so long. I just want to let you know that we have ordered a new server and it is on the way. Hopefully it will be here in a couple weeks and it should further relieve some of the database issues we have been experiencing.

Best,

Jake

Good news indeed Jake. Congrats!

I wonder if there is a way to set the number of cached WU based on the rate of processed WU in the past 1-3 days? This might be better than basing on the number of GPU.

hi all made vid on youtube for multiple instances instruction's and at full load on a Radeon VII
RADEON VII GIGABYTE// 3 Instances_ Milkyway@home WUs BOINC_ 3_instances
https://www.youtube.com/watch?v=4xKy9wGKmz4
all the best and welcome to earth

---