It looks like 1000kh/s is possible with higher clocks.
What is your settings?
Topic: AMD R9 290X? - page 11. (Read 108823 times)
What is your settings?
It looks like 1000kh/s is possible with higher clocks.
Screenshot?
It looks like 1000kh/s is possible with higher clocks.
My best setting so far is 882KH/s. 920/1500 TC 32765 -g 1. Still havent had time to mess with -g 2, but the only way I can get -g 2 to work without hw errors at 800kh/s or more is with TC at 22550ish or higher. -g 2 needs intensity of 19 or 20 with this card, not 13 like a 7970. These don't configure like previous cards at all.
Running 880 now with those clocks.
My best setting so far is 882KH/s. 920/1500 TC 32765 -g 1. Still havent had time to mess with -g 2, but the only way I can get -g 2 to work without hw errors at 800kh/s or more is with TC at 22550ish or higher. -g 2 needs intensity of 19 or 20 with this card, not 13 like a 7970. These don't configure like previous cards at all.
So according to reamde I should try 2816 x 4 and 5 = 11264 14080 tc. Low results here.
If my math isn't off the overclockers guy uses shaders x 11.63 ish and thats way off according to readme.
The readme don't always apply 100% (sometimes way off) to find the sweet spot. I am wrong here?
Can cards really differ this much or is this a problem with win 8.1 and or AMD drivers??
If my math isn't off the overclockers guy uses shaders x 11.63 ish and thats way off according to readme.
The readme don't always apply 100% (sometimes way off) to find the sweet spot. I am wrong here?
Can cards really differ this much or is this a problem with win 8.1 and or AMD drivers??
From the scrypt readme
Quote
--thread-concurrency:
This tunes the optimal size of work that scrypt can do. It is internally tuned
by cgminer to be the highest reasonable multiple of shaders that it can
allocate on your GPU. Ideally it should be a multiple of your shader count.
vliw5 architecture (R5XXX) would be best at 5x shaders, while VLIW4 (R6xxx and
R7xxx) are best at 4x. Setting thread concurrency overrides anything you put
into --shaders and is ultimately a BETTER way to tune performance.
SUMMARY: Spend lots of time finding the highest value that your device likes
and increases hashrate.
This tunes the optimal size of work that scrypt can do. It is internally tuned
by cgminer to be the highest reasonable multiple of shaders that it can
allocate on your GPU. Ideally it should be a multiple of your shader count.
vliw5 architecture (R5XXX) would be best at 5x shaders, while VLIW4 (R6xxx and
R7xxx) are best at 4x. Setting thread concurrency overrides anything you put
into --shaders and is ultimately a BETTER way to tune performance.
SUMMARY: Spend lots of time finding the highest value that your device likes
and increases hashrate.
Quote
---
TUNING AN AMD RADEON 7970
Example tuning a 7970 for Scrypt mining:
On linux run this command:
export GPU_MAX_ALLOC_PERCENT=100
or on windows this:
setx GPU_MAX_ALLOC_PERCENT 100
in the same console/bash/dos prompt/bat file/whatever you want to call it,
before running cgminer.
First, find the highest thread concurrency that you can start it at. They should
all start at 8192 but some will go up to 3 times that. Don't go too high on the
intensity while testing and don't change gpu threads. If you cannot go above
8192, don't fret as you can still get a high hashrate.
Delete any .bin files so you're starting from scratch and see what bins get
generated.
First try without any thread concurrency or even shaders, as cgminer will try to
find an optimal value
cgminer -I 13
If that starts mining, see what bin was generated, it is likely the largest
meaningful TC you can set.
Starting it on mine I get:
scrypt130302Tahitiglg2tc22392w64l8.bin
See tc22392 that's telling you what thread concurrency it was. It should start
without TC parameters, but you never know. So if it doesn't, start with
--thread-concurrency 8192 and add 2048 to it at a time till you find the highest
value it will start successfully at.
TUNING AN AMD RADEON 7970
Example tuning a 7970 for Scrypt mining:
On linux run this command:
export GPU_MAX_ALLOC_PERCENT=100
or on windows this:
setx GPU_MAX_ALLOC_PERCENT 100
in the same console/bash/dos prompt/bat file/whatever you want to call it,
before running cgminer.
First, find the highest thread concurrency that you can start it at. They should
all start at 8192 but some will go up to 3 times that. Don't go too high on the
intensity while testing and don't change gpu threads. If you cannot go above
8192, don't fret as you can still get a high hashrate.
Delete any .bin files so you're starting from scratch and see what bins get
generated.
First try without any thread concurrency or even shaders, as cgminer will try to
find an optimal value
cgminer -I 13
If that starts mining, see what bin was generated, it is likely the largest
meaningful TC you can set.
Starting it on mine I get:
scrypt130302Tahitiglg2tc22392w64l8.bin
See tc22392 that's telling you what thread concurrency it was. It should start
without TC parameters, but you never know. So if it doesn't, start with
--thread-concurrency 8192 and add 2048 to it at a time till you find the highest
value it will start successfully at.
Try this:
-setx GPU_MAX_ALLOC_PERCENT 100
-setx GPU_USE_SYNC_OBJECTS 1
cgminer --scrypt -o -u -p -I 20 --thread-concurrency 8191 --worksize 256 -g 2 --lookup-gap 0
-setx GPU_MAX_ALLOC_PERCENT 100
-setx GPU_USE_SYNC_OBJECTS 1
cgminer --scrypt -o -u -p -I 20 --thread-concurrency 8191 --worksize 256 -g 2 --lookup-gap 0
840 with a lot of hw error.
I don't know 100% the blue screen is related to the tc. When i play with cgminer (start and stopping) the driver may stop responding and I need to reboot and the occasional bluescreen. But if I reboot and start cgminer and let it run = no problems.
Oh my bad, try that with higher TC...was a bit sleepy. :p
No good results
.What is the correct way to calculate the tc?
Try this:
-setx GPU_MAX_ALLOC_PERCENT 100
-setx GPU_USE_SYNC_OBJECTS 1
cgminer --scrypt -o -u -p -I 20 --thread-concurrency 8191 --worksize 256 -g 2 --lookup-gap 0
-setx GPU_MAX_ALLOC_PERCENT 100
-setx GPU_USE_SYNC_OBJECTS 1
cgminer --scrypt -o -u -p -I 20 --thread-concurrency 8191 --worksize 256 -g 2 --lookup-gap 0
840 with a lot of hw error.
I don't know 100% the blue screen is related to the tc. When i play with cgminer (start and stopping) the driver may stop responding and I need to reboot and the occasional bluescreen. But if I reboot and start cgminer and let it run = no problems.
Oh my bad, try that with higher TC...was a bit sleepy. :p
Try this:
-setx GPU_MAX_ALLOC_PERCENT 100
-setx GPU_USE_SYNC_OBJECTS 1
cgminer --scrypt -o -u -p -I 20 --thread-concurrency 8191 --worksize 256 -g 2 --lookup-gap 0
-setx GPU_MAX_ALLOC_PERCENT 100
-setx GPU_USE_SYNC_OBJECTS 1
cgminer --scrypt -o -u -p -I 20 --thread-concurrency 8191 --worksize 256 -g 2 --lookup-gap 0
840 with a lot of hw error.
I don't know 100% the blue screen is related to the tc. When i play with cgminer (start and stopping) the driver may stop responding and I need to reboot and the occasional bluescreen. But if I reboot and start cgminer and let it run = no problems.
Still waiting for more info about the non x...
Try this:
-setx GPU_MAX_ALLOC_PERCENT 100
-setx GPU_USE_SYNC_OBJECTS 1
cgminer --scrypt -o -u -p -I 20 --thread-concurrency 8191 --worksize 256 -g 2 --lookup-gap 0
-setx GPU_MAX_ALLOC_PERCENT 100
-setx GPU_USE_SYNC_OBJECTS 1
cgminer --scrypt -o -u -p -I 20 --thread-concurrency 8191 --worksize 256 -g 2 --lookup-gap 0
Hmm, that's strange. I've never seen a bluescreen from too much TC, usually I just get a memory error before mining even starts.
My 7970's/280x like 4x shaders for a TC, you may try that. They won't do anything at all with any higher TC though, not with two threads. I wonder if the beta drivers for the 290x are different than the 280x ones?
My 7970's/280x like 4x shaders for a TC, you may try that. They won't do anything at all with any higher TC though, not with two threads. I wonder if the beta drivers for the 290x are different than the 280x ones?
28160 = 550
30976 = 20
But cgwatcher reported 0.
Also got bluescreen 3 times in 5 minutes while running and testing these tc.
30976 = 20
But cgwatcher reported 0.
Also got bluescreen 3 times in 5 minutes while running and testing these tc.
If it starts mining than the TC is good. You'll see an error if it is unable to mine with a certain TC. How did you find that number though? I was under the assumption that it should be a multiple of shader cores.
What does this do?
-setx GPU_MAX_ALLOC_PERCENT 100
-setx GPU_USE_SYNC_OBJECTS 1
cgminer --scrypt -o -u -p -I 13 --shaders 2816 --thread-concurrency 28160 --worksize 256 -g 2 --lookup-gap 2 --gpu-engine 1000 --gpu-memclock 1250
You may try a TC of 30976, too.
What does this do?
-setx GPU_MAX_ALLOC_PERCENT 100
-setx GPU_USE_SYNC_OBJECTS 1
cgminer --scrypt -o -u -p -I 13 --shaders 2816 --thread-concurrency 28160 --worksize 256 -g 2 --lookup-gap 2 --gpu-engine 1000 --gpu-memclock 1250
You may try a TC of 30976, too.
What about power consumption of new R9 290(X), are there any data for khs/W ratio?
tc maxed out at around 32768 but nothing produced more then around 550 khash.
How long do I need to test each tc?
How long do I need to test each tc?
1000/1250 right!
Around 800 khash with 1000/1500 stopped at my "golden ration" 1000/1420 on the way up but only around 700.
Testing -g 2 now.
Around 800 khash with 1000/1500 stopped at my "golden ration" 1000/1420 on the way up but only around 700
.Testing -g 2 now.
Weird!
When at g2 what are you using for an intensity? I'd stay at i13 when g2, and 17-20 with g1. That seems to work really well on 78xx and 79xx cards, at least.
For fun I'd set the memory to 1.3-1.6 of stock core clock and see what that does, may just crash. Stock is 1000/1250, right?
When at g2 what are you using for an intensity? I'd stay at i13 when g2, and 17-20 with g1. That seems to work really well on 78xx and 79xx cards, at least.
For fun I'd set the memory to 1.3-1.6 of stock core clock and see what that does, may just crash. Stock is 1000/1250, right?
This clock setting seems to be my "golden ratio". I have played BF4 with 5% overclock for about an hour no crashes. (BF4 does intermittently seem to crash for everyone including me).
So the only reason I down clock is that with for instance stock clock I get 740 khash......
Using setx commands.
When trying some standard configs for -g 2 I get shares rejected and hw errors. Will play with it a little tonight.
So the only reason I down clock is that with for instance stock clock I get 740 khash......
Using setx commands.
When trying some standard configs for -g 2 I get shares rejected and hw errors. Will play with it a little tonight.
Jump to: