Argument options to adjust performance and efficiency: --oc1 and --oc2

miniZ includes a command line argument for improving performance at distinct overclock (OC) values.

When you’re adjusting your power limit (PL) and OC setting values, you can use --oc1 or --oc2 to change the default kernel mode for your GPU. The following table (Table 1.) shows oc1 and oc2 support for each combination of GPU and algorithm. --oc0 is default mining mode that each GPU.

--oc1 or --oc2 will set a specific kernel mode for the GPUs. These refer to kernels we noticed that performed best in some OC settings, and for some GPUs. This is why not all GPUs have oc1 or oc2. Sometimes the default (optimised for stock settings) was the best we found.

Recently, from v1.5t31,2 version, you can use --ocX for miniZ to automatically choose the best kernel for your GPU. For more information check ocX related FAQ here.

Algorithms
GPU 96,5 144,5 125,4 150,5 192,7 210,9 150,5,3 144,5s
BeamHashIII
GTX 1050 2GB - - - - oc1 - - -
GTX 1050 Ti 4GB - oc1/oc2 - oc1 oc1 - - -
GTX 1060 3GB/6GB oc1 oc1/oc2 oc1/oc2 oc1 - oc1 oc1 -
GTX 16XX series - oc1 - - - oc1 - -
P106-100 oc1 oc1/oc2 - oc1 - oc1 oc1 -
GTX 1070 - oc1/oc2 oc2 oc1 oc1 oc1 oc1 -
GTX 1070 Ti - oc1/oc2 oc1/oc2 oc1 oc1/oc2 oc1 oc1/oc2 oc1
GTX 1080 8GB oc1 oc1/oc2 oc1/oc2 oc1 oc1 - oc1/oc2 -
GTX 1080 Ti 11GB - oc1 oc1/oc2 oc1 oc1 oc1 oc1/oc2 oc1
P104-100 oc1 oc1/oc2 oc1 oc1 oc1 - oc1/oc2 -
RTX 2060/2070 - - - - - - oc1 -
RTX 2080/2080 Ti - - - - - - oc1 -
TITAN - oc1 oc1/oc2 oc1 oc1 oc1 oc1/oc2 oc1
Table 1. v1.6v --oc1/--oc2 support for all algorithms and GPUs.

Usually, at lower PL/OC values --oc1 produces better performance. When you push your GPU to higher PL/OCvalues, --oc2 is likely to be produce higher hashrate. It all depends on your OC settings. 

The best is to try both and check which performs best for your settings and GPUs. For stock settings it should not be necessary to use this option.

When you add --oc1 or --oc2 to your command line this setting is applied to all GPUs. You can also apply the setting to a specific GPU.

Examples for a rig with 6 GPUs, mining Zel on equipool:

1. To apply --oc1 to all GPUs

miniZ.exe --url [email protected]:50053 --log --oc1

2. To apply --oc1 only to GPU#2 and GPU#3

miniZ.exe --url [email protected]:50053 --log --oc1=2,3

3. To apply --oc2 to all GPUs except for GPU#1 and GPU#4. Note that order matters (try it out!).

miniZ.exe --url [email protected]:50053 --log --oc2 --oc0=1,4

4. To apply --oc1 to most GPUs, --oc2 to GPU#0, and default mode to GPU#3 and GPU#4.

miniZ.exe --url [email protected]:50053 --log --oc1 --oc2=0 --oc0=3,4

 

1 Available for 125,4 and 150,5,3 algorithms in v1.5t3. Available in all algorithms from v1.5u version.

2: Do not use/apply oc1/oc2/ocX (or --mode) at the same time on the same GPU. This could cause confusion in understanding miniZ behavior. One of the options will prevail though, usually the last one appearing in the command line.

 

* NOTE: Adding --oc1/2 to the command line does not apply OCs to the GPU, it just makes the GPU run with different kernel functions. When you adjust the OCs in Afterburner (or other program) and run miniZ without --oc1/2 the miner will run with the default kernels (usually optimized for stock settings). The --oc command line option just change the way miniZ runs not the OC settings of the GPU. *

For other command line arguments check Usage page.

Happy mining!