[ANN] cudaMiner & ccMiner CUDA based mining applications [Windows/Linux/MacOSX] - page 939.

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: cbuchner1 on February 06, 2014, 09:20:38 AM

Quote from: djm34 on February 06, 2014, 09:12:00 AM

Ok, just tried on the GTX780ti, at L16 T192x32 and using maxregcount of what was indicated in your post, I get around 450Mhash/sec (with variation between 427 and 452) still running at 70% and at 876Mhz (not boosting))

is this for real? unreal!

yes it is (don't know how to post an image on this forum though...)
we'll need to see if it still work like that on the real hash (I don't know how to post an image...
I hope I'll be able to solo mine this coin...

coolisbad

full member

Activity: 140

Merit: 100

Great news about the windows binaries, thanks a lot!

Any advice on what parameters to use with a GTX660 ?

cbuchner1

hero member

Activity: 756

Merit: 502

Quote from: bigjme on February 06, 2014, 08:41:56 AM

Christian I take it the one I have is fine to use? The 124Mhash/s I took a screenshot of?

wouldn't you rather have 450 kHash/s? Wink

try playing with the maxrregcount as I stated earlier.

bigjme

sr. member

Activity: 350

Merit: 250

Are you sure its 450Mhash/s? Huh

?
Screen shot please :-p

cbuchner1

hero member

Activity: 756

Merit: 502

Quote from: paulus51 on February 06, 2014, 08:38:08 AM

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

Examples:
•L27x3 is a launch configuration that works well on GTX 260
•F28x4 is a launch configuration that works on Geforce GTX 460
•K290x2 is a launch configuration that works on Geforce GTX 660Ti
•T30x16 is a launch configuration that works on GTX 780Ti.

This is outdated since the 2014-02-02 release. Kernels were swapped out (taking the ones submitted by nVidia now as default). The X kernel also is a different one now, running on Fermi. S and L kernels were removed.

cbuchner1

hero member

Activity: 756

Merit: 502

Quote from: williammm on February 06, 2014, 08:59:11 AM

Can nvidia geforce 7300 GT use this to mine?

no CUDA, sorry. A 7300 GT is good for minesweeper though.

cbuchner1

hero member

Activity: 756

Merit: 502

Quote from: djm34 on February 06, 2014, 09:12:00 AM

Ok, just tried on the GTX780ti, at L16 T192x32 and using maxregcount of what was indicated in your post, I get around 450Mhash/sec (with variation between 427 and 452) still running at 70% and at 876Mhz (not boosting))

is this for real? unreal!

cbuchner1

hero member

Activity: 756

Merit: 502

Quote from: shadypepe on February 06, 2014, 08:53:53 AM

is it normal (i.e. caused by design of the coin) that i get half the speed for Vertcoin than for other coins?

N=2048 is twice the amount of work compared to N=1024. Can you do two people's work without taking longer? If you can, you deserve a pay raise (or maybe you have been slacking in the past, lol).

So yes it's quite normal to mine Vertcoin at half the speed of regular scrypt coins.

weedoge

member

Activity: 98

Merit: 10

I wanna test this on the Titan but haven't got the first clue where to start building for windows.

djm34

legendary

Activity: 1400

Merit: 1050

Ok, just tried on the GTX780ti, at L16 T192x32 and using maxregcount of what was indicated in your post, I get around 450Mhash/sec (with variation between 427 and 452) still running at 70% and at 876Mhz (not boosting))

(also tried with L128 with 128x32 got above the GHash (but I had two line one indicating 0khash and the next something above the GHash) so I assume it didn't work.)

fcode

full member

Activity: 170

Merit: 100

Latest code gives me 60000 kh/s on the GTX560-448. Double what it was previously, awesome.

The card makes a high pitch squealing sound when running this though. Undecided

williammm

newbie

Activity: 4

Merit: 0

Can nvidia geforce 7300 GT use this to mine?

shadypepe

sr. member

Activity: 266

Merit: 250

is it normal (i.e. caused by design of the coin) that i get half the speed for Vertcoin than for other coins?

duel007

newbie

Activity: 4

Merit: 0

Is there a way to configure a failover pool yet? So many pools having downtime lately, it would be nice to not have to change them when a pool goes down.

bigjme

sr. member

Activity: 350

Merit: 250

Christian I take it the one I have is fine to use? The 124Mhash/s I took a screenshot of?

paulus51

sr. member

Activity: 616

Merit: 321

I will list the configuration for some Nvidia cards:
•GeForce GTX 560 Ti

cudaminer -H 0 -i 1 -l F8x16 -C 1 -m 1 -o stratum+tcp://yourpool.com:3334 -O [WORKERNAME]:[PASSWORD]
•GeForce GTX 660

cudaminer -H 0 -i 1 -l K5x32 -C 1 -m 1 -o stratum+tcp://yourpool.com:3334 -O [WORKERNAME]:[PASSWORD]
•GeForce GTX 670

cudaminer -H 0 -i 1 -l K7x32 -C 1 -m 1 -o stratum+tcp://yourpool.com:3334 -O [WORKERNAME]:[PASSWORD]
•GeForce GTX 780

cudaminer -H 1 -i 1 -l T9x20 -C 2 or -H 1 -i 1 -l T12x32 -c 1 -o stratum+tcp://yourpool.com:3334 -O [WORKERNAME]:[PASSWORD]

prefix blocks x warps

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

Examples:
•L27x3 is a launch configuration that works well on GTX 260
•F28x4 is a launch configuration that works on Geforce GTX 460
•K290x2 is a launch configuration that works on Geforce GTX 660Ti
•T30x16 is a launch configuration that works on GTX 780Ti.

cbuchner1

hero member

Activity: 756

Merit: 502

Quote from: coolisbad on February 06, 2014, 08:25:36 AM

Will there be a windows binary with keccak? Please? Grin

7 PM UTC

We're severly under register pressure on Compute 2.x and 3.0 devices

but Compute 3.5 supports about 255 registers max!

So guys, you can compile the keccak.cu module with -maxrregcount=112. That is what the kernel really wants under compute/sm_10. Then run keccak benchmarks with x16 launch configs and check if it's any faster. I do not have a Compute 3.5 device handy right now.

do NOT compile keccak.cu for sm_30 - in my testing the hashes were no longer validating. And a faster speed is no good if your submitted shares are broken.

I will try to reduce the register pressure in the kernel if possible - the above suggestion might me a good workaround until this is done.

Christian

coolisbad

full member

Activity: 140

Merit: 100

Will there be a windows binary with keccak? Please? Grin

trell0z

newbie

Activity: 43

Merit: 0

Quote from: ivanlabrie on February 06, 2014, 08:16:46 AM

Well, I'm having some issues with the scrypt windows binary...

I was happily mining at 716kh/s with my GTX 780 Windforce at 1267mhz core and I tried higher clocks and crashed.

Then I restarted and whenever I try to mine scrypt cudaminer won't make my card go past 953mhz (stock non-boost clocks?).
I have a custom bios now that removes boost and can mine other coins at 1329mhz core with 1100mv only but cudaminer is still pegged at 953mhz core.

Any ideas?

EDIT: I second the donation part...cudaminer is my favorite mining program now, the dev is really ahead of the game. Cheesy

What's your config for that? I'm doing 660ish~ khash with my 780 gb wf, at 1254mhz :/ Do you have extremely high memclocks also or?

bigjme

sr. member

Activity: 350

Merit: 250

if this coin takes off, christian i may have to send you a pack of beers ;-)

Topic: [ANN] cudaMiner & ccMiner CUDA based mining applications [Windows/Linux/MacOSX] - page 939. (Read 3426921 times)