That hashrate is definitely not correct, but I can't help you further because as I see it the T kernel only works with single memory allocation (-m 1) which I can't use so all I can think of is trying different kernels.

What did autotune ended up with?

Autotune gets between 2.69 and 2.72khash/s

I will check the setting it uses tomorrow. Its almost 5am here so yeh :-p

Treggar your settings are wrong. Tell it to do auto and see what that does with 1 running. Its macing my gtx 780 out so yours shouldnt be doing that much. Unless that coin really is allowing much higher hashrates to yacoin. Im not sure

Im guessing because of it being an older gpu and maybe autotune isnt set up properly.

Yacoin has a much higher N factor than QQcoin. Higher the N factor, less kH, basically.

Anyway, you may be right about the amount of threads. With T36x3 I was able to bring up my hashrate to 98kH/s on a 780. I'm only seeing 6% GPU usage as well. However, if I open multiple instances of cudaminer it just halves the hashrate, and GPU usage stays the same.

Maybe something to do with the way memory is allocated on the Titan kernel?

So Yacoin is worth mining?

It's weird that my Yacoin results (1.9kH/s) seem to be a lot lower than everyone else's. Are you guys with the 780 overclocking your cards? I have mine at +200.

Checked MSI Afterburner to make sure and my card isn't throttling, full clocks 99% usage.

Hm, I am mining on a pool and not solo, maybe that's why.

Edit: Nah, setup solo and same hash rates.

bathrobehero: that's interesting, I'm not seeing the same here though. Changing the scan time doesn't affect hash rate at all for me.

T12x32 is way to big for scrypt-jane. That's what you should use on regular scrypt coins. For yacoin that kind of config would require something like 50GB of GPU ram.

Autotune is not perfect. Look at the chart (run with -D to show debug info) then try configs that are just outside the populated area of the chart, until you've explored all the edges and found your limits. When you go too far it will print something like this: "GPU #0:Launch config 'T11x2' requires too much memory!"

I'm using T20x1 on my 780 and getting 3.4 kHash. T10x2 works well for me as well.

Can someone please explain this to me? It looks contradictory.

-C, --texture-cache   comma separated list of flags (0/1) specifying which of the CUDA devices shall use the texture cache for mining. Kepler devices will profit.

This says kepler devices will profit.

GPU #0: GeForce GTX 770 with compute capability 3.0
GPU #0: the 'K' kernel ignores the texture cache argument

My 770 is a kepler device, but cudaminer says that my kernel ignores the texture cache...

So which is it and how will my device profit from a launch option which is ignored?

I'm running OS 10.9 on a hackintosh, so I don't know that I can help you out there. Although I did try it out on two gtx 670s at work today and they got 2 kH/s each with autotune with 331.20 on Linux. Are you running CUDA 5.5?

For those of you attempting to hash QQC or YBC or any other scrypt-N coin... you're probably going to need to modify some code and recompile. It looks to me like the time value used to calculate the N is hardcoded to Yacoin's start time. See GetNfactor() in scrypt-jane.cpp. edit: just reread the last two pages and I see that some of you have already done that. doh



Are you using the latest version from git or a binary release? I see a commit message on Dec 28th that says "add back support for chunked memory allocation and texture cache to Kepler kernel. Slight speed-ups with -C 1 are seen." which implies he removed it at one point, possibly when upgrading to CUDA 5.5.


My yacoin config.
./cudaminer -u coercion.1 -p x -a scrypt-jane -o 127.0.0.1:9942 -l T21x1 -H 1

I just realized I can't run 21x1 since I pulled today. I ran that config all last night and now I can only run T20x1.

Immature means you can't spend them yet because they need to be included in more blocks so a fork doesn't screw you or anyone you transact with.