Formula Boinc 2018 Strategy

Dang I didn't download enough CPU tasks. They are all going to be done in 3 hours. The estimated WU time was 2 hours each, but they all completed in 1 hour.
 
You can only download up to 128 per host anyway. So if you have less then upload them, chsngr you CPU count to something over 16 and start again.
 
I'm just going to leave the network on and hope that the validation pending tasks build up. I'm going to cruise through anything I get. Wish my Threadripper was all builtup!
 
LOL the N-body tasks are set to 16 threads and they don't change when I properly set the number of CPUs, and restart. Hmm they might not run the most efficiently. It appears these Nbody tasks are set from the project's servers.

Edit: So far for my Threadripper build I have sorted out the CPU, Heatsink, and RAM, Storage (old HD), PSU. Need a case and motherboard.
 
Last edited:
motqalden said:
Seems like way to much work to bunker this project with my gpu's.... just gonna let it ride as its only 1 day
Click to expand...

Am doing this as well.

Edit: With .5/.5, my run times are a consistent low 200s. These are 1070 Ti's.

Unfortunately, if i push for 3 tasks per GPU, i get up over 300s. Gonna fly with just 2 per looks like.
 
Last edited:
Good plan. That looks like the total WUs done per hour would be very close with either option (3 tasks or 2).
 
MN Scout, that behavior with the work units downloading with the core count applies pretty much to all MT projects. To get around it, you typically have to set up an app_config assigning a limit of threads used and that only works if it is in place before you download the work units. Anyone crunching with GPU's in their boxes should make sure and do this anyways to guarantee the CPU's doing MT are not stealing the threads away from feeding the GPU's.
 
There are two main tasks. The one that gives 203.92 and 227.62 credits per task.

Running one HD7970 @ 1GHz, Win7, Driver 14.9, 4 tasks per GPU, no CPU running and with default MW preference setting.
Avg run time for 203.92 task is about 40.3s
Avg run time for 227.62 task is about 31.7s
Both results are averaged over 100 tasks in total.

I can fire up two Nvidia cards but they are not as efficient as 7970. Will see how we go.
 
Last edited:
XS output is not catching up with us yet. Not sure if they are bunkering considering that the tasks finish very quickly or perhaps they have all the time in this world to fire up lots of boinc instances. Haven't seen SUSA members yet in their team.

Only see caveman running at full blast atm. Here are his rigs before he hides them.

upload_2018-8-30_12-13-46.png
 
Someone save his rigs in an html document or something.

We can still look up the rigs by ID even when he hides them.
 
my rig with 2 1080ti crashed while i was at work today... then when it came back online it was only running 2x gpu tasks and favoring CPU over gpu... had to use the config for project_max_concurrent, but this fixed it
 
Is anyone getting a Amazon p3 spot instance? I think 10 Milkyway tasks could run on the V100 at once in just over a minute. I don't have the time to learn how to set it up. :( I don't understand the impact of the spot vs Reserved Duration instances.
 
Pretty sure you should save your money on those for another sprint. I am guessing we are going to walk all over them this sprint as it runs well on GPU. They always get a good lead since they seem to have their bunker game on point and apparently too much time on their hands. I could be wrong and feel free to call me out on it in a few days if i am :D
 
After tonight my computers will hopefully just coast along and not turn off. Some bad storms forecasted for tomorrow. My computers may go down from a power outage for the weekend.
 
After the sprint race got off yesterday, XS just released their CSG bunker. Pretty sure they are prepping this for some time already and hoping that CSG got selected at some point in time. This is a project that is quite difficult to catch up if you just started to bunker only when this project is announced. Just a gentle reminder....

upload_2018-8-31_6-52-11.png
 
Some of us have been bunkering CSG as well. The deadlines are so long you can hold them for a couple sprints.
 
XSUSA is getting blown away in the MW sprint. We are up ~8m points+.

Think it's cool if i get back to AN and finish that off?

Edit - I'll hold off till about this time-ish tomorrow just to ensure no XtraSneaky tactics hurt us.
 
Sure it seems. XS is trying to help SUSA. Pecos is abandoning XS....

upload_2018-9-1_18-50-45.png
 
Yeah i noticed that. cutting losses when they know they can't win in returns for help at other times.
 
Them jumping ship is them saying that they're not worried about the marathon also. I guess they figure they can just ramp up stoneageman at the end of the season if they need to hold us off.
 
Where should I park my 1080TI?

Any benefit to me buying something like a 7970 or 2080X? Debating buying one and parking it on Milkway to try and keep consistent points going there and hopefully gaining some positions. Are they even good at anything else?
 
7970 will be good at MW. Their is also a Primegrid sub project that utilizes FP64 as well. I would imagine Collatz would do fairly well with a 7970 also.

Park the 1080Ti on GPUGrid, Einstein@home, Moo! Wrapper or Collatz. Those projects need some love.
 
Alright. I'll switch my 1080ti between those till I get to 10 mil on GPUGrid, Einstein and Moo.
 
For the record, the S9150s were doing about 11 minutes per task on Collatz with a config file.
 
XtremeSystems picked up a lot of points at XANSONS for COD.

Do we need to do anything strategically to get more WUs ourselves?

upload_2018-9-4_16-52-37.png


I'm leaning towards thinking we are all fine, since this project doesn't routinely give out work.
 
Read the thread "everyone should do this" or something like that. You'll see a batch script to hammer the projects with little to no work.
 
And ask for ALL work as they do have CPU work when it rains. Just grab all that you can because the batches go super fast.
 
It appears we got 0 points lately. I need to get better about running this script for these slow projects. Not helping us to WIN in these, or for me to ever have a chance at 1 million points in them.
 
Yeah, I run them all on my main rigs.

I recently got enough points on CAS@Home to keep us above XS yesterday.
 
Hmmm. Haven't seen that before. That will be disappointing if it happens on a large scale.
 
I’m currently running MilkyWay on both of my 280X’s and will soon fire up a brand new 280 I found this week in my inventory. It’s a warranty replacement from XFX I had completely forgotten about until I went rummaging through all my old video card boxes for a VGA to DVI adapter. Picked up a box for a 280 that was heavy and realized the box was still sealed shut. I then remembered what happened and that I received the replacement a couple of years ago when I wasn’t doing any GPU crunching anymore due to electricity costs. Thing has been sitting on my shelf ever since. Anyway, that bitch is getting some electrons flowing through it soon. Going to hit MW first. Looking to at least hit my 100 million milestone there, may go to 200 million.

My nVidia GPU’s will stay on PrimeGrid for a while, as they are currently making me 9-10 million PPD there on PPS Sieve and my goal is 1 billion in that sub project (~350 million to go).
 
ChristianVirtual said:
regarding longterm bunker for CSG: https://csgrid.org/csg/workunit.php?wuid=3928654

"too many results" ... and zero points. Why is that ? What does it mean for the long-term-bunker idea and the risk of loosing points
Click to expand...

I think because of this constraint applied to the work unit.
upload_2018-9-8_7-6-58.png


So theoretically, you can download lots of tasks and then intentionally abort them. Rinse and repeat to infinity. The aborted task will be part of the quorum of 5 total tasks sent out. This will certainly affect those who bunker (like XS and us). There seems to be a lot of aborted tasks, at least from the tasks that I'm currently bunkering. Ditto for tasks with error. I'm guessing some people aborting because the tasks are too long or for whatever reasons. I don't know if there is a limit on how many you can abort the tasks. It is certainly a dirty strategy but it is still a strategy that can be employed by anyone. Nothing to stop them as far as I know.
 
Last edited:
Looking at some of my tasks, there are two errors already for this WU. My rig is 30626. Probably a quorum of 2 errors might have been reached. I'll find out soon when I do drop the bunker: https://csgrid.org/csg/workunit.php?wuid=3920676. Same with this one https://csgrid.org/csg/workunit.php?wuid=3927678 and https://csgrid.org/csg/workunit.php?wuid=3920518, and a few other more.

So, just got to be careful about bunkering for too long. I know XS occasionally drop their bunker. Maybe they know something that we don't know?
 
I am experimenting and have today turned down the power limit on all of my GPU's to 80%. I have always run my GPU's at stock clocks with no tweaking, but I now want to see if I can save some power $$$ without hitting my PPD too badly. Will need a couple of days to assess impact to PPD, but in just two hours after turning down the limits on all of them, the ambient temp in my basement has gone down by 6 degrees F. There are currently 6 1070ti's, a 980ti, and 2 R9 280X's running PPS Sieve and MW down there. Amazing how much heat they make when running full bore 24x7.
 
You must log in or register to reply here.
Back
Top