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

I have not researched this yet, and the support for different coins is still missing. will get to this tonight....

What do you think is a profitable scrypt-jane coin at the moment, we are all talking YAC, but there are others.

Use the 18.12 version for normal scrypt operations. This version is mostly for scrypt-jane.
You could also try -b 32768 for the old scrypt behavior (if I understood cbuchner1 post earlier today correct). Check the older messages from the last 24 hours.

This version has terrible Scrypt rates for me using: -i 0 -H 1 -l K7x32 -C 1 -m 1
The 12-18 would get 300khash/s with that while this version gets me 163khash/s; GPU usage is at 55% but CPU usage went up to 90% while it was 10% before.

If I were to fire up a BAMT or SMOS linux, could I use a precompiled cudaMiner version (if someone were to share theirs with me), or would I need to use a full linux and compile it myself?

Sorry for the newb question, but I don't know much about linux. I'm willing to learn though!

500kh/s seems a bit odd. only got my  760 to 284kh/s so...

Thanks for the info cbuchner1!
Please note that it's compiled with VS2012 Prof. I think that's the reason why I had to add the few additional files to the archive.
It somehow didn't work when I just installed the "Visual C++ Redistributable for Visual Studio 2012 Update 4" from Microsoft (installed 32 and 64 bit). Maybe a reboot of my machine would be needed, but didn't have time for that.

-C 2 combined with scrypt-jane in the Fermi kernel is not yet working. Without it should validate.

Those looking for an (untrusted) cudaminer binary for testing scrypt-jane mining should look in the quoted posting!!!
patoberli was kind enough to provide it.

This is up and until commit 82. It's built for Windows (32 bit executable, runs under x64). Please note that I didn't get any valid results with this version and my Fermi card though!
I don't know why, but output looked like this:
[2014-01-10 12:14:05] LONGPOLL detected new block
[2014-01-10 12:14:05] GPU #0: Quadro 4000, 0.48 khash/s
[2014-01-10 12:14:44] LONGPOLL detected new block
[2014-01-10 12:14:44] GPU #0: Quadro 4000, 0.48 khash/s
[2014-01-10 12:15:26] LONGPOLL detected new block
[2014-01-10 12:15:26] GPU #0: Quadro 4000, 0.48 khash/s
[2014-01-10 12:16:26] GPU #0: Quadro 4000, 0.48 khash/s
[2014-01-10 12:16:36] LONGPOLL detected new block
[2014-01-10 12:16:37] GPU #0: Quadro 4000, 0.45 khash/s
[2014-01-10 12:16:56] LONGPOLL detected new block
[2014-01-10 12:16:56] GPU #0: Quadro 4000, 0.47 khash/s
[2014-01-10 12:17:26] GPU #0: Quadro 4000 result does not validate on CPU (i=288, s=0)!
[2014-01-10 12:17:47] LONGPOLL detected new block
[2014-01-10 12:17:47] GPU #0: Quadro 4000, 0.48 khash/s
[2014-01-10 12:18:47] GPU #0: Quadro 4000, 0.48 khash/s
[2014-01-10 12:19:17] GPU #0: Quadro 4000 result does not validate on CPU (i=38, s=1)!
[2014-01-10 12:19:21] LONGPOLL detected new block
[2014-01-10 12:19:21] GPU #0: Quadro 4000, 0.48 khash/s
[2014-01-10 12:20:14] LONGPOLL detected new block
[2014-01-10 12:20:14] GPU #0: Quadro 4000, 0.48 khash/s

Startparameter:
D:\bitcoin\yacoin\test>cudaminer.exe -a scrypt-jane -i 1 -l F12x1 -o http://yac.coinmine.pl:8882 -O username.2:password -C 2


https://www.dropbox.com/s/0yfhgko6iodecxa/commit82_32bit.rar

Same, I would appreciate it allot

pass -b 32768 to get same performance. Or maybe 8192, 16384 ... depending on how "interactive" you want the graphics to be when running a display with the card.

by default the --batchsize parameter is 1024. To get previous non-interactive behavior, increase to 32768. ;-)  The difference when enabling -i 1 is that an extra synchronization + 0.1ms sleep is done between kernel calls.

Christian

What you've done to this cudaminer is amazing, even the old Quadro NVS 320M can mine Litecoin a little bit, from 3 to sometimes even 50 kh/s without heating up much!

See GetNfactor() in scrypt-jane.cpp. It calculates N factor by finding the difference between the coin's start time and the current time. start time, minN, and maxN are all hard coded right now, I imagine because the code came from a yacoin miner. YBCoin randomly has the same Nfactor as Yacoin right now, but that won't always be true. I provided parameters for a few coins a couple pages back, here they are again. They are all hardcoded in the mining programs for each of them, with the exception of the cgminer scrypt-jane patch which takes them as command line arguments.

YBCoin: 1372386273, minN: 4, maxN: 30
ZcCoin: 1375817223, minN: 12, maxN: 30
FreeCoin: 1375801200, minN: 6, maxN: 32
OneCoin: 1371119462, minN: 6, maxN: 30
QQCoin: 1387769316, minN: 4, maxN: 30

Also, the interactive changes to the Titan kernel confuse me. Even with -i 0 my system is completely interactive now. I'm not complaining though, my hash rate doesn't appear to have changed.

Just snagged a xeon workstation with 5 pcie slots for $120 (saw it on craigslist and made a beeline for it), filling it up with 640's tomorrow.

It seems that way. Linux has better control over the video memory. Using windows I could never get over 2.2gb memory usage and at that I got driver crashes. In linux I now have 2.86gb out of 3gb and bo crashes. Plus it gave me an extra 1khash/s for the extra memory. I was able to go from 16x1 to 20x1 all by switching. Even minerd for cpus has a performance increase in linux :-)

Seems running scrypt-jane on Windows performs worse than on Linux. I'm getting max ~1.8Kh/s in Windows as opposed to ~2.3Kh/s in Linux with same hardware. Is this to be expected?

Does anyone have the latest windows x64 build that they could share?  I'd like to try mining YAC with my setup.  PM me please.

Ahh, so it really needs an arguement for different coins.
Hopefully the compiled cudaminer im using has the right values for yacoin? Else it may be running for nothing :-)

As a side note to Christian
I have just compiled the latest github. Compared to my last compile I am seeing a performance drop. Not a lot but it is there. Using the same launch file I get

Old - 3.77khash/s
New - 3.66khash/s

Yeah start time and N factor can be different for each coin.  No blocks validate if you don't have the right values in your miner... the miner I that was released with QQcoin had these values configurable as arguments from the command line.  Ybcminer I think it was?

I was guessing :-) from Christian's new rig idea of 15khash, using 4 640's and a 660. Which is abiut 3khash/s each.

But windows is getting very bad results. I gained over 1khash/s by switching to linux