ATTN Litecoin GPU Miners - Scrypt support for cgminer

[bitlane]

Here is info from the Litecoincash pool thread...

Speeds are now back to something more usual staying a bit higher as we setup 21 target

Test period is over and pool running smotly now, with a BIG luck for now

So 21 * 71 = 1491 shares per minute. 1491 divided by 5 cards is 298 utility. That's almost exactly what I'm getting.

Lost in translation... kh vs kh that is.....

If that's the case, CGMiner is RIGHT on target.... Ya ?

[1713864353]

1713864353

[1713864353]

1713864353

[pooler]

Here is info from the Litecoincash pool thread...

Speeds are now back to something more usual staying a bit higher as we setup 21 target

Translated to English: they use a target with 21 trailing zeros (in binary notation), i.e. in hex
0x000007ffffffffffffffffffffffffffffffffffffffffffffffffffffffffff (big endian)

This is the lowest target I've seen so far on a Litecoin pool.

[bitlane]

Sorry...

The 'Lost in translation' I was referring to was Reaper's Local Hash Rate vs CGminer's Local Hash Rates being different, yet VERY similar Submission Rates.
(if it is simply a math problem, or share difficulty issue and reporting)

[-ck]

Sorry...

The 'Lost in translation' I was referring to was Reaper's Local Hash Rate vs CGminer's Local Hash Rates being different, yet VERY similar Submission Rates.
(if it is simply a math problem, or share difficulty issue and reporting)

What hashrate does your pool report you submitting?

[foggyb]

I'm mining at notroll.in pool. It reports very close to what reaper is showing.

[bitlane]

Sorry...

The 'Lost in translation' I was referring to was Reaper's Local Hash Rate vs CGminer's Local Hash Rates being different, yet VERY similar Submission Rates.
(if it is simply a math problem, or share difficulty issue and reporting)

What hashrate does your pool report you submitting?

The pool reports me accurately with slight peaks and valleys for luck, ~ 9.5 MH/s total

That is:
- 15x 7970 (approx 500+ kh/each)
- 3x 5830 (820 kh/3....single rig)
- 2x 5770 (400 kh/2....same rig)
- 1x 6950 (395 kh/s)

=======================================
MINER1 (2.15 MH/s)
----------------------
4x 7970 @ 925/925, 1040mV

worksize 256
aggression 13
threads_per_gpu 5
sharethreads 18
lookup_gap 2
gpu_thread_concurrency 10240

=======================================
MINER2 (2.15 MH/s)
---------------------
4x 7970 @ 925/925, 1040mV

worksize 256
aggression 13
threads_per_gpu 5
sharethreads 18
lookup_gap 2
gpu_thread_concurrency 10240

=======================================
MINER3 (2.61 MH/s)
----------------------
5x 7970 @ 925/925, 1040mV

worksize 256
aggression 13
threads_per_gpu 5
sharethreads 18
lookup_gap 2
gpu_thread_concurrency 10240

=======================================
MINER4 (820 KH/s)
--------------------
3x 5830 @ 840/800, 1055mV

worksize 128
aggression 17
threads_per_gpu 2
sharethreads 18
lookup_gap 2
gpu_thread_concurrency 6144

=======================================
MINER5 (395 MH/s + 980 MH/s + 400 MH/s)
---------------------------------------
1x 6950 @ 800/800, 1000mV
2x 7970 @ 900/900, 1000mV
2x 5770 @ 850/1200, 1050mV

worksize 256 (6950)
aggression 18
threads_per_gpu 2
sharethreads 18
lookup_gap 2
gpu_thread_concurrency 8192

----------------------------
worksize 256 (7970)
aggression 13
threads_per_gpu 5
sharethreads 18
lookup_gap 2
gpu_thread_concurrency 10240

----------------------------
worksize 128 (5770)
aggression 17
threads_per_gpu 1
sharethreads 18
lookup_gap 2
gpu_thread_concurrency 6144

[xurious]

not all of us have 7000 series cards so plz test with 5000 and 6000 series cards also can this be released for us to test and can you make it for windows

were not all linux buffs

Hang on a sec while I pull all that hardware out of my arse....

Oh wait, I don't have any of those in there.

I can let you have root ssh access to whichever flavor of linux you choose to a box with either a 5770, 58xx, and/or 6950 if this helps your testing.

Edit: You can simply put your code in a RAM drive and change root password if you are worried about me seeing the code.

[kano]

Atm the reaper opencl code sucks. My 5870 generates about 420kh/s, to use as a reference. So it should be getting like 6-700 or more from a 7970.

But how many accepted shares does it generate at that alleged hashrate?

According to the pool, about 55k accepted since the night of July 18th ( almost 3 days now) but I also game on this box. I also have a tri 5970 rig that has 250k+ accepted shares. I've found that the thread concurrency switch in reaper has a lot to do with stales/invalids. Also the calculated pool speed is usually +/- 10% of 420, right now at 436.

keep in mind, scrypt was intentionally gpu hostile.  you cannot extrapolate what one gpu 'might' or 'should' get because another is getting x  this is not btc mining.
...

Yes well as everyone knows ... it was supposedly impossible to GPU mine Scrypt faster than CPU with N=1024,p=1,r=1 -> 128KiB
September 28, 2011
https://bitcointalk.org/index.php?topic=45849.msg548778#msg548778

Edit: of course that link above - 3 posts later - shows ArtForz saying he wrote a scrypt GPU miner back in September last year ...........

Though I had a few pages of discussion on the subject of generic GPU vs CPU mining even before that ...
September 17, 2011 starting here:
https://bitcointalk.org/index.php?topic=44423.msg530426#msg530426
That all turned out to be a load of crap also

[Tittiez]

Are you running the cards all on the same rig?  LTC mining is GPU memory bandwidth intensive, if all 4 cards are running at only 1x or 4x or even 8x you'll probably be bottlenecked.

Try using only one GPU in running at 16x.

I have my 5770 on an x1 and it's mining ~200kh/s just fine.

[Tittiez]

Lots of configs

Hey, try setting all the ones that are at 6144 to 7144, it increases my hashrate.

[tacotime]

Are you running the cards all on the same rig?  LTC mining is GPU memory bandwidth intensive, if all 4 cards are running at only 1x or 4x or even 8x you'll probably be bottlenecked.

Try using only one GPU in running at 16x.

I have my 5770 on an x1 and it's mining ~200kh/s just fine.

So memory bandwidth has nothing to do with it, at least over the southbridge...  Someone should really post a chart that plots performance in kh/s with the speed of the memory for the GPU.  I'm really wondering if it's linear or not.  This implementation of scrypt is small enough to be done in the L2 cache, so I have always been wondering how the GPU implementation required megabytes.  I wish someone would break down the algorithm for us or something, but I guess it's in the source code.

[kano]

Are you running the cards all on the same rig?  LTC mining is GPU memory bandwidth intensive, if all 4 cards are running at only 1x or 4x or even 8x you'll probably be bottlenecked.

Try using only one GPU in running at 16x.

I have my 5770 on an x1 and it's mining ~200kh/s just fine.

So memory bandwidth has nothing to do with it, at least over the southbridge...  Someone should really post a chart that plots performance in kh/s with the speed of the memory for the GPU.  I'm really wondering if it's linear or not.  This implementation of scrypt is small enough to be done in the L2 cache, so I have always been wondering how the GPU implementation required megabytes.  I wish someone would break down the algorithm for us or something, but I guess it's in the source code.

N=1024,p=1,r=1 -> 128KiB
i.e. each thread requires 128K or RAM
e.g. in a GPU with 128 parallel processes running at the same time that 128KiB each becomes 16MB

[-ck]

Oh I'm not afraid of putting the code up public. I'm just wary of putting broken code up there and getting lots of people trying it and starting to file meaningless bug reports when the code is in massive flux. I was planning on putting it up shortly anyway.

[wknight]

Oh I'm not afraid of putting the code up public. I'm just wary of putting broken code up there and getting lots of people trying it and starting to file meaningless bug reports when the code is in massive flux. I was planning on putting it up shortly anyway.

Take your time.. no need to rush code when you are making sooooo many changes.

[Graet]

Oh I'm not afraid of putting the code up public. I'm just wary of putting broken code up there and getting lots of people trying it and starting to file meaningless bug reports when the code is in massive flux. I was planning on putting it up shortly anyway.

Take your time.. no need to rush code when you are making sooooo many changes.

+50hundred

none of the people that have said how "easy" it is have done anything (but I guess 99.9% of them never tried )  - conman is actually working hard at this
a little patience people

lmao @ ppl demanding btc back when code isnt even finished being written . oh sorry "threatening". way to encourage work....NOT

[smoothie]

Oh I'm not afraid of putting the code up public. I'm just wary of putting broken code up there and getting lots of people trying it and starting to file meaningless bug reports when the code is in massive flux. I was planning on putting it up shortly anyway.

Take your time.. no need to rush code when you are making sooooo many changes.

+50hundred

none of the people that have said how "easy" it is have done anything (but I guess 99.9% of them never tried )  - conman is actually working hard at this
a little patience people

lmao @ ppl demanding btc back when code isnt even finished being written . oh sorry "threatening". way to encourage work....NOT

+1....."i'll pledge x btc.......wait........gimme my btc back u f*g since you didn't finish the code faster!"

[-ck]

Okay, how's this looking now    Note, mining at higher difficulty 20 on ozcoin.

Code:

 cgminer version 2.5.0 - Started: [2012-07-21 14:15:53]
--------------------------------------------------------------------------------
 (5s):2213.6 (avg):2076.3 Kh/s | Q:78  A:470  R:5  HW:0  E:603%  U:111.9/m
 TQ: 2  ST: 3  SS: 0  DW: 61  NB: 5  LW: 3253  GF: 0  RF: 0
 Connected to http://lc.ozco.in with LP as user ckolivas.0
 Block: a8a8f3d4efcb35dfeac6906cf49b15a3...  Started: [14:19:34]
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU  0:  63.0C 5356RPM | 553.6/535.1Kh/s | A:131 R:3 HW:0 U:  31.20/m I:13
 GPU  1:  61.0C 5429RPM | 537.1/519.3Kh/s | A:120 R:2 HW:0 U:  28.58/m I:13
 GPU  2:  59.0C 5325RPM | 540.1/522.9Kh/s | A:112 R:0 HW:0 U:  26.68/m I:13
 GPU  3:  55.0C 5308RPM | 573.5/529.9Kh/s | A:110 R:0 HW:0 U:  26.20/m I:13
--------------------------------------------------------------------------------

[foggyb]

Now we're talking. Good work. Hopefully there's more headroom left.

To the haters: nothing wrong with setting the bar high. You'd all be unhappy if ckolivas released a miner that was slower or the same speed as reaper. Don't be hypocrites.

[Tittiez]

Okay, how's this looking now    Note, mining at higher difficulty 20 on ozcoin.

Code:

 cgminer version 2.5.0 - Started: [2012-07-21 14:15:53]
--------------------------------------------------------------------------------
 (5s):2213.6 (avg):2076.3 Kh/s | Q:78  A:470  R:5  HW:0  E:603%  U:111.9/m
 TQ: 2  ST: 3  SS: 0  DW: 61  NB: 5  LW: 3253  GF: 0  RF: 0
 Connected to http://lc.ozco.in with LP as user ckolivas.0
 Block: a8a8f3d4efcb35dfeac6906cf49b15a3...  Started: [14:19:34]
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU  0:  63.0C 5356RPM | 553.6/535.1Kh/s | A:131 R:3 HW:0 U:  31.20/m I:13
 GPU  1:  61.0C 5429RPM | 537.1/519.3Kh/s | A:120 R:2 HW:0 U:  28.58/m I:13
 GPU  2:  59.0C 5325RPM | 540.1/522.9Kh/s | A:112 R:0 HW:0 U:  26.68/m I:13
 GPU  3:  55.0C 5308RPM | 573.5/529.9Kh/s | A:110 R:0 HW:0 U:  26.20/m I:13
--------------------------------------------------------------------------------

Much better!

[ThiagoCMC]

kH or Kh... It does matter?!