Does anyone know how to set a backup pool in GUIminer? hope this is the correct thread...
My current setting (flags) are: -v -w128 -f1 (does it matters if there are spaces i.e. -v -w 128 -f 1 ) I see some people do it like that
Thanks!
Topic: Poclbm Flags (Read 57509 times)
Having blown my 450W power supply my XFX 750W PSU arrived yesterday.
Have been running the following setup for about 24 hours now:
GUIMiner (poclbm) on Windows Vista; XFX 5830, 900/300, -v -w256 -f1 = 265Mhash
If I let Afterburner handle the fan speed the GPU sits at around 61/62 degrees C, or at 100% fan 57 C.
MonkeyThink
Have been running the following setup for about 24 hours now:
GUIMiner (poclbm) on Windows Vista; XFX 5830, 900/300, -v -w256 -f1 = 265Mhash
If I let Afterburner handle the fan speed the GPU sits at around 61/62 degrees C, or at 100% fan 57 C.
MonkeyThink
Quote
poclbm -v -w128 -f1
these were the optimal settings for me back when I used poclmb
what do you use now?
I use -v -w256 -f1
Quote
poclbm -v -w128 -f1
these were the optimal settings for me back when I used poclmb
what do you use now?
Lawl i dont see why you placed the word Only in there, your getting what appear to be 97-99% efficency But im a noob at this so dont take my info with weight
poclbm -v -w128 -f1
core clk is 1038 & mem clk is 370, fan is 100%, temp is 65-68C
core clk is 1038 & mem clk is 370, fan is 100%, temp is 65-68C
Only? what's your flags and core speed?
Im using a 6870 and i am LOVING -v -w 128 -f 300; i get no desktop lag, miner effiecency only went down by 2% and i can now play video games while mining (ofcourse the miner runs slower) but rthdribl went from 27 frames while mining to 129 frames while mining (438fps when not mining)
Running with 239Mh/s; Core:940mhz, Mem:1150
i plan to buy another 6870 unless the 69xx has SOMETHING aside from power worth getting
Running with 239Mh/s; Core:940mhz, Mem:1150
i plan to buy another 6870 unless the 69xx has SOMETHING aside from power worth getting
Thats good. I am getting only 279 Mhash/s on my 6870.
Im using a 6870 and i am LOVING -v -w 128 -f 300; i get no desktop lag, miner effiecency only went down by 2% and i can now play video games while mining (ofcourse the miner runs slower) but rthdribl went from 27 frames while mining to 129 frames while mining (438fps when not mining)
Running with 239Mh/s; Core:940mhz, Mem:1150
i plan to buy another 6870 unless the 69xx has SOMETHING aside from power worth getting
Running with 239Mh/s; Core:940mhz, Mem:1150
i plan to buy another 6870 unless the 69xx has SOMETHING aside from power worth getting
Why w128, when the card handles w256 & also putting w256 gives around 7-10Mhash/s more?
Please some one explain, coz it confuses me a lot.
Thanks.
Please some one explain, coz it confuses me a lot.
Thanks.
Card by card, and even card manufacturer,motherboard and many other factors in play, toss in different OS/Driver versions and it gets rather complex. What you're setting here is basically the size of data being pushed to/from the card. Depending on the ton of variables involved, certain settings work better for one reason or another.
There isn't and can never be a a guide where someone can say for sure "this will do better for you", you really just have to fiddle around and find the best config for your setup.
Perfect example, I have 2 identical HP machines in terms of hardware/OS, the only thing that differs is graphics driver versions. On one machine, "-w128" does better than "-v -w64" on the other.
why i can't play -v (the pocldm just get crash)
my system 5970 @defult win7 32bit skd 2.1 and cpu used 100%
amd athlon x2 4200
my system 5970 @defult win7 32bit skd 2.1 and cpu used 100%
amd athlon x2 4200
I tried to see what difference in shares.
I ran both for 1 hour to mine deepbit in PPS & i got this.
-w128 = 232 shares.
-w256 = 221 shares.
11 shares less & no stale in both.
seems 128 mine more shares by reducing worksize.
I ran both for 1 hour to mine deepbit in PPS & i got this.
-w128 = 232 shares.
-w256 = 221 shares.
11 shares less & no stale in both.
seems 128 mine more shares by reducing worksize.
For me the -w128 yields better results than -w 256 (atleast on my 5770). I saw no difference between -w64/128/256 in my 6950.
Why w128, when the card handles w256 & also putting w256 gives around 7-10Mhash/s more?
Please some one explain, coz it confuses me a lot.
Thanks.
Please some one explain, coz it confuses me a lot.
Thanks.
Thanks mortalis. Just what I was looking for. Small donation sent.
Thanks for posting this. I was looking for a list of the flags and had no idea it was as easy as using --help.
If you are using the PC for nothing too graphics heavy better to bump the f closer to 20 and maybe 30
30 is the defaulf one. Code:
-v -w128 -f 30
It seems the following is a good combo for most 5xxx and 6xxx series cards when not using the PC
If you are using the PC for nothing too graphics heavy better to bump the f closer to 20 and maybe 30
On my new 6950 there was no appreciable difference between w 64 and w128. There was a difference on my 5770 where 128 yielded a sizable difference versus 64.
Code:
-v -w128 -f 1
If you are using the PC for nothing too graphics heavy better to bump the f closer to 20 and maybe 30
Code:
-v -w128 -f 25
On my new 6950 there was no appreciable difference between w 64 and w128. There was a difference on my 5770 where 128 yielded a sizable difference versus 64.
Just thought i'd post it for quick reference.
Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USER, --user=USER user name
--pass=PASSWORD password
-o HOST, --host=HOST RPC host (without 'http://')
-p PORT, --port=PORT RPC port
-r RATE, --rate=RATE hash rate display interval in seconds, default=1
-f FRAMES, --frames=FRAMES
will try to bring single kernel execution to 1/frames
seconds, default=30, increase this for less desktop
lag
-d DEVICE, --device=DEVICE
use device by id, by default asks for device
-a ASKRATE, --askrate=ASKRATE
how many seconds between getwork requests, default 5,
max 10
-w WORKSIZE, --worksize=WORKSIZE
work group size, default is maximum returned by opencl
-v, --vectors use vectors
--verbose verbose output, suitable for redirection to log file
--platform=PLATFORM use platform by id
Options:
--version show program's version number and exit
-h, --help show this help message and exit
-u USER, --user=USER user name
--pass=PASSWORD password
-o HOST, --host=HOST RPC host (without 'http://')
-p PORT, --port=PORT RPC port
-r RATE, --rate=RATE hash rate display interval in seconds, default=1
-f FRAMES, --frames=FRAMES
will try to bring single kernel execution to 1/frames
seconds, default=30, increase this for less desktop
lag
-d DEVICE, --device=DEVICE
use device by id, by default asks for device
-a ASKRATE, --askrate=ASKRATE
how many seconds between getwork requests, default 5,
max 10
-w WORKSIZE, --worksize=WORKSIZE
work group size, default is maximum returned by opencl
-v, --vectors use vectors
--verbose verbose output, suitable for redirection to log file
--platform=PLATFORM use platform by id
Jump to: