|
|
rbdrbd
|
|
July 01, 2013, 04:51:35 PM |
|
Thank you, trying it out now.
|
|
|
|
|
mikaelh (OP)
|
|
July 01, 2013, 05:36:02 PM |
|
I have no interest in Ybcoin since it's simply a clone of Yacoin for the Chinese market. Looks like the only thing one would have to change is the calculation of the Nfactor. No doubt someone has already figured that out and is happily mining at 10 Mh/s. Someone else can release a miner for Ybcoin if they want.
|
|
|
|
azwccc
|
|
July 01, 2013, 05:44:20 PM |
|
Links for x86 and x64 versions from mega are the same?
|
Bitrated user: azwccc.
|
|
|
|
mikaelh (OP)
|
|
July 01, 2013, 05:56:20 PM |
|
Links for x86 and x64 versions from mega are the same?
Oops, fixed. Thanks for pointing it out!
|
|
|
|
tomtommy
|
|
July 01, 2013, 06:21:12 PM |
|
+1
Thank You.
|
|
|
|
Moray
|
|
July 01, 2013, 06:38:40 PM |
|
Hm-m, this one is even faster than previous?!? Great work, thank's for sharing!
|
|
|
|
forsetifox
|
|
July 01, 2013, 07:19:15 PM |
|
Thanks Mike. That block spam is hella annoying.
|
|
|
|
eule
|
|
July 02, 2013, 12:48:58 AM |
|
This is amazing, getting 84 kH/s with my good old 5770, these are my settings (not sure if best): yacminer.exe --scrypt -w 64 -I 18 --lookup-gap 2 --thread-concurrency 5120 -g 1 -o http://yacpool.tk:8838 -u Y9JG2HQNMEc3N8nfPdJzT51xwKoQSzZSBJ -p x
|
|
|
|
Eli0t
|
|
July 02, 2013, 01:12:54 AM |
|
"No more spam about blocks being found all the time." very nice
|
LTC: LKpJf3uk7KsHU73kxq8iFJrP1AAKN7Yni7 DGC: DKXGvEbj3Rwgrm2QQbRyNPDDZDYoq4Y44d XPM: AWV5AKfLFyoBaMjg9C77rGUBhuFxz5DGGL
|
|
|
djkakadu
Newbie
Offline
Activity: 11
Merit: 0
|
|
July 02, 2013, 09:46:19 AM |
|
With this settings i have a 123kh/s on 7790. Amazing !
|
|
|
|
azwccc
|
|
July 02, 2013, 07:23:50 PM |
|
I have no interest in Ybcoin since it's simply a clone of Yacoin for the Chinese market. Looks like the only thing one would have to change is the calculation of the Nfactor. No doubt someone has already figured that out and is happily mining at 10 Mh/s. Someone else can release a miner for Ybcoin if they want. Hi Mike, I am new to the code. Is the script.c or script-chacha.cl I need to modify? Thanks,
|
Bitrated user: azwccc.
|
|
|
Mapuo
|
|
July 03, 2013, 12:31:44 PM |
|
I have only 111 kh/s with my 7850
|
|
|
|
paulthetafy
|
|
July 03, 2013, 12:43:55 PM |
|
Hey mikaelh, are you looking into the ways around keeping GPU's usable after the Aug N++? Or is that something hanzac might be doing? Or neither?
|
|
|
|
mikaelh (OP)
|
|
July 03, 2013, 02:08:02 PM |
|
Hey mikaelh, are you looking into the ways around keeping GPU's usable after the Aug N++? Or is that something hanzac might be doing? Or neither? Well, let's re-iterate this once more. GPU mining is not going to magically stop at N = 8192. My miner should survive it just fine. I'm not going to benchmark it because people always keep finding new settings after N changes. Some people will use a higher lookup gap and others will find ways to use lower values. I might come up with some new tricks but at the moment I'm pretty happy how the code scales with the lookup gap.
|
|
|
|
paulthetafy
|
|
July 03, 2013, 03:37:37 PM |
|
Hey mikaelh, are you looking into the ways around keeping GPU's usable after the Aug N++? Or is that something hanzac might be doing? Or neither? Well, let's re-iterate this once more. GPU mining is not going to magically stop at N = 8192. My miner should survive it just fine. I'm not going to benchmark it because people always keep finding new settings after N changes. Some people will use a higher lookup gap and others will find ways to use lower values. I might come up with some new tricks but at the moment I'm pretty happy how the code scales with the lookup gap. My apologies, I thought I understood the way it works but obviously not. I thought that the RAM on the GPU was the limitation and this couldn't be overcome. I'm not sure I understand the lookup gap / TC correlation and the use of GPU RAM vs system RAM.
|
|
|
|
mikaelh (OP)
|
|
July 03, 2013, 04:08:22 PM |
|
Hey mikaelh, are you looking into the ways around keeping GPU's usable after the Aug N++? Or is that something hanzac might be doing? Or neither? Well, let's re-iterate this once more. GPU mining is not going to magically stop at N = 8192. My miner should survive it just fine. I'm not going to benchmark it because people always keep finding new settings after N changes. Some people will use a higher lookup gap and others will find ways to use lower values. I might come up with some new tricks but at the moment I'm pretty happy how the code scales with the lookup gap. My apologies, I thought I understood the way it works but obviously not. I thought that the RAM on the GPU was the limitation and this couldn't be overcome. I'm not sure I understand the lookup gap / TC correlation and the use of GPU RAM vs system RAM. It's pretty hard to discuss the details of lookup gap without explaining the entire scrypt algorithm first. I did write a bit about lookup gap on the other forum: http://yacointalk.com/index.php/topic,350.msg1511.html#msg1511The miner allocates the scratchpad from GPU memory. You may need enough system RAM to support that, but that's a driver issue.
|
|
|
|
|