I'm going to start here, but feel free to push me over to the Pools/p2pool topic.
I have some conceptual confusion/ignorance about using cgminer with p2pool.
(1) What metrics should I be looking at to tune parameters?
(2) What shares are cgminer reporting as accepted? As I (mis?)understand it, cgminer shares are traditional difficulty=1 pool shares, but p2pool shares are different, having a higher difficulty. What is "accepting" the shares that cgminer reports as accepted?
(3) I have been running with default intensity. Now with 2.2.1 that means a default of 1 thread per GPU rather than the former 2. With p2pool, would this be good? bad? don't know?
(4) I have assumed that cgminer's donation feature won't work with p2pool and that donations to CK must therefore be manual. Is that right?
Edit: (1) and (2) are related. With traditional pools, cgminer's U statistic (accepted/minute) seems to be the gold standard for tuning. But with p2pool...?
1. MH/s as reported in the average column is still the only objective measure. Provided you don't have any problem communicating with your pool/server it should tell you ultimately how well it's tuned. 2. No idea with p2pool, you'll have to ask a p2pool expert. 3. Default intensity is "dynamic" meaning it's meant to be used on a desktop with a GUI. If this does not describe your setup, use a static intensity, usually 7-9 provides the best, depending on hardware. Try and find the largest value that does not fluctuate too much. Dynamic works fine regardless of what pool you're using it on, provided that's what you want. 4. It should still work fine. |
|
|
|
This reflects a post-2.2.1 version that I happened to download and which failed to run; the problem is fixed by reverting to the 2.2.1 release. If this report is not useful, just ignore it  The problem version is: 53c1e9a Allow the OpenCL platform ID to be chosen with --gpu-platform. Did you do ./autogen.sh before reconfiguring and rebuilding? What does "./cgminer -n" show? |
|
|
|
Sweet  |
|
|
|
|
What you say about the config files should not apply with the current 2.2.1 version. It should cope fine with zero values, and redundant entries now.
|
|
|
|
|
Likely phatk with 2.1/2.4/2.5 will be faster on everything but GCN.
If you are benchmarking, make sure to delete any .bins before you start, and start cgminer twice after that so it can generate the bins the first time (which is slow) and then load them the second time.
Even 50 shares will do for the MH/s quoted at the end provided you have no network connectivity issues. Don't look at all at how long the shares took to generate, but look at the average MH/s.
|
|
|
|
Updated git tree. (Thanks go to sveetsnelda for most of these fixes) Update poclbm kernel for better performance on GCN and new SDKs with bitalign support when not BFI INT patching. Update phatk kernel to work properly for non BFI INT patched kernels, providing support for phatk to run on GCN and non-ATI cards. If you're desperate to try these on windows, downloading the new files and using the old filenames will work https://raw.github.com/ckolivas/cgminer/master/phatk120203.clhttps://raw.github.com/ckolivas/cgminer/master/poclbm120203.cluse them to overwrite the existing phatk110817.cl poclbm110817.cl This is not a magic performance enhancement. It might improve on nvidia if you can use the phatk kernel, and it will be significantly better on GCN (79xx cards) but will not match other kernels out there yet. |
|
|
|
when i do that with my 6970, it defaults back to stock settings.
I think this is an issue with the 6xxx series, not the miner software. All 6000 series cards are restricted to GPU clock -125 for memclock. For example, if you are running at 900 on GPU, the lowest you can clock the memory is 775. Anything lower than 125 below the GPU clock will reset the memclock to stock speed. Windows applications have extra backdoors to the hardware to get around this. We have no cross platform->linux code that can do this, nor do I have access to how it's done on windows. So afterburner and others can work around this limitation. |
|
|
|
So, summary:
--auto-gpu
by itself ends up enabling the cut off feature and nothing else, default is 95 degrees. See why I would like --temp-cutoff to work without all the other stuff? ? Likely, based on what you've described, I'm guessing what you want is: --auto-gpu --temp-cutoff 72 --gpu-engine 975 This will start it at gpu engine speed 975 and will not throttle it, and will enable the thermal cutoff feature if it his 72 degrees. |
|
|
|
So, summary:
--auto-gpu
by itself ends up enabling the cut off feature and nothing else, default is 95 degrees. See why I would like --temp-cutoff to work without all the other stuff? ? |
|
|
|
|
I expect that intensity 7-9 is optimal for just about every available card. Increasing intensity beyond this will likely make the displayed hashrate fluctuate more wildlly, but the average hashrate will be the same, and utility is unlikely to be affected positively or negatively. However, depending on which SDK/driver combination you use, CPU usage may rise quite dramatically when you get beyond the optimal value.
|
|
|
|
|
Luck plays too big a role in utility to make such a claim I'm afraid.
|
|
|
|
does "SICK" for middle card mean a dysfunctional PCI-e slot? the card starts up fine but after about 2 min does this.
Heat? What temps is it getting up to? mid 80's only
What happens if you ONLY use the 2nd slots (no other cards)?
haven't tried that yet... It means you're driving your card too hard, likely overclocking it too much for the available voltage and running temperature. cgminer tends to run GPUs extraordinarily hard at similar clocks compared to other mining software. |
|
|
|
Now having said that, since temp-cutoff doesn't actually adjust engine or memory clock speed, it may well be valid to have it enabled regardless. The default for temp-cutoff, as described in the readme  , is 95 degrees. I vote for this. I actually asked about it many pages ago (possibly many moons by now) and didn't see a response. In the meantime, though, without using a config file, can I keep the card at an overclocked speed and cutoff (my card quits working with auto-gpu or auto-fan, which is why I would like temp-cutoff to work without them, but if I could lock the GPU and not turn on auto-fan, that might be a workaround). IOW, since this will presumably downclock before cutoff: --auto-gpu --temp-hysteresis 1 --temp-cutoff 72 --gpu-engine 975 Is this a valid command?: --auto-gpu --temp-hysteresis 1 --temp-cutoff 72 --gpu-engine 975-975 I would test it myself, but I don't really want to have to reboot two or three times because my card messes up, and I would rather fully understand the theory first. Even after a lot of help in the last couple pages, I find it murky, especially since I thought I saw a post that implied the opposite of my understanding of --temp-overheat and --temp-cutoff... That is an awfully low cutoff, and cutoff doesn't throttle unless you set the overheat temp LOWER than it. However, if you specify --auto-gpu without ANY other parameters, like engine speed or memory speed, it will STILL turn off the GPU without adjusting GPU engine clock when it gets to temp cutoff. So, summary: --auto-gpu by itself ends up enabling the cut off feature and nothing else, default is 95 degrees. |
|
|
|
[2012-02-02 15:02:40] clGetPlatformsIDs failed (no GPU?)
[2012-02-02 15:02:40] 0 GPU devices detected This is a broken SDK installation. Come on conman how could they have broken the installation? It is so simple (one step) we just copied over opencl.dll version 1.1.0.0 from my windows7 machine (to windows xp machine). LOL |
|
|
|
[2012-02-02 15:02:40] clGetPlatformsIDs failed (no GPU?)
[2012-02-02 15:02:40] 0 GPU devices detected This is a broken SDK installation. |
|
|
|
|
There is no way on earth it only says 0 devices enabled. I'm trying to help you so I expect the courtesy of you actually using the goddamn command.
An -n output looks like this.
[2012-02-03 08:36:22] CL Platform vendor: Advanced Micro Devices, Inc.
[2012-02-03 08:36:22] CL Platform name: AMD Accelerated Parallel Processing
[2012-02-03 08:36:22] CL Platform version: OpenCL 1.1 AMD-APP (831.4)
[2012-02-03 08:36:22] Error: Getting Device IDs (num)
[2012-02-03 08:36:22] clDevicesNum returned error, no GPUs usable
[2012-02-03 08:36:22] 0 GPU devices detected
|
|
|
|
Well looks like you solved the 6000 series 150Mhz limit. Setting the memory 125 below engine speed is a problem only on software that uses the ATI Display Library to adjust the speeds. There is windows software that has other means of poking the devices to adjust speeds that does not use the ADL. ATI have not made that information available, nor is it, I believe, crossplatform. Thus I can't use their approach since I don't have access to that information, and even if I could, it would probably only work on windows. Flashing the bios on these devices makes it respond via ADL to below 125 though. Also, the ADL does allow me to try and set values outside the "safe range", and that's what cgminer does, but that doesn't mean the hardware will listen to you. Hence why it returns to you the now "reported" values after you try and set it from the menu so you can confirm for yourself if it has taken or not. I can set all sorts of things outside the safe range, but cannot set others. |
|
|
|
is there anyone else running windows xp having the same problem as me? it says "no devices enabled. Cannot mine!" 2.1.2 works for me but i would like to see if i get higher hashes in xp
More info would be good... hardware, driver versions, sdk version, and what "cgminer.exe -n" gives you from 2.2.1. |
|
|
|
Thanks for the healthy discussion guys. The multiple input from various people makes it much easier to provide support if it doesn't all come from me. Okay so on the temp-cutoff feature. The theory behind the ADL usage in cgminer was that unless anything in GPU management was explicitly enabled, then cgminer should under no circumstances try and change settings itself. Thus auto-gpu must be enabled before temp-target, temp-overheat, or temp-cutoff are active. As ADL is unreliable in its ability to correlate which device is which from the mining, I was loathe to making it do anything unless the user had manually gone in and confirmed everything was working as anticipated. I really didn't want people to get "surprises". Now having said that, since temp-cutoff doesn't actually adjust engine or memory clock speed, it may well be valid to have it enabled regardless. The default for temp-cutoff, as described in the readme , is 95 degrees. |
|
|
|
|
I had an absolutely massive rise in hashrate going from 0 to 5% (more than 5%). Going from 5 to 20, on the other hand, would make hashrates fluctuate wildly, but ultimately be the same average as 5%. So it seemed to be more of transient turbo boost at levels above 5%, but since mining goes 24/7, it ended up being the same. There is no documentation about what powertune really does. Nevertheless, if you're well within good heat ranges, and powertune is available, it is *well* worth trying. To me it appears to increase hashrate proportional to the amount of power it it uses which is perfectly valid as far as I'm concerned. No, I don't have hard at-the-wall numbers to prove this.
|
|
|
|
|
Show Posts
