Author

Topic: Low Reported Hashrate with LTC mining (Read 1658 times)

newbie
Activity: 16
Merit: 0
April 08, 2013, 01:05:05 AM
#4
ok after some research thru the forums
I installed cgminer into a new folder and I running it seperate than my BTC one, not sure why but requires a tiny space so

added the 2 commands to the .bat file

Code:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1

ran cgminer for a few minutes and got my thread concurrency from the .bin file name

now coinotron is reporting ~560KH/s much greater than 80KH/s

tweaking my gpu and memory speeds and now my rig is using 4gbs of system ram
member
Activity: 84
Merit: 10
April 08, 2013, 12:12:35 AM
#3
Litecoin has a more complex hashing algorithm than bitcoin, so a lower hash rate is normal.
newbie
Activity: 16
Merit: 0
April 08, 2013, 12:03:34 AM
#2
I am getting the same types of results when I switch from BTC mining with cgminer to LTC mining.
On my test machine with 1 7950 cgminer shows 630KH/sec but coinotron, notroll, and kattare all show no higher than 80KH/s
hero member
Activity: 682
Merit: 500
March 06, 2013, 11:16:44 PM
#1
I'm not 100% sure if this is the place to put a thread like this (pools section, or alt. currencies section), but either way I hope you fellas can help me out.

I just recently switched over to LTC mining on my remaining GPU's because the BTC difficulty has been going no where but up. I've got a 5850 and a 5830 running. Together they report 550-600khash/sec, which I've seen to be in the ball park of where they should be at roughly stock clocks. I'm mining with cgminer 2.10.5, and the pool I'm using is notroll.in. So the mining end of the operation appears to be working flawlessly. However, when I check my account details and such at the pool's website, I have never seen a reported hashrate over 125khash/s. This issue was happening when I mined at litecoinpool.org as well. According to the calculator on their sites, I should be in the neighborhood of 15LTC/day. But I've been 3-4LTC/day instead, so the hashrate online isn't being reported wrong.

I was wondering if anyone else had seen this, or if they had any ideas on how to fix this. Thanks in advance!
Jump to: