Topic: Record hashrate for a 5850? (me, showing off) - page 4. (Read 15271 times)

what agression is for?

can we put AGRESSION 999 for exemple?

Wow!  My best card froze at 1025 MHz.  Perhaps the XFX cards are a bit better at overclocking than the Sapphire Xtremes, perhaps you have a lucky card, perhaps you have a more stability inducing configuration than my own.  I'm assuming your XFX's stock voltage is indeed 1.0875V.  I'd be very interested to learn about your configuration, are you using Windows or Linux?

Inspired by this I've clocked my good card up to 1025 MHz again to see if it lasts longer this time.  I wonder if keeping the card very cool affects stability, I'll keep my card under 50*C and see if it can hold 1025 MHz for 24 hours.  I'm only 5 mins in but already 423.7 MH/s feels good .  How long did your card last at 1030MHz before you decided to increase the clock?

Here is that WORKSIZE=128 again.  I simply cannot figure this out; WORKSIZE=256 is always about 10 MH/s faster for me no matter what my other settings are.  I guess there's an outside chance that this is a Windows/Linux difference.  If you check up the thread you'll find whopper and I competing for the highest hash rate for a 1000MHz card and ended up agreeing that 412-413 is currently achieveable.  Perhaps you can give our settings a go and realise 410MH/s once more!

At the moment I'm using:
RAM=360 MHz, SDK 2.1, Catalyst 11.6, basic phatk with just the MA patch (3%), AGGRESSION=16, WORKSIZE=256, VECTORS, BFI_INT, FASTLOOP=false.

although swapping out SDK 2.1 for SDK 2.4 and 'basic phatk with MA patch' for 'latest phatk patches' is only 0.6 MH/s slower for me at these core speeds and may be much easier for you to try.

Greetings, 5850 owners. I am dropping in to tell you the true tale of the non-reference XFX 5850 (this one: http://www.newegg.com/Product/Product.aspx?Item=N82E16814150477&cm_re=xfx_5850-_-14-150-477-_-Product) that I purchased for $100 on Craigslist. The first night I ran it, the fan broke so that it was no longer speed-adjustable, and stayed at 1100 RPM at all times. This made it quite unsuitable for mining, of course. I communicated with XFX's customer services representatives several times, but was unable to obtain the necessary RMA. I ended up buying the Arctic Cooling Twin Turbo Pro, which fits perfectly and works like.....well, it just works. So well does it work, in fact, that I slowly increased the core clock speed, and it did not freeze until 1035 MHz (410 MH/s)! Right now, I am running it at 1000 MHz (398 MH/s), just to be safe. Note that this is at STOCK VOLTAGE, and has not exceeded 64 degrees C at any time! I think I got a lucky card.

Miner Settings: Phoenix, phatk (latest optimized version), worksize=128, aggression=11

Absolutely.  I'm just following a half-way scientific approach, fixing some factors and then trying to maximise others (in this case hash rate).  Besides, maxing the hash rate is fun.

When my power meter finally arrives I'll be looking very carefully at power consumption and may try to max MH/J before returning to a compromise which takes into account the very high value of mined BTC versus the value of the consumed power where I live.  I've planned ahead to this end a little by investing in a fairly effinient (90%) and exceptionally quiet power supply.  Undervolting is a consideration here too.

As for the pools, I've always been a solo miner and my circumstances are such that there is no reason for me to change.  A friend of mine is pool mining in Windows with BTC guild and has had much trouble in the last two weeks.  multiminer solves some of these issues but he's not tried it yet (and I have no reason to).

Another very important factor for me is noise.  My miner has to live in my room and I value my sanity far more than the BTC it produces.  I replaced the stock coolers on my cards with Zalman VF3000As (Caution: these coolers are not designed for these cards).  Combining this with no overvolting and I'm able to run these cards at high clocks and with 40% fans (which are very quiet).  When the stock coolers were still attached I needed to run them at 80% for reasonable temperatures and this was very noisy indeed (be wary of 100% on the stock coolers, many people have had problems with the fans dying on these cards).

I simply let aticonfig generate the xorg.conf for me, nothing changed there. (aticonfig --initial -f --adapter=all)

I guess that little extra MH/s isnt really important. At this point it would be better to look for some real-world effecting factors, including better cooling, network latency (better pools) to reach a higher real hashrate

Our setups are very similar, so much so that the missing 1.3 MH/s puzzles me.  I guess this could be a difference in the way phoenix and poclbm calculates the value to be displayed from the data fed to them by phatk.  the 10 MHz RAM difference has practically no effect on the hashing speed and varying the AGGRESSION among the 'hard' levels (13 and up) only makes a difference of about 0.6 MH/s.

Ah.  I see.  I was confused because phoenix comes with two kernels, called poclbm and phatk.  I guess poclbm also refers to the front end.  I'll also try some 'harder' aggression settings again (was using AGGRESSION=13 until recently).

I have only one possible tip:  Add a file '.xinitrc' to your home folder and simply put in the one line 'cat'.  This will simply wait for input and could be considered a slight improvement on running an xterm.  This almost certainly won't affect hashing rate but might affect stability a tiny bit.  Either way, it seems neater to me.

Are you doing anything special in xorg.conf?  I don't really know what I'm doing in this file.  I don't think I've made an impact on jitter, hash-rate, or stability yet but it's hard to tell with stability.

I dont use the poclbm kernel, I'm using poclbm miner with phatk kernel Run "git pull", it was included recently
As of the clocks, I'm on 1000,350 now. There is no aggression in poclbm, I use -f0 which is the hardest setting, -w256 and -v

Running headless means I simply run "xinit" which spawns an empty desk with one xterm window in case of ubuntu server. I didn't change anything config related, except for having "export DISPLAY=:0" included in my bashrc file.

Very interesting.  On my system (980MHz core with 360MHz ram):

python phoenix.py -u http://:@:/ -a 1 -q 1 -k poclbm VECTORS BFI_INT AGGRESSION=11 WORKSIZE=256 DEVICE=1
401 MH/s (+/- 2 MH/s)

python phoenix.py -u http://:@:/ -a 1 -q 1 -k poclbm VECTORS BFI_INT AGGRESSION=11 WORKSIZE=128 DEVICE=1

391 MH/s (+/- 2MH/s)

Perhaps this is something to do with RAM clock speed.  I'll investigate.

Edit: Before getting to the RAM I noticed that this playing around with poclbm and AGGRESSION has frozen my card.  This is the second time today!  I really have to pull it back to 975 MHz unfortunately.  I'll do my testing on my good core (still running well after 36 hours at 1020 MHz).

Ok.  In which case '-a 1' does something entirely different and no averages taken by default.

What is your RAM clock and AGGRESSION at the moment?

Also, you mention you are running headless.  I assume you are therefore using custom '/etc/X11/xorg.conf', '/home/user/.xinitrc', et cetera, to activate the cards and give the drivers and poclbm something to point at but without asking the cards to drive any kind of desktop.  If so then I must admit I'm having some trouble getting xorg.conf just right.  I've got it to a point where if I plug a monitor into one of the cards there will be no signal but I'm not convinced it's not doing something anyway.  Any tips would be appreciated and I'll happily share my files if you're interested.

For me, it's the opposite. I lose 10 MH/s if I set -w 256.

I'm actually using Phoenix, so my settings look a bit different:

I'm running poclbm

Yes, I look forward to when that is released.  As far as I can tell there's a early version out but it's only usable on Windows.

By the way, how are you using phatk?  Are you driving it through phoenix?  If so be aware that, by default, the readout is an average of the last 10 rates and this can be disabled with the flag '-a 1'.  I find the moving average is only useful if your MH/s is leaping around by more than 1 MH/s say which shouldn't be the case here.

Hehe I guess so 

Maybe it will change with the new SDK 2.5, so we can squeeze out a little more Hashes 

You and I are clearly of one mind.

As you probably know from the latest patch thread
http://forum.bitcoin.org/index.php?topic=25860.40
I've already tested SDK 2.4 a little and found that at high core clock speeds SDK 2.1 is still slightly superior for the Sapphire HD5850 Xtreme.

If you are done with trying then let me know and I'll fill gellimac in on the details of my configuration.

Looks like we need SDK 2.4 for this, but I will stay with 2.1 at the moment

Can you get it higher with the kernel improvements?  No improvements have helped my rate since the MA tweak.  Feel free to use the recent improvements (from earlier today) to beat 413.3 MH/s.  If you have 412.0 MH/s then I'm hopeful you'll beat it and I'll find out how to improve my rates.

I can only get it up to 412.0 MH/s 
not incorporating the recently made kernel improvements posted at this board

No.  I simply want to give whopper some time to try and improve on my rate.

You me to pay you to know how I can gain 13 MH/s 

All right if you want but for now I have only 0.00006084 BTC it is all I can give...