Bitcoin GPU-based Mining Machines good for BOINC / SETI?

Message boards : Number crunching : Bitcoin GPU-based Mining Machines good for BOINC / SETI?
Message board moderation

To post messages, you must log in.

Previous · 1 . . . 39 · 40 · 41 · 42 · 43 · 44 · 45 . . . 66 · Next

AuthorMessage
Ian&Steve C.
Avatar

Send message
Joined: 28 Sep 99
Posts: 4267
Credit: 1,282,604,591
RAC: 6,640
United States
Message 1979779 - Posted: 10 Feb 2019, 22:10:23 UTC - in response to Message 1979755.  


[Edit] I just looked up the 300mm Thermaltake ribbon cable
https://www.amazon.com/Thermaltake-AC-045-CN1OTN-C1-Premium-Extender-Graphic/dp/B06Y1SX7ZN
Yikes! That would add up fast for a multiple mining rig at $66 a piece.


yup. but there are cheaper options that still work.

like this: https://www.amazon.com/LINKUP-Riser-Cable-64GB-Extender/dp/B07994SMZZ/ref=sr_1_3?keywords=pcie+3.0+riser+16x&qid=1549836533&s=electronics&sr=1-3
Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

ID: 1979779 · Report as offensive     Reply Quote
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1979780 - Posted: 10 Feb 2019, 22:12:02 UTC

I forgot to mention. I am running all gpus with 1 core per gpu with -nobs in the gpu command line.

When I run the gpus without a dedicated core the box pegs 100% because the gpu threads are no longer counted directly towards the cpu limit.

I expect if I play with manually dropping the project max concurrent I could get the cpus to back off down below 100% but this fix was faster. And I am not sure if I can free up any cpu cores without pegging the cpu at 100% again.

Tom
A proud member of the OFA (Old Farts Association).
ID: 1979780 · Report as offensive     Reply Quote
Ian&Steve C.
Avatar

Send message
Joined: 28 Sep 99
Posts: 4267
Credit: 1,282,604,591
RAC: 6,640
United States
Message 1979781 - Posted: 10 Feb 2019, 22:13:06 UTC - in response to Message 1979775.  

it's almost always bad USB cables. I have a lot of spares.
Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

ID: 1979781 · Report as offensive     Reply Quote
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1979785 - Posted: 10 Feb 2019, 22:30:56 UTC - in response to Message 1979779.  

Thanks. I bookmarked that link. Lot more reasonable and lots more length choices.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1979785 · Report as offensive     Reply Quote
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1979787 - Posted: 10 Feb 2019, 22:34:45 UTC - in response to Message 1979780.  

I expect if I play with manually dropping the project max concurrent I could get the cpus to back off down below 100% but this fix was faster. And I am not sure if I can free up any cpu cores without pegging the cpu at 100% again.


Be careful of any max_concurrent statement with any BOINC client release greater than 7.14.2.

DA broke BOINC work fetch with max_concurrent in the latest branch
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1979787 · Report as offensive     Reply Quote
Ian&Steve C.
Avatar

Send message
Joined: 28 Sep 99
Posts: 4267
Credit: 1,282,604,591
RAC: 6,640
United States
Message 1979794 - Posted: 10 Feb 2019, 23:08:41 UTC - in response to Message 1979787.  

i'm using 7.15.0 and use project_max_concurrent. it still acts normal to me. downloads and caches the right number of WUs and runs the right number of CPU jobs.
Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

ID: 1979794 · Report as offensive     Reply Quote
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1979798 - Posted: 10 Feb 2019, 23:40:47 UTC - in response to Message 1979794.  
Last modified: 10 Feb 2019, 23:43:05 UTC

I should say that grabbing the master out of the 7.15.0 branch NOW is not a good idea. You grabbed it out of the branch before my commit #2918 was merged. That is what broke work fetch.
[Edit] See my and Richard's post in my thread.
https://setiathome.berkeley.edu/forum_thread.php?id=83645
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1979798 · Report as offensive     Reply Quote
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1980229 - Posted: 14 Feb 2019, 4:09:15 UTC - in response to Message 1979660.  





So this is https://setiathome.berkeley.edu/show_host_detail.php?hostid=8589036 now?


Tom
A proud member of the OFA (Old Farts Association).
ID: 1980229 · Report as offensive     Reply Quote
Ian&Steve C.
Avatar

Send message
Joined: 28 Sep 99
Posts: 4267
Credit: 1,282,604,591
RAC: 6,640
United States
Message 1980233 - Posted: 14 Feb 2019, 4:45:15 UTC - in response to Message 1980229.  

yup. up to 8 cards now.

working great
Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

ID: 1980233 · Report as offensive     Reply Quote
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1980488 - Posted: 15 Feb 2019, 12:48:53 UTC

I had stability issues and am down to "only" 6 cards. I googled a way to read/watch the system log. So far everything is still running. I may add a video card back in now that I have a chance to "see" what is happening when everything quits.

Tom
A proud member of the OFA (Old Farts Association).
ID: 1980488 · Report as offensive     Reply Quote
Ian&Steve C.
Avatar

Send message
Joined: 28 Sep 99
Posts: 4267
Credit: 1,282,604,591
RAC: 6,640
United States
Message 1980549 - Posted: 15 Feb 2019, 18:25:52 UTC - in response to Message 1980488.  

What’s happening when it quits?

One symptom you can look for to see if bad USB cables might be causing problems. With the system running, run nvidia-smi -l to keep the nvidia-smi loop running every few seconds. If you see one or more cards that are running below 90% all the time, it’s likely a bad USB cable on that card. With everything working properly, you should see 95+% GPU utilization nearly all the time (except when moving to a new WU where it’ll briefly drop to 0).
Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

ID: 1980549 · Report as offensive     Reply Quote
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1980553 - Posted: 15 Feb 2019, 19:00:30 UTC - in response to Message 1980549.  
Last modified: 15 Feb 2019, 19:01:17 UTC

What’s happening when it quits?

One symptom you can look for to see if bad USB cables might be causing problems. With the system running, run nvidia-smi -l to keep the nvidia-smi loop running every few seconds. If you see one or more cards that are running below 90% all the time, it’s likely a bad USB cable on that card. With everything working properly, you should see 95+% GPU utilization nearly all the time (except when moving to a new WU where it’ll briefly drop to 0).


I come in and logon and all the programs I left running are gone. Its almost like it rebooted and self logged on. Since I have the bios set for power off instead of power on when it looses power and I require a logon password I am pretty sure it is not re-booting.

I can try the looping for nvidia-smi. So far the only times it shows below 90% is when it is ending/starting a new task when I manually check.

If it runs continuously with no problems for a couple more days, I will add the 7th gpu back in and continue to watch the system log.

If push comes to shove it will simply be a 6 gpu system. But if I can manage to tinker with something so I can run 7 or 8 I will.

While I can't say for the future, at this stage I think I will suspend the idea of trying to get a copy of your system up (eg. new MB) for two reasons. 1) Its doing pretty good already. 2) You had to down grade your cpu chips. The only down grade I have for the cpu's would be all the way down to e5-2670's.

Tom
A proud member of the OFA (Old Farts Association).
ID: 1980553 · Report as offensive     Reply Quote
Ian&Steve C.
Avatar

Send message
Joined: 28 Sep 99
Posts: 4267
Credit: 1,282,604,591
RAC: 6,640
United States
Message 1980556 - Posted: 15 Feb 2019, 19:11:38 UTC - in response to Message 1980553.  

i didnt really downgrade the CPUs. i just put in more efficient CPUs. the CPUs i moved to are actually an upgrade.

The CPUs that seemed to cause a problem : E5-2690 8c/16t 135W/32nm
The new CPUs that work fine: E5-2680v2 10c/20t 115W/22nm

more cores, slightly less clock speed, smaller lithography, much more efficient, and overall more productive.
Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

ID: 1980556 · Report as offensive     Reply Quote
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1980561 - Posted: 15 Feb 2019, 19:24:13 UTC - in response to Message 1980553.  

If it logged off the current user, then that is shown in the system log. Pretty simple to see the event preceding the logoff and that would point to what is causing the instability. Look for the big break in continuity of the time stamps in the log before you logged back in.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1980561 · Report as offensive     Reply Quote
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1980607 - Posted: 15 Feb 2019, 23:34:10 UTC - in response to Message 1980561.  

If it logged off the current user, then that is shown in the system log. Pretty simple to see the event preceding the logoff and that would point to what is causing the instability. Look for the big break in continuity of the time stamps in the log before you logged back in.


I am still learning how to get to the right part of the system log. So I am still not even seeing the startup/re-boot.

Tom
A proud member of the OFA (Old Farts Association).
ID: 1980607 · Report as offensive     Reply Quote
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1980610 - Posted: 15 Feb 2019, 23:54:10 UTC

A brand new boot will always be captured in syslog. The previous boot will be in syslog.1
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1980610 · Report as offensive     Reply Quote
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1980639 - Posted: 16 Feb 2019, 2:59:00 UTC - in response to Message 1980610.  

A brand new boot will always be captured in syslog. The previous boot will be in syslog.1


TY. Let me look again :)
A proud member of the OFA (Old Farts Association).
ID: 1980639 · Report as offensive     Reply Quote
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1980641 - Posted: 16 Feb 2019, 3:05:42 UTC - in response to Message 1980639.  

A brand new boot will always be captured in syslog. The previous boot will be in syslog.1


TY. Let me look again :)


I am going to go research for some kind of better tool to try to read the log. The previous log doesn't show a shutdown, a crash, nothing. It just stops.

Tom
A proud member of the OFA (Old Farts Association).
ID: 1980641 · Report as offensive     Reply Quote
Profile Tom M
Volunteer tester

Send message
Joined: 28 Nov 02
Posts: 5124
Credit: 276,046,078
RAC: 462
Message 1980643 - Posted: 16 Feb 2019, 3:32:10 UTC - in response to Message 1980641.  

A brand new boot will always be captured in syslog. The previous boot will be in syslog.1


TY. Let me look again :)


I am going to go research for some kind of better tool to try to read the log. The previous log doesn't show a shutdown, a crash, nothing. It just stops.

Tom


Ok. I give up. Either tonight or tomorrow morning I will be installing the Ubuntu desktop. I have set Seti for NNT and then I will backup the xml files in Boinc. Re-install etc.

Then I should be able to follow advice :/

Tom
A proud member of the OFA (Old Farts Association).
ID: 1980643 · Report as offensive     Reply Quote
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1980644 - Posted: 16 Feb 2019, 3:50:21 UTC - in response to Message 1980643.  

Just grab the entire BOINC folder and move it to another drive temporarily. Then once you have Ubuntu Desktop installed, move the folder back to the Desktop.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1980644 · Report as offensive     Reply Quote
Previous · 1 . . . 39 · 40 · 41 · 42 · 43 · 44 · 45 . . . 66 · Next

Message boards : Number crunching : Bitcoin GPU-based Mining Machines good for BOINC / SETI?


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.