Topic: guiminer flags (Read 12397 times)
Nebraska huh? Where at? I'm in Iowa myself.
ok this is what I meant, I found some more flags that may be relevant when using guiminer, and what they are:
-f FRAMES, --frames=FRAMES
will try to bring single kernel execution to 1/frames
seconds, default=30, increase this for less desktop
lag
-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
-f FRAMES, --frames=FRAMES
will try to bring single kernel execution to 1/frames
seconds, default=30, increase this for less desktop
lag
-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
I used to have same flags, but I've seen that adding -f1 improve a bit some Mhash (~3Mhash and it's more stable) but you may fell a bit "lag" on your system.
Sorry for the n00b question, but can someone post a list of the flags one can use with guiminer, and a description of them?
for instance, I have -v -w128 right now on mine since I saw it mentioned in the Hardware comparison chart... but I'd like to know what they are, and additional flags as well
for instance, I have -v -w128 right now on mine since I saw it mentioned in the Hardware comparison chart... but I'd like to know what they are, and additional flags as well
Jump to: