its command line interface and options.
Additional command line options are:
--no-autotune disables the built-in autotuning feature for
maximizing CUDA kernel efficiency and uses some
heuristical guesswork, which might not be optimal.
--devices [-d] gives a list of CUDA device IDs to operate on.
Device IDs start counting from 0!
--launch-config [-l] specify the kernel launch configuration per device.
This replaces autotune or heuristic selection.
--interactive [-i] list of flags (0 or 1) to enable interactive
desktop performance on individual cards. Use this
to remove lag at the cost of some hashing performance.
Do not use large launch configs for devices that shall
run in interactive mode - it's best to use autotune!
--texture-cache [-C] list of flags (0 or 1 or 2) to enable use of the
texture cache for reading from the scrypt scratchpad.
1 uses a 1D cache, whereas 2 uses a 2D texture layout.
This is very experimental and may hurt performance
on some cards.
--single-memory [-m] list of flags (0 or 1) to make the devices
allocate their scrypt scratchpad in a single,
consecutive memory block. On Windows Vista, 7/8
this may lead to a smaller memory size being used.
>>> Example command line options, advanced use <<<
cudaminer.exe -d 0,1,2 -i 1,0,0 -l auto,S27x3,28x4 -C 0,2,1
-o stratum+tcp://coinotron.com:3334 -O workername:password
I tell cudaminer to use devices 0,1 and 2. Because I have the monitor
attached to device 0, I set that device to run in interactive mode so
it is fully responsive for desktop use while mining.
Device 0 performs autotune for interactive mode because I explicitly
set it to auto. Device 1 will use kernel launch configuration S27x3 and
device 2 uses 28x4.
I turn on the use of the texture cache to 2D for device 1, 1D for device
2 and off for the other devices.
The given -o/-O settings mine on the coinotrom pool using the stratum
protocol.