Topic: 5870 worker question, also pps/proportional (Read 4150 times)

Nope, pools can't measure your real hash rate. All they do is compute an estimate of your speed based on the number of low difficulty blocks (a.k.a. shares) you submit in a given timeframe. It goes like that: 1 pool share equals one solved block at difficulty of 1 which takes about 4 Ghashes on average to solve. If you submit 10 shares for 1 minute that is 40 Ghashes/min or 667 Mhash/s on average. But one should consider that part of that minute is network latency associated with getting work and submitting back each result. It also depends on how lucky you are - it could take 1 hash to solve the share (very unlikely) or 400 Ghashes (once again very unlikely). It's all simple statistics - look at "geometric distribution" in Wikipedia or some other math book if you would like to understand the theory.

Your miner software measures the actual number of hashing operations done in a unit time and thus provides much more accurate estimate on the hashing power of your rig.

On average it shouldn't matter if you mine solo or in a pool. It should not matter if you mine at deepbit, slush or BTCGuild, besides the different taxes, number of staled shares, server latency and whether you are paid for invalid blocks or not.

I cannot change the clocks by that much, i think the max on one is 900 and the min on the other is 600

running at 440 hash according to phoenix (1ghz, 185 mem) however btcguild is saying my average is 520 hash, which is the more accurate or true? I think btcguild is giving me way better results than either slush or deepbit cud. I have no invalid shares or errors...! I think this is much better than i cud have hoped, anyone got any reasons why i shudnt be with btcguild?

ive got mine running at 440 hash now fairly stable. I only ever really mine when not using my pc, so would you suggest i keep my 185/300 memory clock (sometimes i change between the two but 185 is fastest so far) rather than your 1200?

this was something I posted in another forum when I first started.

Ahh, my bad.

Are you getting better yields with BTC Guild?
I currently use Eligius and get about 1btc a day on average with similar speeds.

many thanks max, btw i added u on msn. When you get a chance walk me through o/c. I did download msi afterburner, but its worth noting that it will not accept my changes in clock values. I changed the allow overclocking setting in the conf file but still continues to not accept my changes. For the moment ive been using amd clock tool, do you think i should just change the settings to 1000, 300 memory clock straight away or work my way up? also clock tool has me at 1.1 voltage atm, i cant change this to anything else (like 1.35) only 0.9, 1 and 1.1 are available for selection

Actually I was comparing using Worksize=128 (430Mhash with 200mhz memory) and worksize=256 (432Mhash with 350mhz).  And I installed classic menu shell, because I hate Windows 7 start menu

I'm using BTC Guild, 0% fees, and no problems since new server started.

Slush takes 2% deepbit takes 3%.

Slush's website has a few problems when I try connecting, but I think its worth the 1%...

ok now ive managed to get 410 on phoenix using 128 and aggr=13. I used the same settings on poclbm but never got anywhere near that many hash/sec.

Ok now that im fine tuning my speeds can i ask whether slush or deepbit would be better for me?

Memory does hardly anything and is not worth the temp increase. Hashing uses the Shaders in the core mostly,

In fact, many miners underclock the memory to a very low value, though be careful when doing this as you may crash the machine if you are trying to use the machine at the same time. If you are using Windows, I'd be sure to set your desktop theme to the most basic, as in never versions (vista and up) the desktop is actually GFX accelerated, and could interfere with mining or cause a crash when coming back from screen lock.

There are "sweet spots" in core/memory clock ratio that lead to great performance. Their existence is a consequence of the fact that GPU core must access data in memory from time to time and if core and memory are out of clock sync, core wait cycles are added and that leads to performance decrease. If one has enough time he can experiment with varying the memory clock speed in search for those sweet spots.

ahh its ok now, both deepbit and slush pools working with poclbm and phoenix. I seem to be getting around 10 m/hash more in phoenix, just a query though, the displayed hash, are they true or average, reason is ask is poclbm often shows me at 330~ but then deepbit will display my average in last 5 mins at 350 or something like that

Sort of, AMD currently bundles the opencl driver with the Catalyst driver, so just make sure you have a clean install of the newest version, 10.5, At the moment. You do not need to install the SDK unless you have issues. (At least on a windows based-machine.)


Be careful with over-clocking, I recommended using "MSI Afterburner" like others have said, or "Saphhire TRIXX" if you have a Sapphire card. Use those with HWINFO http://www.hwinfo.com/download32.html to check the temperatures and utilization rate.

The most important thing to remember is to set the fan up high, some utilities will allow you to modify the rates at which the fan turns up, others just specify a static percentage.

Keep the GPU under 60 C if you are running this all the time. Using HWINFO you can see the Shader temp, use this as your scale instead of the core temp. Hashing (mining) uses the shaders almost exclusively. Other utilities will give you an overall temp, but may be underscoring the shader highs.

Tweak slowly, bump the core up at 20 a time then test using either the built-in AMD tool, or Kombuster which comes with MSI Afterburner, as you run into issues, lower by 5 or slightly increase the voltage, be very careful with voltage, you can easily fry the card and this is not covered by warantee.

EDIT: I mention keeping the temps under 60, although higher temps won't necessarily fry the machine, (Most cards are rated to around 90C) Long term this can cause heat damage. Ambient temperature in the room can also rise over time if not well ventilated. You don't want to come back from work and find the room at 85F with a burnt our card is all I am saying.

Ok, clocked memory from 200mhz to 350mhz and got 432Mhash/s (2Mhash/s increase). Not sure if it's worth it (more power and temperature, I guess?)

413 Mhash/s with WORKSIZE=256
406 Mhash/s with WORKSIZE=128

Phoenix 1.48 + phatk, Windows 7 32-bit, SDK 2.4, Phenom 140 CPU, dual 5870 at 935/319.

i knew they had problems, even when announcd i was only getting the odd error, now it seems every worked share is an error!

SDK 2.4 is the one bundled with the 11.5 drivers. Look at the downloaded file name. It should be something like:
11-5_vista32_win7_32_dd_ccc_ocl.exe
The "ocl" part means that the OpenCL SDK is included. Just (re-)install it.

I don't think so, my friend is also getting those errors. That's why there's no fee at Deepbit atm.

Phoenix is exactly what I am using. The best aggression for me is actually 7, and I am using 128 as worksize. at one point I had results better than 430, but now its at about 400.

When you guys mention SDK 2.4 do you mean the catalyst control center? Can you pleas post a link where I can download SDK 2.4, as of right now I am just using the latest Catalyst Control Center, and MSI afterburner, but my sliders will not go as low, or as high as mentioned in other posts above.