[ANN][YAC] Yacminer GPU miner for Yacoin - page 5.

Thirtybird

hero member

Activity: 693

Merit: 500

Quote from: antonio8 on February 23, 2014, 12:10:32 AM

Quote from: Thirtybird on February 21, 2014, 11:25:35 PM

Quote from: guysoft on February 21, 2014, 05:26:59 PM

Hey,
So I have bene playing with Yacminer and I can't pass the 1 kh/s without getting HW errors on my Sapphire R9 290.
I was wondering, could I use ultracoin minier to mine yacoins? It uses scrypt-jane and I get on it stable 333 kh/s.

But I get rejects when connection to a pool.

Thirtybird, any thoughts on that?
Is there a difference in the source?

http://www.ultracoin.net/ultracoinminer.html

Guy

The difference is Ultracoin is at NFactor 10, and YACoin is at NFactor 14. This means that YACoin takes 16 times as much memory to perform one calculation as Ultracoin. Hashrate in theory should only be 16 time less, but no card out has enough memory to be able to completely utilize ALL the GPU power before it runs out of memory, so GPU hasrates are even lower than that.

If you can't cross 1 KH/sec with YACoin without getting hardware errors, I suggest you read the recommendations in the SCRYPT-README file included with the YACMiner source and binaries https://github.com/Thirtybird/YACMiner/blob/master/SCRYPT-README. Configuring a miner (ANY miner) for a high N factor scrypt-chacha coin take practice, patience, and experimentation. Configuring a miner for Ultracoin, or any scrypt (litecoin, dogecoin et. al) is child's play and you can usually cut and paste someone else's settings for any card and get in the ballpark for results.

I agree whole heartedly with that.

I can't get this to run for nothing without hardware errors. Tried lower intensity to lowest setting, xintensity to lowest setting. Don't know if I need rawintensity set. So dang frustrating. Literally been trying to mine this coin for 2 days now with my R7 250. Running perfect on my 750ti.

Just about ready to give up and move on to another coin.

The _ONLY_ way I recommend configuring YACMiner is using Raw Intensity. Everything else is likely to be less than optimal. Read the SCRYPT-README included with the package (the new one from 3.4.2 has some major updates), and check the yac wiki hardware page for some suggestions. If that's a 2GB card, you can get 2.5 KH/sec out of it (or thereabouts, depends on manufacturer) - if it's a 1 GB card, not so much... YAC needs memory, and 1GB cards don't really cut it too well...

links for the help
https://bitcointalksearch.org/topic/ann-yacminer-amd-gpu-miner-for-scrypt-chacha-n-scrypt-and-scrypt-coins-475569
https://github.com/Thirtybird/YACMiner
http://yacoinwiki.tk/index.php/Mining_Hardware_Comparison

antonio8

legendary

Activity: 1400

Merit: 1000

Quote from: Thirtybird on February 21, 2014, 11:25:35 PM

Quote from: guysoft on February 21, 2014, 05:26:59 PM

Hey,
So I have bene playing with Yacminer and I can't pass the 1 kh/s without getting HW errors on my Sapphire R9 290.
I was wondering, could I use ultracoin minier to mine yacoins? It uses scrypt-jane and I get on it stable 333 kh/s.

But I get rejects when connection to a pool.

Thirtybird, any thoughts on that?
Is there a difference in the source?

http://www.ultracoin.net/ultracoinminer.html

Guy

The difference is Ultracoin is at NFactor 10, and YACoin is at NFactor 14. This means that YACoin takes 16 times as much memory to perform one calculation as Ultracoin. Hashrate in theory should only be 16 time less, but no card out has enough memory to be able to completely utilize ALL the GPU power before it runs out of memory, so GPU hasrates are even lower than that.

If you can't cross 1 KH/sec with YACoin without getting hardware errors, I suggest you read the recommendations in the SCRYPT-README file included with the YACMiner source and binaries https://github.com/Thirtybird/YACMiner/blob/master/SCRYPT-README. Configuring a miner (ANY miner) for a high N factor scrypt-chacha coin take practice, patience, and experimentation. Configuring a miner for Ultracoin, or any scrypt (litecoin, dogecoin et. al) is child's play and you can usually cut and paste someone else's settings for any card and get in the ballpark for results.

I agree whole heartedly with that.

I can't get this to run for nothing without hardware errors. Tried lower intensity to lowest setting, xintensity to lowest setting. Don't know if I need rawintensity set. So dang frustrating. Literally been trying to mine this coin for 2 days now with my R7 250. Running perfect on my 750ti.

Just about ready to give up and move on to another coin.

Thirtybird

hero member

Activity: 693

Merit: 500

Quote from: guysoft on February 21, 2014, 05:26:59 PM

Hey,
So I have bene playing with Yacminer and I can't pass the 1 kh/s without getting HW errors on my Sapphire R9 290.
I was wondering, could I use ultracoin minier to mine yacoins? It uses scrypt-jane and I get on it stable 333 kh/s.

But I get rejects when connection to a pool.

Thirtybird, any thoughts on that?
Is there a difference in the source?

http://www.ultracoin.net/ultracoinminer.html

Guy

The difference is Ultracoin is at NFactor 10, and YACoin is at NFactor 14. This means that YACoin takes 16 times as much memory to perform one calculation as Ultracoin. Hashrate in theory should only be 16 time less, but no card out has enough memory to be able to completely utilize ALL the GPU power before it runs out of memory, so GPU hasrates are even lower than that.

If you can't cross 1 KH/sec with YACoin without getting hardware errors, I suggest you read the recommendations in the SCRYPT-README file included with the YACMiner source and binaries https://github.com/Thirtybird/YACMiner/blob/master/SCRYPT-README. Configuring a miner (ANY miner) for a high N factor scrypt-chacha coin take practice, patience, and experimentation. Configuring a miner for Ultracoin, or any scrypt (litecoin, dogecoin et. al) is child's play and you can usually cut and paste someone else's settings for any card and get in the ballpark for results.

guysoft

newbie

Activity: 10

Merit: 0

Hey,
So I have bene playing with Yacminer and I can't pass the 1 kh/s without getting HW errors on my Sapphire R9 290.
I was wondering, could I use ultracoin minier to mine yacoins? It uses scrypt-jane and I get on it stable 333 kh/s.

But I get rejects when connection to a pool.

Thirtybird, any thoughts on that?
Is there a difference in the source?

http://www.ultracoin.net/ultracoinminer.html

Guy

Thirtybird

hero member

Activity: 693

Merit: 500

Quote from: xandebnu on February 19, 2014, 06:49:51 AM

anyone know the command line to Scrypt R9 280x - GV-R928XOC-3GD?

Any chance you could not spam every thread with your question? I offered you advice in one of them..

xandebnu

sr. member

Activity: 672

Merit: 251

Infleum

anyone know the command line to Scrypt R9 280x - GV-R928XOC-3GD?

patoberli

member

Activity: 106

Merit: 10

Thanks for the help.
The most stable/fast I find is this:
yacminer --scrypt -o stratum+tcp://yac.coinmine.pl:9088 -u pato.4 -p password --thread-concurrency 5050 --lookup-gap 1 -w 32 -R 288

This produces quite exactly 0.9 - 1.0 kh/s.

A higher lookup-gap reduces the speed, more than -R 288 increases the speed, but HW will increase more than accepted.

Thirtybird

hero member

Activity: 693

Merit: 500

Quote from: patoberli on February 13, 2014, 05:11:28 PM

I don't get the new build to work on my 5870m with the latest beta drivers under windows 8.1 x64.
yacminer --scrypt -o stratum+tcp://yac.coinmine.pl:9088 -u pato.4 -p password --thread-concurrency 7168 --lookup-gap 2
with -I 7 runs without many errors, but only around 0.5 kh/s. If I increase -I to 10 or 9 I get nearly 2 kh/s, but only HW counting up.
Memory usage is just 650 MB (my card has 1 GB), but increasing --thread-concurrency to 8192 will crash the driver.
Instead of -I -R 256 runs, -R 512 increasing HW. Anything between 256 and 512 produces an error:
[2014-02-13 23:10:28] Error -54: Enqueueing kernel onto command queue. (clEnque
ueNDRangeKernel)

Only 128, 256, 512, 1024, .... are valid -R configurations (but > 256 = HW errors Sad

)

Any ideas?

That's a bummer. For best results on that card, allocate as much memory as you can. If you can't allocate more than 512 MB on a 1GB card, you need to do the basics first and once that is sorted out, then tweak YACMiner. If you can't sort that out, I would resort to stable non-beta drivers.

Pro-Tip: On 5XXX, 6XXX and maybe 7XXX series cards, you have to adjust -R in values of work-size. You haven't specified it, so I'm guessing it's defaulting to 256 for your card. Set worksize to 32 and adjust R in increments of 32 until you find the highest value for R that does not produce HW errors. Oh, and lookup-gap - you'll need 4 or maybe even 8...

patoberli

member

Activity: 106

Merit: 10

I don't get the new build to work on my 5870m with the latest beta drivers under windows 8.1 x64.
yacminer --scrypt -o stratum+tcp://yac.coinmine.pl:9088 -u pato.4 -p password --thread-concurrency 7168 --lookup-gap 2
with -I 7 runs without many errors, but only around 0.5 kh/s. If I increase -I to 10 or 9 I get nearly 2 kh/s, but only HW counting up.
Memory usage is just 650 MB (my card has 1 GB), but increasing --thread-concurrency to 8192 will crash the driver.
Instead of -I -R 256 runs, -R 512 increasing HW. Anything between 256 and 512 produces an error:
[2014-02-13 23:10:28] Error -54: Enqueueing kernel onto command queue. (clEnque
ueNDRangeKernel)

Only 128, 256, 512, 1024, .... are valid -R configurations (but > 256 = HW errors Sad

)

Any ideas?

debido666

member

Activity: 68

Merit: 10

Quote from: Thirtybird on February 03, 2014, 01:26:48 PM

Quote from: debido666 on February 03, 2014, 12:25:06 AM

Reason I ask about --scan-time and --expiry is of this link. http://www.reddit.com/r/dogecoin/comments/1ui3bx/increase_such_hashrate_1_to_5_scrypt_tweaking/ceicnyv

I know it's for Dogecoin. Isn't Yacoin 60s block time? Maybe stratum takes care of this for pools?
Learning as I go...

That was a good read - it's never something I've tweaked. The default for scan-time is actually 30 seconds in YACMiner. It may have been carried over from cgminer, or it may have been added by someone before I got it.

Expiry may offer an improvement, looking at my long-running thread on one machine, I've got 31 stales shares and 7 rejected shares over 65 hours on 4 cards. That's a very low percentage considering I have over 4,000 accepted shares. It may sneak in a couple more than the stock configuration, but I doubt it will be anything vastly outside the margin of error in luck-based mining...

And this...https://github.com/veox/sgminer/issues/22

Thirtybird

hero member

Activity: 693

Merit: 500

Quote from: debido666 on February 03, 2014, 12:25:06 AM

Reason I ask about --scan-time and --expiry is of this link. http://www.reddit.com/r/dogecoin/comments/1ui3bx/increase_such_hashrate_1_to_5_scrypt_tweaking/ceicnyv

I know it's for Dogecoin. Isn't Yacoin 60s block time? Maybe stratum takes care of this for pools?
Learning as I go...

That was a good read - it's never something I've tweaked. The default for scan-time is actually 30 seconds in YACMiner. It may have been carried over from cgminer, or it may have been added by someone before I got it.

Expiry may offer an improvement, looking at my long-running thread on one machine, I've got 31 stales shares and 7 rejected shares over 65 hours on 4 cards. That's a very low percentage considering I have over 4,000 accepted shares. It may sneak in a couple more than the stock configuration, but I doubt it will be anything vastly outside the margin of error in luck-based mining...

Thirtybird

hero member

Activity: 693

Merit: 500

Quote from: ilostcoins on February 03, 2014, 07:00:41 AM

Thank you for the great work, Thirtybird. My hashrate is improved by 25% or so. Cheesy

The raw intensity is a great setting to have and your tip for using GPUz to tune thread concurrency is a good one. I haven't try other more refined changes though.

What I did was just start with some low intensity, use GPUz to check how far my thread concurrency (TC) can go, and then change raw intensity to TC/32 (I use lookup gap 2, g 1). I guess I can fine tune for further improvement, but haven't done that so far.

debido666, I don't know if this is related to your case, but sometimes, after using some bad miner settings, even though Windows seem to be ok or have recovered, I need to reboot for miner to work correctly with good settings.

Glad to hear it. TC / 32 is right about where I am on my settings (just a bit under actually) on my 250's with G=1. My 240 4GB cards are quite a bit different as I have to run them at G=2. Their multiplier is ~1/38 - those are really the little cards that can. 320 shaders pumping out ~2.8KH/sec!

debido666

member

Activity: 68

Merit: 10

My computer doesn't like GPU-Z. Because of Windows 8.1? UEFI enabled?

After a 12 hour test, getting 1.6 KH/s. With plenty of accepted shares. A few HW. Going to change it from 632 raw-intensity to 624.

ilostcoins

sr. member

Activity: 274

Merit: 250

Thank you for the great work, Thirtybird. My hashrate is improved by 25% or so. Cheesy

The raw intensity is a great setting to have and your tip for using GPUz to tune thread concurrency is a good one. I haven't try other more refined changes though.

What I did was just start with some low intensity, use GPUz to check how far my thread concurrency (TC) can go, and then change raw intensity to TC/32 (I use lookup gap 2, g 1). I guess I can fine tune for further improvement, but haven't done that so far.

debido666, I don't know if this is related to your case, but sometimes, after using some bad miner settings, even though Windows seem to be ok or have recovered, I need to reboot for miner to work correctly with good settings.

debido666

member

Activity: 68

Merit: 10

Quote from: debido666 on February 03, 2014, 12:37:15 AM

Tried 16384 again. It's working correctly. Going to try higher values. Weird.

If I go pass 19991, it switches from dedicated to dynamic. ~1470 of memory tops.

debido666

member

Activity: 68

Merit: 10

Tried 16384 again. It's working correctly. Going to try higher values. Weird.

debido666

member

Activity: 68

Merit: 10

Quote from: Thirtybird on February 02, 2014, 10:30:23 PM

Quote from: debido666 on February 02, 2014, 03:21:34 PM

Thanks for the reply. Think I have a problem with GPU-Z. Dedicated stays at 0 MB, always. Dynamic is the only thing that changes.
I have a 2 GB card.

Well, with any card currently available, I think you get better performance with 1 thread, but for your card you will need to allocate 1.6 -1.7 GB to that thread. (double your TC to 28416 and adjust up or down from there). You're trying to cram a bunch of work into half the available memory - YACoin mining benefits from more memory - give it to it!

Thanks for the tip on HWInfo64 - I will point windows 8 folks to that tool.

--scan-time and --expiry : I don't set them, so whatever the default is.

Thing is, when I go higher than what's stated. It goes over to dynamic memory (I tried 16384 and it bombs). Think there's more in use than HWinfo states.
I'm on single thread, now. -R 512. I get some HW. But it seems OK.

Reason I ask about --scan-time and --expiry is of this link. http://www.reddit.com/r/dogecoin/comments/1ui3bx/increase_such_hashrate_1_to_5_scrypt_tweaking/ceicnyv

Quote

You want both to be < block time, which is 60s for Dogecoin. Optimal values will take some playing around with relative to your hardware setup, but anything lower than the block time will result in an improvement in accepted shares (not hash rate, just better results from your hash rate). Generally I would say that expiry should be a little higher than scan time, and probably both should be 1/2 or less than the block time. You could start with values of 1 for each and work up, or maybe start at 30s or so for each and work down. The default values I believe are 120s expiry and 60s scantime based on 600s block time for bitcoin, so working off the same premise perhaps values of 12s expiry and 6s scantime would be the dogecoin analogue.

I know it's for Dogecoin. Isn't Yacoin 60s block time? Maybe stratum takes care of this for pools?
Learning as I go...

Thirtybird

hero member

Activity: 693

Merit: 500

Quote from: debido666 on February 02, 2014, 03:21:34 PM

Thanks for the reply. Think I have a problem with GPU-Z. Dedicated stays at 0 MB, always. Dynamic is the only thing that changes.
I have a 2 GB card.

Well, with any card currently available, I think you get better performance with 1 thread, but for your card you will need to allocate 1.6 -1.7 GB to that thread. (double your TC to 28416 and adjust up or down from there). You're trying to cram a bunch of work into half the available memory - YACoin mining benefits from more memory - give it to it!

Thanks for the tip on HWInfo64 - I will point windows 8 folks to that tool.

--scan-time and --expiry : I don't set them, so whatever the default is.

debido666

member

Activity: 68

Merit: 10

15 min run. scan-time 20 expiry 30.

debido666

member

Activity: 68

Merit: 10

Thirtybird. I noticed we're on the same pool. What are you using for --scan-time --expiry?

Topic: [ANN][YAC] Yacminer GPU miner for Yacoin - page 5. (Read 57517 times)