Overclock.net banner

1 - 14 of 14 Posts

·
Registered
Joined
·
179 Posts
Discussion Starter · #1 ·
Currently, I'm mining using clevermining, and using my R9 280X and getting ~475-550Kh/s. I've seen people running 280X's getting easily 700+Kh/s. Not sure why I'm getting such a low rate. Any Ideas? Also, at this current rate, I'm getting about ~$2.40/day with 24/7 mining. Is it worth it to do this with the power cost as well as the wear on my components?

Just looking for input. Thanks.
 

·
Registered
Joined
·
2,506 Posts
Need more information. What are your clocks? What's in your .bat file? What miner are you using?
 

·
Registered
Joined
·
179 Posts
Discussion Starter · #3 ·
Quote:
Originally Posted by battleaxe View Post

Need more information. What are your clocks? What's in your .bat file? What miner are you using?
Slight overclock. 1130MHz on the GPU, 6430MHz memory. Could probably push it further, but I haven't really had time. I'm on spring break from college now so I'll look into it. I'm using cgminer 3.7.2 with the following in my .bat file:

Code:

Code:
cgminer --scrypt -o stratum+tcp://us.clevermining.com:3333  -u 1Dmfvxvr4W1z9nt83uQbWAYHyPauw5jV4m -p x -I 13 -g 2 -w 256 --thread-concurrency 8192
 

·
Registered
Joined
·
2,506 Posts
Put your memory back to 1500 (6000mhz) and start decreasing your core little by little. You will likely see the hashes go up while you do this. Also put -I 18 in place of the -I 13

Start there and see what happens, I'll try to help more tomorrow. Going to bed now.
 

·
Registered
Joined
·
179 Posts
Discussion Starter · #5 ·
Quote:
Originally Posted by battleaxe View Post

Put your memory back to 1500 (6000mhz) and start decreasing your core little by little. You will likely see the hashes go up while you do this. Also put -I 18 in place of the -I 13

Start there and see what happens, I'll try to help more tomorrow. Going to bed now.
Going back to 1070 on the core, 6000 on the memory, and setting intensity to 18, I see that my GPU usage is jumping around more, from like 65-90%. Also, my PC gets laggy, and the mouse jumps around. I imagine this has something to do with the intensity?

EDIT: Let it run at this config for about an hour, as I went to watch a TV show. Came back to 28 hardware errors and a slow hashrate. Changed to 1000 core, 1500 memory, and intensity back to 13, and I'm currently getting ~670Kh/s.
 

·
Registered
Joined
·
1,248 Posts
I have mine slightly underclocked with 1000 core, 1500 mem and 1050 vddc

With these settings

-I 13 -g 2 -w 256 --thread-concurrency 11200

They stay constantly between 690-710 and around 65c
 

·
Registered
Joined
·
179 Posts
Discussion Starter · #7 ·
Quote:
Originally Posted by Rage19420 View Post

I have mine slightly underclocked with 1000 core, 1500 mem and 1050 vddc

With these settings

-I 13 -g 2 -w 256 --thread-concurrency 11200

They stay constantly between 690-710 and around 65c
These settings so far are working well for me, getting 670Kh/s. Haven't tried thread-concurrency at 11200 yet though. Still using 8192. Undervolted to 1150, but not sure how low its safe to go and not sure how to test that.

EDIT: Tried 11200, and it resulted in the same choppiness that gave me 28 hardware errors above, so I'm going to stick with 8192 for now.
 

·
Registered
Joined
·
2,506 Posts
Quote:
Originally Posted by Rage19420 View Post

I have mine slightly underclocked with 1000 core, 1500 mem and 1050 vddc

With these settings

-I 13 -g 2 -w 256 --thread-concurrency 11200

They stay constantly between 690-710 and around 65c
^ This

1000/1500 is a known setting that works well. High OC's don't really help with AMD cards and mining. They do seem to help on Nvidia cards and mining though. Not sure why but I think its just the way the thread depth is written or something on the miner. Nice job.

As Rage said; the next thiing to do is get your voltage as low as you can go stable. Decreasing your power is what its all about once you have your hashes figured.
 

·
Registered
Joined
·
179 Posts
Discussion Starter · #9 ·
Quote:
Originally Posted by battleaxe View Post

^ This

1000/1500 is a known setting that works well. High OC's don't really help with AMD cards and mining. They do seem to help on Nvidia cards and mining though. Not sure why but I think its just the way the thread depth is written or something on the miner. Nice job.

As Rage said; the next thiing to do is get your voltage as low as you can go stable. Decreasing your power is what its all about once you have your hashes figured.
What's the best method for undervolting? Just keep dropping my voltage while mining until my computer locks up, then raise it a bit?
 

·
Registered
Joined
·
2,506 Posts
Quote:
Originally Posted by NV43 View Post

What's the best method for undervolting? Just keep dropping my voltage while mining until my computer locks up, then raise it a bit?
Pretty much.
 

·
Registered
Joined
·
179 Posts
Discussion Starter · #11 ·
Something else I have been meaning to ask about, but not sure it deserves its own thread. Using the settings here:

Code:

Code:
cgminer --scrypt -o stratum+tcp://us.clevermining.com:3333  -u 1Dmfvxvr4W1z9nt83uQbWAYHyPauw5jV4m -p x -I 13 -g 2 -w 256 --thread-concurrency 8192
I keep getting this:

What is the meaning of the "detected new block" lines? Are they supposed to be as frequent as they are? Also, what are the lines saying "rejected untracked stratum" about?

Thanks again.
 

·
Registered
Joined
·
179 Posts
Discussion Starter · #12 ·
Quote:
Originally Posted by NV43 View Post

Something else I have been meaning to ask about, but not sure it deserves its own thread. Using the settings here:

Code:

Code:
cgminer --scrypt -o stratum+tcp://us.clevermining.com:3333  -u 1Dmfvxvr4W1z9nt83uQbWAYHyPauw5jV4m -p x -I 13 -g 2 -w 256 --thread-concurrency 8192
I keep getting this:

What is the meaning of the "detected new block" lines? Are they supposed to be as frequent as they are? Also, what are the lines saying "rejected untracked stratum" about?

Thanks again.
Anyone familiar with this?
 

·
Premium Member
Joined
·
1,850 Posts
The detected new block message is normal, the pool itself is just letting your miner know it is starting work on a new block.

If you're mining on Clevermining, then you can safely ignore the rejected untracked shares, as they do not seem to affect your accepted hashrate

However, AFAIK anywhere else you'd have to check with the pool directly to make sure
Quote:
When cgminer sends shares via stratum, it does not send the share and then wait for the response as this might slow down the sending of other shares. This means that the response back from the pool is processed separately from the share submission (to make the most of a truly multithreaded environment). However there is never a guarantee that the responses come back in the same order you send them. So cgminer stores a copy of each share as it sends it to the server in its own local database of submitted shares. When it gets a response back about that share from the pool, it deletes the copy of that share. Now stratum is meant to be an uninterrupted connection to the pool, and if you lose that connection, it is assumed that your "session" is no longer valid. So if you send some shares and get disconnected before you get a response, cgminer has to assume that those shares have been lost - otherwise it may end up keeping copies of heaps of shares that it will never get a response to and wastes memory. If you manage to reconnect, sometimes the pool will actually tell you "oh by the way those shares are ok" - however cgminer has now thrown out the record of what those shares were and can only say that the pool said a share was accepted or rejected. Then cgminer just says it's an "untracked share"." (c) ckolivas
Also see this thread about your hashrate

---
 

·
Registered
Joined
·
502 Posts
Hey guys, I purchased two Sapphire Dual-X 280Xs, the owner said he flashed the BIOS's to 1.081v vs 1.21v on both cards but I am not getting 700 KH/s, only getting around 580-600

I am using SGMiner 4.1.0

My config:
"intensity" : "13",
"worksize" : "256",
"lookup-gap" : "2",
"thread-concurrency" : "8192",
"gpu-engine" : "1000",
"gpu-memclock" : "1500",
"temp-cutoff" : "90",
"expiry" : "1",
"failover-only" : true,
"log" : "5",
"queue" : "0",
"scan-time" : "1",
"shaders" : "2048,",
"device" : "0",
"gpu-threads" : "2"
 
1 - 14 of 14 Posts
Top