dishwara
Legendary
Offline
Activity: 1855
Merit: 1016
|
|
July 24, 2012, 06:17:25 PM |
|
i used shaders option with this release http://www.mediafire.com/?0ue7860yv89o05y on windows 7 64 bit & getting this error [2012-07-24 23:43:53] cgminer.exe: --shaders: unrecognized option
My bat file is cgminer.exe --scrypt --url http://lc.ozco.in:9332 --userpass xxx:xxx --shaders 1600 -I 13
|
|
|
|
ailikun
|
|
July 24, 2012, 06:30:27 PM |
|
ckolivas just released this new option.
but nobody have compiled a new version of cgminer yet.
|
Komuto Herovato is definitely the chief engineer of bfl)
|
|
|
|
Bigal
|
|
July 24, 2012, 07:23:11 PM Last edit: July 24, 2012, 07:42:00 PM by Bigal |
|
Under Ubuntu 12.04 with 12.6 drivers and sdk with the latest build of cgminer the highest you can set the thread concurrency is 2048 I'm trying to figure why I guess that is the limit in cgminer and not reaper if the kernels are similar?
four 5850s
"intensity" : "11,11,11,11", "vectors" : "1,1,1,1", "worksize" : "128,128,128,128", "kernel" : "scrypt,scrypt,scrypt,scrypt", "gpu-engine" : "0-750,0-700,0-700,0-700", "gpu-memclock" : "1000,1000,1000,1000", "gpu-vddc" : "1.000,0.950,0.950,0.950", "gpu-threads" : "2", "scrypt" : true,
this works perfectly at -I 11 ~675 kh at -I 12 start errors miss-target
I get the same exact results under reaper
worksize 128 aggression 11 threads_per_gpu 2 sharethreads 18 lookup_gap 2 gpu_thread_concurrency 2048
aggression 11 works great no errors ~ 675 kh aggression 12 throws errors
Ok the best results for reaper for me seems to be
worksize 128 aggression 12 threads_per_gpu 2 sharethreads 18 lookup_gap 2 gpu_thread_concurrency 5760
this works great no errors ~1030kh pool reports roughly same
I don't have any 5850s running under windows to seem if the results are the same. The same settings that work on both give nearly identical khs in both programs, but the difference is the thread concurrency maximum of 2048 in cgminer vs. 5760 in reaper? this even make sense lol?
I have a couple 5870s I'm need to test this out on but I'm thinking 4 x shader count is the optimum?
I just noticed that reaper builds the buffer at 360mb @ 5760tc 4 x 360 = 1440
|
|
|
|
foggyb
Legendary
Offline
Activity: 1736
Merit: 1006
|
|
July 24, 2012, 07:25:25 PM |
|
Sweet. Works on 7970 - gets the optimum values automatically.
|
Hey everyone! 🎉 Dive into the excitement with the Gamble Games Eggdrop game! Not only is it a fun and easy-to-play mobile experience, you can now stake your winnings and accumulate $WinG token, which has a finite supply of 200 million tokens. Sign up now using this exclusive referral link! Start staking, playing, and winning today! 🎲🐣
|
|
|
ailikun
|
|
July 24, 2012, 07:50:06 PM |
|
doesnt seem to work right for me.. Each time i try to launch it, my fourth 7970 crashes..
But it works well, with an earlier version
|
Komuto Herovato is definitely the chief engineer of bfl)
|
|
|
pekv2
|
|
July 24, 2012, 08:00:48 PM |
|
|
|
|
|
VelvetLeaf
Member
Offline
Activity: 98
Merit: 10
|
|
July 24, 2012, 08:01:20 PM |
|
Does CGminer-Scrypt support 1400 x Tesla M2050, the card BX use to launch the attack against litecoin network ? How many kH/s you can get with that NVIDIA card ? Is it bigger than 90 kH/s ?
|
BTC : 1GN81dxzxyFPQsyAtdocXr5S9Mcg4wcfFG LTC : LgmYvXsYXc4xdjsMKXJWqtagxVvioK6iaw FC : 6dpSnKMtttUUYzaRu1EB7Lu18PBRVHU3V7
|
|
|
|
pekv2
|
|
July 24, 2012, 08:16:51 PM |
|
Added the --shaders option now - Make the thread concurrency and lookup gap options hidden on the command line and autotune parameters with a newly parsed --shaders option. So you should only need to try --shaders and -I now. Note that any intensity above 13 is a gamble and highly dependent on hardware/software combination as to whether it's better, so -I 13 is a good start. Here's the table again: GPU Processing Elements 7750 512 7770 640 7850 1024 7870 1280 7950 1792 7970 2048
6850 960 6870 1120 6950 1408 6970 1536 6990 (6970x2)
6570 480 6670 480 6790 800
6450 160
5670 400 5750 720 5770 800 5830 1120 5850 1440 5870 1600 5970 (5870x2)
And for those who need me to spell it out, let's say you have a 5830, try this first: --shaders 1120 -I 13 This is horrible for me. 2 5850's. [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit GPU 0: 43.0C 3581RPM | 13.4/ 15.1Kh/s | A:1 R:0 HW:0 U:1.73/m I:13 GPU 1: 46.0C 3410RPM | 50.4/ 53.6Kh/s | A:1 R:0 HW:0 U:1.73/m I:13
cgminer --scrypt -o http://site:port -u username -p password --shaders 1440 --intensity 13 vs 809 khash/s cgminer --scrypt -o http://site:port -u username -p password --worksize 256 --lookup-gap 2 --thread-concurrency 7200 -g 1 --intensity 19
|
|
|
|
passerby
Member
Offline
Activity: 112
Merit: 10
|
|
July 24, 2012, 08:55:55 PM |
|
Okay, maybe I am being painfully slow today but...
1) Litecoin is intended to be a CPU coin, right ?
2) So, from this thread it appears that GPU mining it in a manner that is more economically effective than CPU mining is possible, right ?
But, if both 1 and 2 is true, doesn't that mean that litecoin is kinda...pointless?
|
|
|
|
Luke-Jr
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
July 24, 2012, 09:13:23 PM |
|
Okay, maybe I am being painfully slow today but...
1) Litecoin is intended to be a CPU coin, right ?
2) So, from this thread it appears that GPU mining it in a manner that is more economically effective than CPU mining is possible, right ?
But, if both 1 and 2 is true, doesn't that mean that litecoin is kinda...pointless?
Litecoin is a scam - there is no such thing as a "CPU coin" and never can be. I think Con is only doing this because he's being paid - in Bitcoins https://en.bitcoin.it/wiki/Litecoin#Criticism
|
|
|
|
bitcoiners
|
|
July 24, 2012, 09:18:04 PM |
|
Okay, maybe I am being painfully slow today but...
1) Litecoin is intended to be a CPU coin, right ?
2) So, from this thread it appears that GPU mining it in a manner that is more economically effective than CPU mining is possible, right ?
But, if both 1 and 2 is true, doesn't that mean that litecoin is kinda...pointless?
Litecoin is a scam - there is no such thing as a "CPU coin" and never can be. I think Con is only doing this because he's being paid - in Bitcoins https://en.bitcoin.it/wiki/Litecoin#CriticismWell considering you wrote that. It's totally believable! lol.
|
|
|
|
passerby
Member
Offline
Activity: 112
Merit: 10
|
|
July 24, 2012, 09:32:14 PM |
|
Litecoin is a scam - there is no such thing as a "CPU coin" and never can be.
Could you go into more details on this one ?
|
|
|
|
Luke-Jr
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
July 24, 2012, 09:35:29 PM |
|
Litecoin is a scam - there is no such thing as a "CPU coin" and never can be.
Could you go into more details on this one ? It is impossible to design a proof-of-work that cannot be specialized (eg, ASICs). Designing them to be resistent to existing technologies increases the security risk such specialization presents. Simple proofs like SHA256 (in Bitcoin) have proven to work well, since it scales up in tiers (CPU -> GPU -> FPGA -> ASIC).
|
|
|
|
-ck
Legendary
Offline
Activity: 4256
Merit: 1645
Ruu \o/
|
|
July 24, 2012, 09:37:10 PM |
|
This thread is not the forum for that discussion.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
bitcoiners
|
|
July 24, 2012, 09:42:00 PM |
|
Litecoin is a scam - there is no such thing as a "CPU coin" and never can be.
Could you go into more details on this one ? It is impossible to design a proof-of-work that cannot be specialized (eg, ASICs). Designing them to be resistent to existing technologies increases the security risk such specialization presents. Simple proofs like SHA256 (in Bitcoin) have proven to work well, since it scales up in tiers (CPU -> GPU -> FPGA -> ASIC). Some of you Bitcoin purists really are scared of LTC aren't you? Start your own thread if you'd like to discuss this. I'm sure some would be more than happy to talk. Otherwise STFU.
|
|
|
|
-ck
Legendary
Offline
Activity: 4256
Merit: 1645
Ruu \o/
|
|
July 24, 2012, 11:13:16 PM |
|
Under Ubuntu 12.04 with 12.6 drivers and sdk with the latest build of cgminer the highest you can set the thread concurrency is 2048 I'm trying to figure why I guess that is the limit in cgminer and not reaper if the kernels are similar?
four 5850s
"intensity" : "11,11,11,11", "vectors" : "1,1,1,1", "worksize" : "128,128,128,128", "kernel" : "scrypt,scrypt,scrypt,scrypt", "gpu-engine" : "0-750,0-700,0-700,0-700", "gpu-memclock" : "1000,1000,1000,1000", "gpu-vddc" : "1.000,0.950,0.950,0.950", "gpu-threads" : "2", "scrypt" : true,
this works perfectly at -I 11 ~675 kh at -I 12 start errors miss-target
I get the same exact results under reaper
worksize 128 aggression 11 threads_per_gpu 2 sharethreads 18 lookup_gap 2 gpu_thread_concurrency 2048
aggression 11 works great no errors ~ 675 kh aggression 12 throws errors
Ok the best results for reaper for me seems to be
worksize 128 aggression 12 threads_per_gpu 2 sharethreads 18 lookup_gap 2 gpu_thread_concurrency 5760
this works great no errors ~1030kh pool reports roughly same
I don't have any 5850s running under windows to seem if the results are the same. The same settings that work on both give nearly identical khs in both programs, but the difference is the thread concurrency maximum of 2048 in cgminer vs. 5760 in reaper? this even make sense lol?
I have a couple 5870s I'm need to test this out on but I'm thinking 4 x shader count is the optimum?
I just noticed that reaper builds the buffer at 360mb @ 5760tc 4 x 360 = 1440
cgminer's buffer build, thread concurrency, gap lookup and intensity/aggression work identically to raper so you will get identical buffer results, base performance etc with the same settings. The only thing I do differently is I check for errors when submitting the requests to opencl. You CAN override the upper limit for thread concurrency by just putting it in manually. However what likely happens is the error from the kernel running happens randomly. cgminer does not ignore the errors, whereas raper doesn't even check for them, it just keeps sending the kernel over and over ignoring whether it's working or not. Why linux has lower reported memory limits on this occasion to windows I don't know but I'm guessing it's just the driver differences. I could go in and make it ignore the results of failed kernel queueing, but that's so counter to good programming it's ridiculous. However it seems I have no choice...
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
pekv2
|
|
July 24, 2012, 11:33:54 PM |
|
Added the --shaders option now - Make the thread concurrency and lookup gap options hidden on the command line and autotune parameters with a newly parsed --shaders option. So you should only need to try --shaders and -I now. Note that any intensity above 13 is a gamble and highly dependent on hardware/software combination as to whether it's better, so -I 13 is a good start. Here's the table again: GPU Processing Elements 7750 512 7770 640 7850 1024 7870 1280 7950 1792 7970 2048
6850 960 6870 1120 6950 1408 6970 1536 6990 (6970x2)
6570 480 6670 480 6790 800
6450 160
5670 400 5750 720 5770 800 5830 1120 5850 1440 5870 1600 5970 (5870x2)
And for those who need me to spell it out, let's say you have a 5830, try this first: --shaders 1120 -I 13 This is horrible for me. 2 5850's. [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit GPU 0: 43.0C 3581RPM | 13.4/ 15.1Kh/s | A:1 R:0 HW:0 U:1.73/m I:13 GPU 1: 46.0C 3410RPM | 50.4/ 53.6Kh/s | A:1 R:0 HW:0 U:1.73/m I:13
cgminer --scrypt -o http://site:port -u username -p password --shaders 1440 --intensity 13 vs 809 khash/s cgminer --scrypt -o http://site:port -u username -p password --worksize 256 --lookup-gap 2 --thread-concurrency 7200 -g 1 --intensity 19
|
|
|
|
-ck
Legendary
Offline
Activity: 4256
Merit: 1645
Ruu \o/
|
|
July 24, 2012, 11:52:00 PM |
|
This is horrible for me. 2 5850's. [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit GPU 0: 43.0C 3581RPM | 13.4/ 15.1Kh/s | A:1 R:0 HW:0 U:1.73/m I:13 GPU 1: 46.0C 3410RPM | 50.4/ 53.6Kh/s | A:1 R:0 HW:0 U:1.73/m I:13
cgminer --scrypt -o http://site:port -u username -p password --shaders 1440 --intensity 13 vs 809 khash/s cgminer --scrypt -o http://site:port -u username -p password --worksize 256 --lookup-gap 2 --thread-concurrency 7200 -g 1 --intensity 19 What debugging do you get running it with -D -T and then stopping it before it starts mining about size when you start it with --shaders 1440? Look for messages about buffer, lookup gap and thread concurrency.
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
|