Bitcoin Forum
October 22, 2018, 12:28:05 AM *
News: Make sure you are not using versions of Bitcoin Core other than 0.17.0 [Torrent], 0.16.3, 0.15.2, or 0.14.3. More info.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 [87] 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 ... 1136 »
  Print  
Author Topic: [ANN] cudaMiner & ccMiner CUDA based mining applications [Windows/Linux/MacOSX]  (Read 3401633 times)
kernels10
Sr. Member
****
Offline Offline

Activity: 408
Merit: 250


ded


View Profile
December 22, 2013, 07:00:55 AM
 #1721

So after running my GTX 560 Ti for 2days staight at a solid 280khash on the new 12/18 software, cudaminer out of nowhere spiked the hashrate up to about 450 and the card started giving hardware errors as it can't run that high.

I got the notification from my.mining pool that a worker was down, so I RDP to the machine close out cudaminer and restart my script, no changes made at all.

Now all of a sudden cudaminer is saying, "unable to query CUDA driver version.  Is an nVidia driver installed."
This of course isn't true.

Seeing as how this happened the very first time I ran cudaminer I simply tried to reinstall the driver.  When that didn't work I tried downgrading the driver and still no luck.  I even installed the CUDA development kit and that didn't work either.  I can no longer get cudaminer to launch any of the 3 versions that I have previously used.

I'm very confused at the moment.  The only thing crossing my mind is that maybe when I RDP to the machine the graphic settings are changing for remote desktop and the CUDA driver is being disabled and therefore cannot relaunch.

Anyone ever tried to restart cudaminer via RDP before?
Bigger question is why did cudaminer decide to randomly jump to 450khash after 2 straight days mining at 280?

Thoughts, comments, help, all appreciated.  5k doge to anyone that can help me find a solution.

Lots doge you rich coins wow cudaminer wow doge happy coin.


Driver crashed? happens to me if I try to push my oc to high, does it still happen after reboot?

Haven't used RDP but I am using chrome remote desktop and haven't had issues.


I am able to get up to about 322kH/s (jumps around 315-326 I'm logged in via chromeRD) under win8 pro using  -H 1 -i 0 -C 2 -D -l K31x6 if you (or anyone else with a 660Ti) wanna try that.

I don't think the -C option does anything for kepler right now though.

Edit: I'm slow
1540168085
Hero Member
*
Offline Offline

Posts: 1540168085

View Profile Personal Message (Offline)

Ignore
1540168085
Reply with quote  #2

1540168085
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1540168085
Hero Member
*
Offline Offline

Posts: 1540168085

View Profile Personal Message (Offline)

Ignore
1540168085
Reply with quote  #2

1540168085
Report to moderator
ak84
Full Member
***
Offline Offline

Activity: 126
Merit: 100


View Profile
December 22, 2013, 07:07:00 AM
 #1722


I am able to get up to about 322kH/s (jumps around 315-326 I'm logged in via chromeRD) under win8 pro using  -H 1 -i 0 -C 2 -D -l K31x6 if you (or anyone else with a 660Ti) wanna try that.

I don't think the -C option does anything for kepler right now though.


That's weird, I get 255 khash/s with those settings.
How or why did you choose K31x6? I'm not sure what the numbers mean beyond K = Kepler

Is there some command to find optimal settings for my comp?

▬▬▬▬▬▬▬▬▬ Edutainment.Tech ▬▬▬▬▬▬▬▬▬
Double ICO: Games for smart and games for business
SmartGames    ◼ CorpEdu
kernels10
Sr. Member
****
Offline Offline

Activity: 408
Merit: 250


ded


View Profile
December 22, 2013, 07:25:40 AM
 #1723


I am able to get up to about 322kH/s (jumps around 315-326 I'm logged in via chromeRD) under win8 pro using  -H 1 -i 0 -C 2 -D -l K31x6 if you (or anyone else with a 660Ti) wanna try that.

I don't think the -C option does anything for kepler right now though.


That's weird, I get 255 khash/s with those settings.
How or why did you choose K31x6? I'm not sure what the numbers mean beyond K = Kepler

Is there some command to find optimal settings for my comp?


weird. I got that from an auto run (-H 1 -i 0 -C 2 -D), not sure which version of cudaminer I was using at the time. Also, I am using afterburner to oc.
ak84
Full Member
***
Offline Offline

Activity: 126
Merit: 100


View Profile
December 22, 2013, 08:05:41 AM
 #1724



http://imgur.com/AW36Ct0

Ok, tried overclocking for the first time in my life. GTX 660 Ti

I've cracked the 300 khash/s barrier! with

-H 1 -i 0 -C 1 -D -l K7x32


Thanks everyone for the help.

▬▬▬▬▬▬▬▬▬ Edutainment.Tech ▬▬▬▬▬▬▬▬▬
Double ICO: Games for smart and games for business
SmartGames    ◼ CorpEdu
larue05
Newbie
*
Offline Offline

Activity: 38
Merit: 0


View Profile
December 22, 2013, 02:25:42 PM
 #1725

So after running my GTX 560 Ti for 2days staight at a solid 280khash on the new 12/18 software, cudaminer out of nowhere spiked the hashrate up to about 450 and the card started giving hardware errors as it can't run that high.

I got the notification from my.mining pool that a worker was down, so I RDP to the machine close out cudaminer and restart my script, no changes made at all.

Now all of a sudden cudaminer is saying, "unable to query CUDA driver version.  Is an nVidia driver installed."
This of course isn't true.

Seeing as how this happened the very first time I ran cudaminer I simply tried to reinstall the driver.  When that didn't work I tried downgrading the driver and still no luck.  I even installed the CUDA development kit and that didn't work either.  I can no longer get cudaminer to launch any of the 3 versions that I have previously used.

I'm very confused at the moment.  The only thing crossing my mind is that maybe when I RDP to the machine the graphic settings are changing for remote desktop and the CUDA driver is being disabled and therefore cannot relaunch.

Anyone ever tried to restart cudaminer via RDP before?
Bigger question is why did cudaminer decide to randomly jump to 450khash after 2 straight days mining at 280?

Thoughts, comments, help, all appreciated.  5k doge to anyone that can help me find a solution.

Lots doge you rich coins wow cudaminer wow doge happy coin.


Driver crashed? happens to me if I try to push my oc to high, does it still happen after reboot?

Haven't used RDP but I am using chrome remote desktop and haven't had issues.

I completely agree that it was indeed a driver crash that caused the initial hardware errors.  I had them happen several times during testing to get the perfect khash on this card.

However the "unable to query CUDA driver" still happens after reboot.
dga
Hero Member
*****
Offline Offline

Activity: 737
Merit: 511


View Profile WWW
December 22, 2013, 03:28:25 PM
 #1726

Semi-idle question:  Is there community interest in sponsoring some more optimization of the cudaminer code for Kepler GK104 and GK110-based cards?

(I ask about sponsoring, because part of what I have in mind is picking up a new card or two to use for benchmarking.  I'm thinking in particular of trying to optimize for the GK110-based 780 and 780Ti, but I'd also like to make sure my results generalize.  Unfortunately, I'm not a gamer, so outside of using them for research in my day job - where I already have some - I don't have any real use for shiny video cards. :-)

In honesty, I think I threw my best optimization ideas at the version most of you are already running.  *grins*  But there's probably another 5% here and there, which could translate into, say, at least a 10-20kh/sec boost on faster cards.

  -Dave

larue05
Newbie
*
Offline Offline

Activity: 38
Merit: 0


View Profile
December 22, 2013, 04:50:59 PM
 #1727

So after running my GTX 560 Ti for 2days staight at a solid 280khash on the new 12/18 software, cudaminer out of nowhere spiked the hashrate up to about 450 and the card started giving hardware errors as it can't run that high.

I got the notification from my.mining pool that a worker was down, so I RDP to the machine close out cudaminer and restart my script, no changes made at all.

Now all of a sudden cudaminer is saying, "unable to query CUDA driver version.  Is an nVidia driver installed."
This of course isn't true.

Seeing as how this happened the very first time I ran cudaminer I simply tried to reinstall the driver.  When that didn't work I tried downgrading the driver and still no luck.  I even installed the CUDA development kit and that didn't work either.  I can no longer get cudaminer to launch any of the 3 versions that I have previously used.

I'm very confused at the moment.  The only thing crossing my mind is that maybe when I RDP to the machine the graphic settings are changing for remote desktop and the CUDA driver is being disabled and therefore cannot relaunch.

Anyone ever tried to restart cudaminer via RDP before?
Bigger question is why did cudaminer decide to randomly jump to 450khash after 2 straight days mining at 280?

Thoughts, comments, help, all appreciated.  5k doge to anyone that can help me find a solution.

Lots doge you rich coins wow cudaminer wow doge happy coin.


Driver crashed? happens to me if I try to push my oc to high, does it still happen after reboot?

Haven't used RDP but I am using chrome remote desktop and haven't had issues.

WOOOT!!!!!  kernels10 you have been awarded 5k doge.  My conclusion about RDP was 100% accurate and I was able to verify that via chrome remote desktop.

I used RDP to install chrome remote desktop, exited RDP, entered through chrome remote desktop and the scripts started up perfectly.  What this verified is that at least on the GTX 560 Ti RDP does indeed kill the CUDA nVidia drivers upon connection; therefore making it impossible to restart cudaminer.

I'm curious if this is the case with all Microsoft RDP sessions.
Antivanity
Newbie
*
Offline Offline

Activity: 26
Merit: 0


View Profile
December 22, 2013, 05:48:22 PM
 #1728

2 x EVGA 780 Classified overclocked to 1300MHz
cudaminer settings: -i 0 -H 1 -m 1 -l T12x16

http://i.imgur.com/O2dXdTf.jpg
Ponn
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
December 22, 2013, 05:52:11 PM
 #1729

Hi everyone, I wrote a small Treatise on Cuda Miner, mind helping me check it over? (Much updated! wow!)
http://www.reddit.com/r/Dogecoinmining/comments/1tguse/a_treatise_on_cuda_miner/
Quote
A Treatise on CUDAMiner
Thanks CBuchner for creating Cudaminer!
If this helped please upvote for other puppy miners!
I've added popular cards and configs to the bottom.
Disclaimer: I'm like every other shibe.. I can make mistakes, if something doesn't look right, please, please correct me! Thanks!
Some edits: A Minor Observation. -c 1 performs better than -c 2 generally.
Hi! So you're looking to Mine using your Nvidia Card, don't know how to setup CUDA Miner?
The basic format for CUDA Miner's .bat file will be.
Stratum (For HTTP: Replace stratum+tcp with http):
Ex: cudaminer -H 0 -i 1 -l auto -C 2 -o stratum+tcp://xyz.yourpool.com:porthere -u username.worker -p password
What each flag does:
[-H] scrypt also has a small SHA256 component to it: 0 hashes this single threaded on the CPU. 1 to enable multithreaded hashing on the CPU. 2 offloads everything to the GPU (default)
[-i] list of flags (0 or 1) to enable interactive desktop performance on individual cards. Use this to remove lag at the cost of some hashing performance. Do not use large launch configs for devices that shall run in interactive mode - it's best to use autotune!
This setting set at 0 will cause your GPU to run at 100% and most likely will cause lag while even tabbing through your browser! Set at 1 if you're trying to use your PC while mining.
[-l] specify the kernel launch configuration per device. This replaces autotune or heuristic selection. You can pass the strings "auto" or just a kernel prefix like L or F or K or T to autotune for a specific card generation or a kernel prefix plus a lauch configuration like F28x8 if you know what kernel runs best (from a previous autotune).
[-C] list of flags (0 or 1 or 2) to enable use of the texture cache for reading from the scrypt scratchpad. 1 uses a 1D cache, whereas 2 uses a 2D texture layout. Cached operation has proven to be slightly faster than noncached operation on most GPUs.
In Depth & Getting the most out of your card:
Well, let me start off with a checklist.
Do you have the latest version of CUDA Miner?
If Yes then Move on.. If no (Or you're not sure), then go here: https://bitcointalk.org/index.php?topic=167229.0
Do you have the latest drivers installed for your video card?
If yes.. carry on! If not.. http://www.nvidia.com/Download/index.aspx
Well then, now that that's done...
A few things you'll need to know before going on..
What video card do you have?
If you know.. Carry on. If you're not sure.. Then Install GPU-Z to find out!
http://www.techpowerup.com/downloads/SysInfo/GPU-Z/
Now that you know what video card you have, you'll have to find out what compute version it is using. Find your video card on this chart. (For ease, use ctrl + F on windows and then type in the # of your card)
Compute Version:
1.0
G80, G92, G92b, G94, G94b GeForce GT 420, GeForce 8800 Ultra, GeForce 8800 GTX, GeForce GT 340, GeForce GT 330, GeForce GT 320, GeForce 315, GeForce 310, GeForce 9800 GT, GeForce 9600 GT, GeForce 9400GT, Quadro FX 5600, Quadro FX 4600, Quadro Plex 2100 S4, Tesla C870, Tesla D870, Tesla S870 1.1
G86, G84, G98, G96, G96b, G94, G94b, G92, G92b GeForce G110M, GeForce 9300M GS, GeForce 9200M GS, GeForce 9100M G, GeForce 8400M GT, GeForce G105M, Quadro FX 4700 X2, Quadro FX 3700, Quadro FX 1800, Quadro FX 1700, Quadro FX 580, Quadro FX 570, Quadro FX 470, Quadro FX 380, Quadro FX 370, Quadro FX 370 Low Profile, Quadro NVS 450, Quadro NVS 420, Quadro NVS 290, Quadro NVS 295, Quadro Plex 2100 D4, Quadro FX 3800M, Quadro FX 3700M, Quadro FX 3600M, Quadro FX 2800M, Quadro FX 2700M, Quadro FX 1700M, Quadro FX 1600M, Quadro FX 770M, Quadro FX 570M, Quadro FX 370M, Quadro FX 360M, Quadro NVS 320M, Quadro NVS 160M, Quadro NVS 150M, Quadro NVS 140M, Quadro NVS 135M, Quadro NVS 130M, Quadro NVS 450, Quadro NVS 420, Quadro NVS 295
1.2
GT218, GT216, GT215 GeForce GT 240, GeForce GT 220, GeForce 210, GeForce GTS 360M, GeForce GTS 350M, GeForce GT 335M, GeForce GT 330M, GeForce GT 325M, GeForce GT 240M, GeForce G210M, GeForce 310M, GeForce 305M, Quadro FX 380 Low Profile, NVIDIA NVS 300, Quadro FX 1800M, Quadro FX 880M, Quadro FX 380M, NVIDIA NVS 300, NVS 5100M, NVS 3100M, NVS 2100M
1.3
GT200, GT200b GeForce GTX 280, GeForce GTX 275, GeForce GTX 260, Quadro FX 5800, Quadro FX 4800, Quadro FX 4800 for Mac, Quadro FX 3800, Quadro CX, Quadro Plex 2200 D2, Tesla C1060, Tesla S1070, Tesla M1060
2.0
GF100, GF110 GeForce GTX 590, GeForce GTX 580, GeForce GTX 570, GeForce GTX 480, GeForce GTX 470, GeForce GTX 465, GeForce GTX 480M, Quadro 6000, Quadro 5000, Quadro 4000, Quadro 4000 for Mac, Quadro Plex 7000, Quadro 5010M, Quadro 5000M, Tesla C2075, Tesla C2050/C2070, Tesla M2050/M2070/M2075/M2090
2.1
GF104, GF106 GF108,GF114, GF116, GF119 GeForce GTX 560 Ti, GeForce GTX 550 Ti, GeForce GTX 460, GeForce GTS 450, GeForce GTS 450, GeForce GT 640 (GDDR3), GeForce GT 630, GeForce GT 620, GeForce GT 610, GeForce GT 520, GeForce GT 440, GeForce GT 440, GeForce GT 430, GeForce GT 430*, GeForce GTX 675M, GeForce GTX 670M, GeForce GT 635M, GeForce GT 630M, GeForce GT 625M, GeForce GT 720M, GeForce GT 620M, GeForce 710M, GeForce 610M, GeForce GTX 580M, GeForce GTX 570M, GeForce GTX 560M, GeForce GT 555M, GeForce GT 550M, GeForce GT 540M, GeForce GT 525M, GeForce GT 520MX, GeForce GT 520M, GeForce GTX 485M, GeForce GTX 470M, GeForce GTX 460M, GeForce GT 445M, GeForce GT 435M, GeForce GT 420M, GeForce GT 415M, GeForce 710M, GeForce 410M, Quadro 2000, Quadro 2000D, Quadro 600, Quadro 410, Quadro 4000M, Quadro 3000M, Quadro 2000M, Quadro 1000M, NVS 5400M, NVS 5200M, NVS 4200M
3.0
GK104, GK106, GK107 GeForce GTX 770, GeForce GTX 760, GeForce GTX 690, GeForce GTX 680, GeForce GTX 670, GeForce GTX 660 Ti, GeForce GTX 660, GeForce GTX 650 Ti BOOST, GeForce GTX 650 Ti, GeForce GTX 650, GeForce GTX 780M, GeForce GTX 770M, GeForce GTX 765M, GeForce GTX 760M, GeForce GTX 680MX, GeForce GTX 680M, GeForce GTX 675MX, GeForce GTX 670MX, GeForce GTX 660M, GeForce GT 750M, GeForce GT 650M, GeForce GT 745M, GeForce GT 645M, GeForce GT 740M, GeForce GT 730M, GeForce GT 640M, GeForce GT 640M LE, GeForce GT 735M, GeForce GT 730M, Quadro K5000, Quadro K4000, Quadro K2000, Quadro K2000D, Quadro K600, Quadro K500M, Tesla K10
3.5
GK110, GK208 GeForce GTX TITAN, GeForce GTX 780, GeForce GT 640 (GDDR5), Quadro K6000, Tesla K20 '*' - OEM-only products (Thanks Wikipedia!)
Now.. Moving on and now that you know what version you have..
We now can find out what Kernel CUDA Miner is best suited to using! Available kernel prefixes are: L - Legacy cards (compute 1.x) F - Fermi cards (Compute 2.x) S - Kepler cards (currently compiled for Compute 1.2) - formerly best for Kepler K - Kepler cards (Compute 3.0) - based on Dave Andersen's work. Now best for Kepler. T - Titan, GTX 780 and GK208 based cards (Compute 3.5) X - Experimental kernel. Currently requires Compute 3.5 (Copied from the CUDAMiner Readme) For Legacy Cards you're best off using auto.
Now find the # of SM(X) units for your card here: http://en.wikipedia.org/wiki/Comparison_of_Nvidia_graphics_processing_units
Fermi is limited to 16 Warps per SM Unit Kepler is limited to 32 Warps per SMX Unit.
If you're on Fermi, with The 560 Ti which has 8 SM units your .bat file will look something like: cudaminer -H 0 -i 1 -l F8x16 -C 2 -o stratum+tcp://xyz.yourpool.com:porthere -u username.worker -p password
If you're using Kepler, with the 660 (Seems to be a popular card), which has 5 SMX Units your .bat will look like: cudaminer -H 0 -i 1 -l K5x32 -C 2 -o stratum+tcp://xyz.yourpool.com:porthere -u username.worker -p password
Titan should be the same as Kepler. (Although someone else may know more on this topic..)
Ta-Da!
To get the most out of your card, you can tweak the -H and -C with 0 1 or 2. I would not recommend using -i 0 if you are trying to browse the web while using your computer, things can stutter, a lot, and annoy you.
WOW! Much hash. http://s15.postimg.org/onsy6sdjf/doge2.jpg
General Mining Tips:
Be sure to find a good pool of course! Try to find a PPLNS Pool with 0-1% fee. I'm not going to suggest any, I don't want to seem biased. There are many good pools! (Thanks Crazypotatoes on doges.org for suggesting this)
Use GPU-Z to monitor temperatures on your card. If it gets too hot you may want to shut it down. Mining doges isn't worth it at the expense of your computer and or video card. (Crazypotatoes again)
Use MSI Afterburner to increase your fan speeds. (Don't Overclock if you're not sure about what you're doing. There are many guides on this but I don't think its worth it if you're not sure what you're touching.) (Yep Crazypotatoes)
Some cards and configs:
560 Ti: -H 0 -i 1 -l F8x16 -C 1 -m 1
660: -H 0 -i 1 -l K5x32 -C 1 -m 1
670:-H 0 -i 1 -l K7x32 -C 1 -m 1
780: -H 1 -i 1 -l T9x20 -C 2 or -H 1 -i 1 -l T12x32 -c 1
Thanks!
ak84
Full Member
***
Offline Offline

Activity: 126
Merit: 100


View Profile
December 22, 2013, 07:07:24 PM
 #1730

Ponn that is excellent. Thank you.

BTW please specify that -i 0 will fully use GPU and slow down your computer display a little
while -i 1 will leave a little power for your display needs.

IN my case using -i 1  reduces hash speed ~20khash/s but when switching browser tabs or typing I'm not noticeably lagging. With -i 0 I have some display lag.

▬▬▬▬▬▬▬▬▬ Edutainment.Tech ▬▬▬▬▬▬▬▬▬
Double ICO: Games for smart and games for business
SmartGames    ◼ CorpEdu
cbuchner1
Hero Member
*****
Offline Offline

Activity: 756
Merit: 500


View Profile
December 22, 2013, 07:23:41 PM
 #1731

2 x EVGA 780 Classified overclocked to 1300MHz
cudaminer settings: -i 0 -H 1 -m 1 -l T12x16



yeah, keep making me sorry for buying 3x 780 Ti ...

The extra power draw of the 3 additional SMX in the Ti prevents any meaningful overclocking, it seems.

Christian

Antivanity
Newbie
*
Offline Offline

Activity: 26
Merit: 0


View Profile
December 22, 2013, 07:25:38 PM
 #1732

2 x EVGA 780 Classified overclocked to 1300MHz
cudaminer settings: -i 0 -H 1 -m 1 -l T12x16

http://i.imgur.com/O2dXdTf.jpg

yeah, keep making me sorry for buying 3x 780 Ti ...

The extra power draw of the 3 additional SMX in the Ti prevents any meaningful overclocking, it seems.

Christian



Im actually in line for the Step-Up program by EVGA to upgrade to TI's for free. You saying its not worth it ?
Ponn
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
December 22, 2013, 07:29:32 PM
 #1733

2 x EVGA 780 Classified overclocked to 1300MHz
cudaminer settings: -i 0 -H 1 -m 1 -l T12x16

http://i.imgur.com/O2dXdTf.jpg

yeah, keep making me sorry for buying 3x 780 Ti ...

The extra power draw of the 3 additional SMX in the Ti prevents any meaningful overclocking, it seems.

Christian



Just want to say thanks a bunch for CUDA Miner.. I'm learning something for once rather than twiddling my thumbs on the internet! Wish I could tip ya, but I don't have anything to tip with atm.
cbuchner1
Hero Member
*****
Offline Offline

Activity: 756
Merit: 500


View Profile
December 22, 2013, 07:34:54 PM
 #1734

Im actually in line for the Step-Up program by EVGA to upgrade to TI's for free. You saying its not worth it ?

I am peaking out at 590 kHash/s per device. Meh. limited to 106% TDP, by the way.

Antivanity
Newbie
*
Offline Offline

Activity: 26
Merit: 0


View Profile
December 22, 2013, 07:36:49 PM
 #1735

Im actually in line for the Step-Up program by EVGA to upgrade to TI's for free. You saying its not worth it ?

I am peaking out at 590 kHash/s per device. Meh. limited to 106% TDP, by the way.



Oh, well that makes me sad. My 2 cards have 2 diff TDP.. 110% and 115%.. which i find odd..

Anyway, thanks for cudaminer, specially the December 18th update.. amazing speed boots!
cbuchner1
Hero Member
*****
Offline Offline

Activity: 756
Merit: 500


View Profile
December 22, 2013, 07:37:10 PM
 #1736

The github repo now contains some more optimized SHA256 code that gives a little extra speed with the -H 2 option. Less time spent on the SHA256 part means more time spent on the scrypt core part means higher hash rate.

Christian
cbuchner1
Hero Member
*****
Offline Offline

Activity: 756
Merit: 500


View Profile
December 22, 2013, 07:39:11 PM
 #1737

Oh, well that makes me sad. My 2 cards have 2 diff TDP.. 110% and 115%.. which i find odd..

Anyway, thanks for cudaminer, specially the December 18th update.. amazing speed boots!

If these are identical cards and hardware revisions, you could try flashing the VGA bios of the 115% card over the BIOS of the slower card. Credit for the giant speed boost goes to David Andersen. He implemented the code in such a way that I couldn't really wrap my mind around before I actually saw his code (I've tried, but couldn't picture it).


cbuchner1
Hero Member
*****
Offline Offline

Activity: 756
Merit: 500


View Profile
December 22, 2013, 08:47:04 PM
 #1738

Semi-idle question:  Is there community interest in sponsoring some more optimization of the cudaminer code for Kepler GK104 and GK110-based cards?

In honesty, I think I threw my best optimization ideas at the version most of you are already running.  *grins*  But there's probably another 5% here and there, which could translate into, say, at least a 10-20kh/sec boost on faster cards.

  -Dave

You could also optimize on the low-end GT 640 (GDDR 5 version). It has Compute 3.5, does around 105 kHsh/s with OC and I generally found its results to scale up pretty linearly with the number of SMX. i.e. scaling it up to 12 SMX (like the GTX 780) yields some 630 kHash/s which people actually seem to be hitting when overclocking their devices.

EDIT: I did some profiling with Cuda 5.5 Visual Profiler on a Compute 3.0 device recently (also 2 SMX, a laptop part). I found that the artithmetic units were pretty maxed out. And it also showed an 80% efficiency in the instruction scheduler. Meaning that the dual issue feature in each SMX four warp schedulers was pretty nicely utilized. The occupancy on each SMX was 100%, which is perfect. Memory accesses were fully coalesced 128 byte transactions. Can't get any better than this.

My recent optimizations in the SHA256 code were aimed at lower register use and higher occupancy. There is still some extra efficiency to be had coalescing the memory access, I guess.




dga
Hero Member
*****
Offline Offline

Activity: 737
Merit: 511


View Profile WWW
December 22, 2013, 08:59:51 PM
 #1739

Semi-idle question:  Is there community interest in sponsoring some more optimization of the cudaminer code for Kepler GK104 and GK110-based cards?

In honesty, I think I threw my best optimization ideas at the version most of you are already running.  *grins*  But there's probably another 5% here and there, which could translate into, say, at least a 10-20kh/sec boost on faster cards.

  -Dave

You could also optimize on the low-end GT 640 (GDDR 5 version). It has Compute 3.5, does around 105 kHsh/s with OC and I generally found its results to scale up pretty linearly with the number of SMX. i.e. scaling it up to 12 SMX (like the GTX 780) yields some 630 kHash/s which people actually seem to be hitting when overclocking their devices.

EDIT: I did some profiling with Cuda 5.5 Visual Profiler on a Compute 3.0 device recently (also 2 SMX, a laptop part). I found that the artithmetic units were pretty maxed out. And it also showed an 80% efficiency in the instruction scheduler. Meaning that the dual issue feature in each SMX four warp schedulers was pretty nicely utilized. The occupancy on each SMX was 100%, which is perfect. Memory accesses were fully coalesced 128 byte transactions. Can't get any better than this.


Ooh.  Good idea for the cheaper device - thank you. 

Re "can't get any better" - that's the other reason I was thinking about grubbing for help.  I'm guessing that the remainder of the optimization is going to be ugly.  I've been staring at, e.g., the cuobjdump assembly output and the instruction throughput tables and trying to figure out if there are ways to improve it (nothing obvious).  And, as you note, 80% instruction scheduling is already quite high.  Doubling up keys in a clever way might get that to 90 but at the cost of probably unacceptable register pressure.  I tried it once and threw away the code, but there are a few other ways to imagine doing it.

It's really hard to beat the raw number of ALUs those AMD devices have when the code is as trivially parallel as brute-force hashing.

polarbear7217008
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
December 22, 2013, 09:04:57 PM
 #1740

So I am just mining a bit for the experience and its mostly going well but this weird thing. After a couple accepted my hash rate goes out of control and it never works again until I reboot my computer. If this is a known issue or someone else has this if you could let me know. Thanks and sorry if this is newbish.



Code:
[2013-12-21 14:15:56] GPU #0: using launch configuration K10x14
[2013-12-21 14:15:56] GPU #0: GeForce GT 750M, 4480 hashes, 9.72 khash/s
[2013-12-21 14:16:04] GPU #0: GeForce GT 750M, 586880 hashes, 76.56 khash/s
[2013-12-21 14:16:33] GPU #0: GeForce GT 750M, 2298240 hashes, 77.26 khash/s
[2013-12-21 14:16:33] accepted: 1/1 (100.00%), 77.26 khash/s (yay!!!)
[2013-12-21 14:16:40] GPU #0: GeForce GT 750M, 546560 hashes, 76.78 khash/s
[2013-12-21 14:16:41] accepted: 2/2 (100.00%), 76.78 khash/s (yay!!!)
[2013-12-21 14:17:06] GPU #0: GeForce GT 750M, 1944320 hashes, 77.23 khash/s
[2013-12-21 14:17:06] accepted: 3/3 (100.00%), 77.23 khash/s (yay!!!)
[2013-12-21 14:17:53] GPU #0: GeForce GT 750M, 4636800 hashes, 97.35 khash/s
[2013-12-21 14:17:53] GPU #0: GeForce GT 750M, 5841920 hashes, 364482 khash/s
[2013-12-21 14:18:48] Stratum detected new block
[2013-12-21 14:18:48] GPU #0: GeForce GT 750M, 1978523776 hashes, 35912 khash/s
[2013-12-21 14:18:55] GPU #0: GeForce GT 750M, 2154705280 hashes, 347175 khash/s
[2013-12-21 14:23:55] Stratum detected new block
[2013-12-21 14:23:55] GPU #0: GeForce GT 750M, 605833216 hashes, 2014 khash/s
[2013-12-21 14:23:56] GPU #0: GeForce GT 750M, 120843520 hashes, 340147 khash/s
[2013-12-21 14:26:11] Stratum detected new block
[2013-12-21 14:26:11] GPU #0: GeForce GT 750M, 3904416000 hashes, 28782 khash/s
[2013-12-21 14:26:16] GPU #0: GeForce GT 750M, 1726941440 hashes, 345834 khash/s
[2013-12-21 14:33:27] GPU #0: GeForce GT 750M, 2568025856 hashes, 5971 khash/s
[2013-12-21 14:33:28] GPU #0: GeForce GT 750M, 358234240 hashes, 346545 khash/s
[2013-12-21 14:33:29] Stratum detected new block
[2013-12-21 14:33:29] GPU #0: GeForce GT 750M, 661507840 hashes, 347550 khash/s
[2013-12-21 14:36:42] Stratum detected new block
[2013-12-21 14:36:42] GPU #0: GeForce GT 750M, 2588029440 hashes, 13409 khash/s
[2013-12-21 14:36:45] GPU #0: GeForce GT 750M, 804558720 hashes, 345060 khash/s
[2013-12-21 14:39:03] Stratum detected new block
[2013-12-21 14:39:03] GPU #0: GeForce GT 750M, 955258624 hashes, 6888 khash/s
[2013-12-21 14:39:05] GPU #0: GeForce GT 750M, 413306880 hashes, 343030 khash/s
[2013-12-21 14:40:08] Stratum detected new block
Pages: « 1 ... 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 [87] 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 ... 1136 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!