Except thats not what he said at all. m0's kernel ALSO runs best at -w 64 and low -f settings. -f controls kernel execution length; ANY kernel will run better with lower -f settings because there is far less time wasted on kernel setup overhead.
10.12 may or may not cause issues for some people. Downgrading to 10.11 should fix them for the few people that have them.
Topic: DiabloMiner GPU Miner - page 79. (Read 866572 times)
Art's miner is great, but not without disadvantages. At -f 30 it is significantly slower than the original miner. At -f 2 it is faster, but the desktop is useless for interactive work. Could we have an option to use the old miner? Perhaps even an option where DiabloMiner switches miner when it has to slow down due to desktop activity, and changes back to Art's miner with -f 1 when the screensaver is on?
Its just a kernel switch. The kernel does not have control over what you describe, so what you describe is impossible.... if Art's miner performs badly, it will perform badly no matter the -f setting.23:48 < ArtForz> my kernel usually likes -w 64 or 128 and really low -f
23:48 < ArtForz> I'm running the equivalent of -f 2 her
Quote
Also, if you are using 11.1, don't. Also, -f 30 sounds rather low for keeping your desktop interactive.
I use 10.12 It works for me. And -f 30 was good enough for me with the previous kernel, and gave a decent hashrate while keeping interactivity. Art's kernel is not good at this setting, according to ArtForz. Art's miner is great, but not without disadvantages. At -f 30 it is significantly slower than the original miner. At -f 2 it is faster, but the desktop is useless for interactive work. Could we have an option to use the old miner? Perhaps even an option where DiabloMiner switches miner when it has to slow down due to desktop activity, and changes back to Art's miner with -f 1 when the screensaver is on?
Its just a kernel switch. The kernel does not have control over what you describe, so what you describe is impossible.... if Art's miner performs badly, it will perform badly no matter the -f setting. Art's kernel DOES drive the hardware (3%) harder, so it MAY require a larger -f number to keep the same desktop interactivity, but thats about it.
Also, if you are using 11.1, don't. Also, -f 30 sounds rather low for keeping your desktop interactive.
Update: Changed to 15 sec avg/forever double meter, further decreased run size floor, allow very maximum nonce before saturation flush
Art's miner is great, but not without disadvantages. At -f 30 it is significantly slower than the original miner. At -f 2 it is faster, but the desktop is useless for interactive work. Could we have an option to use the old miner? Perhaps even an option where DiabloMiner switches miner when it has to slow down due to desktop activity, and changes back to Art's miner with -f 1 when the screensaver is on?
With '-f 1' after a few hours it's definitely settled in for a nice hash rate. It swings maybe +/- 5%. Quite acceptable.
The miner, even with -f 1, tries to adjust to system activity. I use -f 1000 on my 4850 now, and it swings wildly in all sorts of directions when I'm using my computer.... this is by design. Most people want to mine while having a useful desktop. -f 1 curbs this behavior as much as possible, but obviously does not eliminate it.
Using Fedora 14, "-f 1" switch improved my hashrate more than 25% both on 5870 and 5970,
peaks are 350 and 610 Mhash respectively. f1 is your friend ...
peaks are 350 and 610 Mhash respectively. f1 is your friend ...
Ok, it's not crossfire related. Even with a single card my hashes are all over the map, unlike my other system. It must be driver versions.
Cdecker, how do you get the data for those graphs?
DiabloD3, "-f 1" definitely improves my hash-rate, but it still swings wildly. Typically between 300M and 350M, but also way below 300M from time to time. I'll try turning off crossfire and see if it improves.
DiabloD3, "-f 1" definitely improves my hash-rate, but it still swings wildly. Typically between 300M and 350M, but also way below 300M from time to time. I'll try turning off crossfire and see if it improves.
Connections to the miner when they lag (such as connection failures) confuses the miner. If thats a long count hash, thats completely inaccurate... it could have flatlined completely to 0.
Ohoh, somehow this is worrying me:
Any idea what might be causing this? I'm getting it along with a few connection errors to slush's pool
Any idea what might be causing this? I'm getting it along with a few connection errors to slush's pool
With dual cards, my hash/sec are all over the place. It never settles in to a steady rate. (running locally)
As I said to cdecker, if you're benchmarking use -f 1
With dual cards, my hash/sec are all over the place. It never settles in to a steady rate. (running locally)
Hmm, are you connecting locally or to slush's pool?
Use below -f 5, my miner counts hash performance from start, instead of using a 30 second average. If you're seriously benchmarking it, use -f 1 and let it run for like 15 minutes.
Yeah, that's exactly my problem. It was fluctuating like hell but it stabilized over time right now I have a 5 hash/s standard deviation which is incredible. I had only a 5 minute warmup phase,a 5 minute hot phase and measured the average over the 5 minute hot phase and it didn't look nice. But with a longer warmup phase it looks better. Here's my monitoring graph for the last 24h.
Notice the high fluctuation and then the stabilization to a higher average
Use below -f 5, my miner counts hash performance from start, instead of using a 30 second average. If you're seriously benchmarking it, use -f 1 and let it run for like 15 minutes.
Strange, with -f 10 it now gives me similar results to what I got before ArtForzz's kernel was introduced. But I have a standard deviation of ~10%! Still not perfect but I'm going to tweak my settings further
Run the miner with --help. The only tuning switches are -w and -f, -w changes worksize (on ATI it has to be a multiple of 64, 64 seems to be the fastest, 256 is the default; on NVidia it has to be a multiple of 32, and all values seem to work exactly alike), -f changes how long the kernel runs (FPS, the lower the value the longer it runs, -f 1 has the least overhead but also destroys desktop interactivity).
Hi :
Running Diablo successfully in Fedora 14, HD 5870, 260/290 Mhash/s with -w 64.
Any place I can find complete reference of tunning switches, sorry cannot not find them in wiki nor in docs.
Many Thanks
Gustavo
Running Diablo successfully in Fedora 14, HD 5870, 260/290 Mhash/s with -w 64.
Any place I can find complete reference of tunning switches, sorry cannot not find them in wiki nor in docs.
Many Thanks
Gustavo
Jump to: