Documentation to help using PG Miner Bench.

During the installation there is a few things that needs to be agreed to.


Settings -> Appsettings
On first start the application needs to be setup.

The application is using two 'rounds' to find the most optimal overclock settings for each GPU in a system. The first round is for attempting to find which combinations of 'power target', 'base clock offset' and 'memory clock offset' the GPU's will not work with. The second round takes the top results from the first round and runs each at a longer period of time. Round 2 attempts to find if a combination of parameters is stable over time, to try and make each system as stable as possible while running overclocked GPU's. The number of runs in round 2 can be set using the 'Round 2 runs' setting. Different algorithms will require different length's of each run. For example it is highly recommended to use, if not the maximum time for each round, at least 1 hour for round 1 and at least 9 hours for round 2 when evaluating x16r algorithm. Other algorithms require's less time for each round, but the longer the runs are, the more likely it is that the results found by the application will be stable over longer period of times when mining.

If the checkbox 'Use the same parameters for all devices' is checked the user don't have to input parameters for each GPU on the 'Parameters' tab. Instead only the first GPU will be enabled on that tab, and the parameters for the rest of the GPU's will filled in as the user chooses parameters for the first GPU. If the checkbox is not checked the user will have to input parameters for each GPU individually and click each save button for the parameters to be added to the database.

There are currently two different logics available when evaluating.

⦁ Thorough, will walk through all possible combinations beginning with lowest settings. First it will go through base clock offset and for each successful run it will increase the offset by the value set in the 'base clock offset increase steps' box. If the miner crashes during a run it will retry the same paramaters as many times as specified in the 'Round * retries' options. If all attemps fails at a given base clock setting the application will mark that combination as failed in the database, and it will assume that any higher base clock would fail as well and mark them as failed. When it reaches the highest value set for base clock offset, or if the miner fails and the rest is marked as failed, the application increase the memory clock offset by the steps defined in the 'memory clock offset increase steps', and the base clock will start from the lowest defined offset again. For each memory clock offset the application walk through the available core clock offset steps again. When the steps for memory clock offset has reached the it's maximum, the application will start increase the power target and both core clock offset and memory clock offset will start from the lowest defined value.
Depending on the settings used this can be very time consuming.

⦁ Random, works a little bit differently. It will pick a set of parameters from the database and run through it. It will still use the retry amount defined, and it will still mark any higher core clock offsets as failed if the miner crashes. If a run is successful, it will however also assume that any lower core clock offset would also be successful and mark them as such in the database, meaning it will run those mark as successful. This will decrease the length of the evaluations quite a lot, depending on the ranges set in the parameters. The 'estimated time remaining' will be the same when an evaluation is started but will decrease during the runs.
This logic is faster, but it will not be as precise as using thorough. It is however recommended for algorithms that needs longer runs for evaluating if they are stable or not.

As can be seen in the screenshot below there are an option for using a custom fan curve. The application contains two simple curves that gives the user the choiche not to use any other tool for controlling the GPU fans. This option will however not be available for users that have RTX cards in their systems, simply because the tools used to control the fans do not support fan control on those cards at the moment. So a third party tool is recommended.

Skip seconds are used to control how much time a miner should be given to be able to connect to the pool and start mining. This can differ quite a lot between miner starts, so at least 30 seconds will be required for most miners and algorithms. Some will need even more time. This is used so that each run can be measured only with data from actual mining and not from waiting for data. This affects both the hashrate and the power draw.

Intensity increase steps sets how big the steps are to be when evaluating intensity.

Use Tp Link Smart Plug (HS110) enables to get the powerdraw from the plug (wall) instead of just the GPU's. Check the box and enter the ip address for the plug. The 'Total powerdraw' at the top will when show the wall powerdraw. If unchecked it will show the sum of all GPU's in the system. If an incorrect ip address is entered it will show 'ERROR' instead of current powerdraw, it might take a few seconds to update.

Enable Hash Auger integration will make it possible to update the settings for each GPU in Hash Auger after an evaluation completes. For this to work it requires Hash Auger 2.8.8 beta 1 or higher. It also requires that the 'Enable Web Api' and the 'Execute Remote Commands' checkboxes are checked and that an API port number and an API full access key is setup in Hash Auger and that the same port and key is entered in PG Miner Bench.


Settings -> Monitor output
The monitor output shows the communication between the main app and the monitor. The output is active upon application start and is disable automatically after it outputs 250 lines. It can be activated again at any time by checking the 'Enable output' checkbox.


Settings -> Algos
Not much to do on the 'Algos' tab other then to enabled or disable algorithms that should be available in the application.


Settings -> Pools
On the pools tab the user chooses which pools should be available to use when running an evaluation. Currently only autoexchaning pools are avalable in the application. Here the user will have to input the payout address for the coin the user want's to get paid in, and the symbol for that coin. If the pools uses regions, like ZPool does, a suitable region needs to be choosen from the dropdown. The user also gets the choiche to decide which algorithms should be available for each pool. Only algorithms enabled on the 'Algos' tab will be available in the grid.


Settings -> Miners
On the miners tab the user can choose which miners should be available to user for an evaluation. To enable a miner first check the checkbox for 'Miner enabled' and then on the right the checkbox for 'Version enabled'. The textboxes and the 'Downloaded' checkbox are for informational purposes only and can not be changed. The user then has two choices for download, either by clicking the 'Download' button which will add the version to the download queue and download it immediately or just add it to the queue by clicking the 'Add to download queue' button. If the 'Start downloading' button on the 'Downloads' tab has been clicked and the queue has not finished it will get downloaded, otherwise it will get downloaded when the user clicks the 'Start downloading' button. Here the user can also choose which algorithms should be available to use for each miner, or even the miner version. Only algorithms enabled on the 'Algos' tab will be available in the grid. When checking or unchecking algorithms the 'Save' button will need to be clicked. The 'Save' button is only used for saving which algorithms should be available, otherwise the application will autosave when checking or unchecking the 'Miner enabled' and the 'Version enabled' checkboxes.


Settings -> Downloads
The downloads tab shows any active or queued downloads. Uf there are queued downloads, the queue can be started by clicking the 'Start downloading' button. Queued downloads will persist if the application is closed, and it will go to this tab at the next start to remind the user that there are downloads in the queue.


Settings -> Parameters
If the checkbox 'Use the same parameters for all devices' is checked on the appsettings tab, only the GPU will be enabled on this tab. While the user inputs parameters for the first GPU, the will be filled as well. If the checkbox is not checked the user will have to input parameters for each GPU that should be evaluated.
Be carefull on what parameters is used since the application does not check if they are within reason or not.

When the user clicks the save button the application calculates estimated time for the evaluation. As can be seen that time can be very excessive depending on the size of the increase steps set on the appsettings tab.

There are some options available to reduce the time an evaluation will take. The user can increase the level of the steps or change the ranges. The user can also run for example only power target first and find what percentage is sutiable, or if the user already knows what power target to use simply set that percentage as both low and high values. When setting a fixed power target the estimated time reduces a lot. Is using the random logic this evaluation would most likely take less than a day instead of almost five days to complete.


The results tab gathers all the successful runs and presents them i a grid that by default is sorted after hashrate. To resort the grid just click the header for the column you want to sort by, for example the "hash/watt" column header. When a new result is added to the grid it will reset the sorting and sort by hashrate again.
As soon as there are any results available it is possible to export the raw data that makes up the grid. Just remember that if you start a new evaluation the grid will not reset until the first successful run is complete. If a new evaluation has been started and you hit F8 while showing the results for old evaluation, there will bo no data in the export. So it is important to remember to export the data before saving parameters for a new evaluation. If you are using version 1.0 you may first need to activate the grid by clicking on any row. Starting with 1.0.1 it is possible to export the results without first activating the grid.
If you have Hash Auger installed and the integration is configured it is possible to export/update Hash Auger straight from the results tab. Select the GPU you want to update Hash Auger for and then double click on the desired row. If Hash Auger is not running it will be started to make the update possible, and be closed when the update is complete. Remember that Hash Auger needs to have the API configured to allow the execution of remote commands. Hash Auger will be updated with what miner and algorithm the result is for, power target, core clock offset, memory clock offset, intensity (is other than miner default), hashrate and hash/watt. And it will enable overclocking for the miner on the current algorithm. It will however not enable overclocking for the GPU if that is not done. That you need to do manually.

If Hash Auger is running the following two screens will show.

If Hash Auger is not running it will first be started.

This is how it can look in Hash Auger before and after the update is done.

Since the update provides both hashrate and hash/watt, Hash Auger will recalculate both the preferred miner (and change it if the updated miner performs better) and energy cost.

On the output tab the user can see what the miners (that supports redirection) output's to the console.


The details tab presents the current activity for each GPU. Here you start and stop evaluations. If you choose to stop for any reason the application will pick up where it left off when the respective start buttons are clicked again. To get the most correct results it is however important not to change anything in the rig before an evaluation is complete, or it might scew the results, for example if you stop to update the Nvidia drivers. Keep the rigs as they are if you are running an evaluation or restart the entire evaluation by going to the Settings -> Parameters tab and clicking save.

If you hover over the number for each GPU a small tooltip will popup with more information about each GPU.

If you hover over the dots for each GPU a small tooltip will popup with a short description of what they represent.


Developers fee
Developers fee in PG Miner Bench works a little different from other software. Max dev fee runtime is 18 minutes per 24 hours of evaluation runtime and is bound to each GPU. This means that only GPU's that are actually being evaluated will mine dev fee. If you have 6 GPU's in the system but is only evaluating 4 of them, only those 4 will mine dev fee.

This works by keeping track of each GPU's runtime and when a GPU is about to switch parameters a check will be done to see if the GPU has been running evaluations long enough for dev fee session to become active. Currently the minimum dev fee session time is 90 seconds. So if a GPU has not been running evaluations long enough to build up to a 90 second dev fee session the GPU will continue to run another evaluation run. If the accumulated dev fee session time is above 90 seconds the software will mine dev fee for that time.

PG Miner Bench will never stop a running evaluation run to mine dev fee, it will only mine dev fee between runs. This also means that not every dev fee session will be exactly 90 seconds, instead the time will vary and be different depending on the set round runtimes. A dev fee session that runs during round 1 will usually be shorter than a session running during round 2.

The meaning of this tab is to let the user decide if dev fee should be premined instead of being mined during evaluations. Any dev fee mined from this tab will be added to the total dev fee runtime. If you decide to mine 18 minutes of dev fee time on this tab the software will not mine any dev fee during evaluation for the next 24 hours of total GPU runtime.

Dev fee is currently mined using the latest version of Z-Enemy suited for the currently installed driver version. It will use the highest available power limit chosen from the currently set parameters but will never be higher than 100%. If the maximum power limit set for a GPU is 110%, dev fee session will run at 100%, and if set to 90% the dev fee session will run at 90%. No overclocking is used for mining dev fee. All dev fee will be mined on a predetermined pool and using a predetermined algorithm.

Visit The
Discord server for support or other questions.