Expected Hashrate and current profitability
-
Thank you. The hashrate detected by the pool is updating now approximately as it should. The pool displays 960kh/s, I’m counting 1030kh/s.
With the commands “-g 1,1 --lookup-gap 2,2 --expiry=15 --queue=0” cgminer was not working so I removed those arguments by the trial and error method for now.
I also added Parameters for better managing and balancing the heat on the respective GPUs, I’m save below 80°C:
–auto-gpu --auto-fan --gpu-dyninterval 5 --gpu-powertune 10,10 --gpu-engine 1050-1085,900-925 --gpu-memclock 1400,1250 --temp-target 65 --gpu-fan 45-99 -
Ending the Qt Clients (wallets) and now above 1Mh/s displayed in the pool.
Let’s see how the payouts come up as expected. -
You’re very welcome. :))
Apologies for the commands that did not work – I was unable to test them as I don’t have access to a setup with multiple GPUs like yours at them moment. I’m guessing maybe it doesn’t like the double "1"s in the “-g” command, maybe only one is necessary.
(EDIT: reviewed the readme file, it seems “-g 1” is correct, NOT “-g 1,1” … I’ve modified my previous post to reflect this, sorry about that!)Your temperature management/clockspeed settings look good to me, but I’m not really an expert on that part of cgminer (I do all clockspeed and fan control settings with MSI Afterburner).
Glad to see things are now working more as expected. Best of luck in collecting coins! :)
-
Hey, sorry to highjack this thread but I’ve got a similar problem
cgminer says i get about 40-50kh/s (i only have a 4850 and using intensity 10, don’t laugh :P)
but featherpool.com says i only hvae 7kh/s :SI read what you suggested before Nadeah, but i don’t understand that stuff too well haha my cgminer is all set up with cgminer.conf so I don’t think I have to do any of that command line stuff, I just run cgminer.exe and stuff happens lol
this is what I’ve got in cgminer.conf:{
“pools” : [
{
“url” : “http://featherpool.com:9999”,
“user” : “anbo369.1”,
“pass” : “12345”
}
]
,
“intensity” : “10”,
“vectors” : “1”,
“worksize” : “256”,
“kernel” : “scrypt”,
“lookup-gap” : “0”,
“thread-concurrency” : “0”,
“shaders” : “800”,
“gpu-engine” : “0-0”,
“gpu-fan” : “0-85”,
“gpu-memclock” : “0”,
“gpu-memdiff” : “0”,
“gpu-powertune” : “0”,
“gpu-vddc” : “0.000”,
“temp-cutoff” : “95”,
“temp-overheat” : “85”,
“temp-target” : “75”,
“api-port” : “4028”,
“expiry” : “120”,
“gpu-dyninterval” : “7”,
“gpu-platform” : “0”,
“gpu-threads” : “1”,
“hotplug” : “5”,
“log” : “5”,
“no-pool-disable” : true,
“queue” : “1”,
“scan-time” : “60”,
“scrypt” : true,
“temp-hysteresis” : “3”,
“shares” : “0”,
“kernel-path” : “/usr/local/bin”
}thanks for reading :P
-
Hi anbo,
Nothing wrong with 50KH/s, all we can do is make the best of what we’ve got! ;)
You’re right; since you’re using a configuration file you won’t need to specify all of these settings on the command line. Taking a quick look at your config file, I don’t see anything glaringly wrong. I wonder, what is your number of accepts/rejects (or the rate) in cgminer? It could be that the pool is rejecting a large number of your shares. Are you getting any hardware errors?
If hardware errors are the issue, you’ll need to do a bit of tweaking between the intensity and thread-concurrency and possibly clockspeeds/voltages. If that’s not the case, but you’re getting a high number of rejects, the pool could be the problem. Try dropping the “expiry” setting down to 10 or 15 and see if anything improves. Also, try some other pools.
If your reject/stale rate is low but pools are still showing your hashrate low then please post a screenshot of cgminer, if you could, after at least ~15-30minutes of mining – I’d be interested to see what it shows. I’m honestly not sure what the problem might be in that case, sorry. :(
Best of luck in getting the issue sorted!
-
Thanks for the reply! Haven’t had any hardware problems so I guess that isn’t the issue, but I do get some rejects/stales. (not sure how many is considered a lot)
I’ll run it tomorrow while i’m at uni, then I’ll post a screen shot :D
-
Hi all :)
If somebody knows how to mine FC on ATI Radeon HD4730 please help. I’m using 11.2driver+SDK 2.3. I was tryed all versions ATI drivers from 11.2 to 13.1 (18 different versions) but GPU-Z detects OpenCL only with 11.2 driver + SDK 2.3 installed. When i start cgminer with -n it shows: ATI RV770 OpenCL 1.1 ATI-Stream-v2.3
I’m starting start “featherpool.com.bat” with
setx GPU_MAX_ALLOC_PERCENT 100
cgminer -T
and in my cgminer.conf:
{
“pools” : [
{
“url” : “http://featherpool.com:9999”,
“user” : “onik1318.1”,
“pass” : “x”
}
]
,
“intensity” : “8”,
“worksize” : “128”,
“lookup-gap” : “2”,
“shaders” : “640”,
“expiry” : “30”,
“gpu-dyninterval” : “7”,
“gpu-platform” : “0”,
“gpu-threads” : “1”,
“log” : “5”,
“queue” : “1”,
“scan-time” : “60”,
“scrypt” : true,
“shares” : “0”,
“kernel-path” : “/usr/local/bin”
}
GPU load is 0% and in the command line window:D:\FT\cgminer-3.0.1-windows>setx GPU_MAX_ALLOC_PERCENT 100
SUCCESS: Specified value was saved.
D:\FT\cgminer-3.0.1-windows>cgminer -T
[2013-04-28 22:26:11] Started cgminer 3.0.1
[2013-04-28 22:26:11] Loaded configuration file cgminer.conf[2013-04-28 22:26:11] Probing for an alive pool
[2013-04-28 22:26:15] Network diff set to 1.8M
[2013-04-28 22:26:15] Long-polling activated for http://featherpool.com:9999/LP
[2013-04-28 22:26:36] LONGPOLL from pool 0 detected new block
[2013-04-28 22:27:23] LONGPOLL from pool 0 detected new block
who knows why scrypt mining does not work on my HD4730? -
Hello BarrowHill,
I don’t see anything that really stands out as an issue in your configuration file. Comparing it to mine (with a different GPU, but similar options), the only major difference that I can see is my config includes a line: “kernel” : “scrypt” just under the “worksize” option. Honestly, I don’t know if this is necessary or not, since your configuration already specifies “scrypt” : true. Either way, mine has both specified.
That said, I don’t really have any ideas what could be causing your problem. Luckily, there is something that you can try in order to possibly gain more insight into the problem. Modify your cgminer command line from the current “cgminer -T” to “cgminer -T -D --verbose 2>errorlog.txt” and give the program another run. After it finishes loading, let it run just a few more seconds and then you can close it out. Next, open up the errorlog.txt file that was created in the cgminer folder and have a look around in there for anything that looks like a relevant error message.
If you find anything interesting in the way of an error message, take it to Google and see what he says. :)
Sorry I can’t really help more, I’ve not ever had an issue like yours. Please let us know if you figure anything out!
-
Hi again anbo!
In answering the last post I almost forgot that I wanted to reply to you, too! Your plan sounds like a good one. :)
Generally, you want your stale/reject rate to be less than 5%, preferably below 1%. I’ve been mining at fc.dontmine.me and I’m currently at 141961 accepted shares with only 471 rejected. That’s a .33% reject rate which is quite good. The pool generally shows my hashrate to be between ~200KH/s higher to ~100KH/s lower than what cgminer shows.
Something else occurred to me, but I don’t know if it’ll make any difference for you. Generally, the “worksize 256” option seems to fix the issue of pool KH/s not matching up – in your case it apparently doesn’t. :( But , I noticed that most people with your GPU (or any AMD 4000 series) seem to run worksize 128. I don’t really know if it’ll change anything or not but you could just give it a try, I suppose.
Good luck :))
-
Here’s a pic of my cgminer after a few hours of running:
[URL=http://s911.photobucket.com/user/Anbo369/media/cgminer.png.html][IMG]http://i911.photobucket.com/albums/ac314/Anbo369/cgminer.png[/img][/URL]
God damn you get a lot of accepted! What are you mining with?
Oh that worksize thing could be important, now that I think about it I’m pretty sure my 4850 is only 128 bit, so perhaps that’s relevant! :D
thanks for persevering with me! :D
-
Thanks for the picture, it’s truly worth a thousand words! So much information there, where to start? :)
I notice you’re running version 2.11.3 of cgminer. While I doubt this has much to do with any of your issues, you might like to try the latest version, 3.1.0 and see if it makes any difference. Your rejected share rate seems quite high (79/(280+79)=.22 or 22%!). I think it may be caused by a mixture of a few things. You’ve a bit of stale shares interspersed here and there. I think changing your “expiry” setting from 120 down to say, 10 might make some difference here. Your GF (Getwork fail) and RF (Remote fail) numbers are good which should indicate that the pool is functioning well and your connection to it is good. Nonetheless, I find the seemingly high number of new blocks detected before longpoll a bit odd. I would think that could indicate the pool is being a bit slow in notifying you of new blocks which would cause some of the stale shares that you see.
Another major issue here is your number of hardware errors (seen as “HW:228” next to the GPU 0 stats). Ideally you should have none. If your card otherwise functions properly with no artifacting in games or on the desktop, I’d guess the hardware errors are simply caused by your cgminer settings. Unfortunately, I’m not familiar with the 4850, but from a bit of research, it seems like you’re running at stock clock speeds so I doubt your hardware errors are caused by overclocking. Generally, in cgminer, hardware errors can be caused by setting a wrong thread-concurrency or intensity. You’ve not specified a thread-concurrency so it’s picking one automatically based on your number of shaders. cgminer may be guessing wrong. Additionally, your intensity of 10 is a bit low – sometimes low intensities can cause hardware errors. I took a look at the Litecoin mining hardware list and found some 4850s with their cgminer settings listed. :)
See the hardware comparison list here: https://github.com/litecoin-project/litecoin/wiki/Mining-hardware-comparison
For starters, I was surprised with the hashrates! It seems we should be able to get nearly double what you’re managing right now (and without hardware errors!). One of the cards is listed as using a thread-concurrency of 3200 (4*number of shaders). This looks like it might be a good starting point for testing. I’d also try an intensity of at least 13. Regardless of what this does with your hashrate, see if it at least gets rid of the hardware errors.
Here are some of the changes that I’d make to the configuration file that you posted above:
[b]“intensity” : “13”,[/b]
[b]“worksize” : “128”,[/b]
[b]“thread-concurrency” : “3200”,[/b]
[b]“expiry” : “10”,[/b]You’ll likely have to do a bit of trial and error with the thread-concurrency and intensity. Unfortunately, I can’t guarantee that any of these changes will have any positive impact, but with mining it’s all about testing, testing and more testing.
If you manage to work out the hardware errors, that should eliminate at least half (maybe more!) of your issues. :))
Once the hardware errors are sorted, I’d suggest doing a bit of testing at a different pool. I mine at fc.dontmine.me and really like it there. The pool uses stratum (a different type of mechanism for getting “work” from the pool) and so it does a very good job of knocking down the number of stale shares.
As for my hardware – it’s a secret! ;)
Really though, I’m mining with two 7970s and a 7950. My hashrate is around 1,900KH/s.
I like problem solving so it’s really no trouble at all working with you; in fact – it’s fun! Thanks for your responsiveness as well.
Good luck!
-
Holy crap you are so informative!
I always thought i didn’t have any HW problems, because I always looked at the HW in the second top line haha
thank you so very, very, very much!I’ll give all that a shot, and we’ll see how it goes :D
I might give your pool a shot a little later as wellI’ll be sure to keep you posted on how it all turns out :D
Sincerely thanking you!
-
I want to add my thanks as well. I am not currently having any problems, but I did learn some new things from this thread. I want to thank the OP for not being afraid to “look stupid,” because by daring to ask the question, I got to learn something from the highly informative followup posts. Thanks and kudos all around!