v0.7.21 release.

todxx · Dec 17, 2020 · 3e76256 · 3e76256
1 parent baa3baf
commit 3e76256
Show file tree

Hide file tree

Showing 3 changed files with 57 additions and 46 deletions.
diff --git a/README.md b/README.md
@@ -1,4 +1,4 @@
-# teamredminer v0.7.20
+# teamredminer v0.7.21
 This is an optimized miner for AMD GPUs created by todxx and kerney666.
 
 **Download is available in the [github releases section](https://github.com/todxx/teamredminer/releases).**
@@ -16,6 +16,8 @@ Below is a list of mining operating systems and management software that have bu
 
 This miner supports a range of algorithms.  Please see the list below for details.  The miner is configured via command line only, please run with the --help option to print a short help message for how to use the command line options.
 
+**This miner supports mining ethash with 4GB Polaris GPUs after epoch 381 on linux.  Please see the guide [here](https://github.com/todxx/teamredminer/blob/master/doc/ETHASH_4GB_HOWTO.txt)**
+
 This miner includes the following algorithms and their respective dev fees:
 
 |        Algorithm          |  Fee |
@@ -100,6 +102,13 @@ For example command lines please see the batch/shell scripts in the miner downlo
 For command line options see the [USAGE.txt](USAGE.txt) file that comes with the miner.
 
 -----------
+Changes in v0.7.21
+
+Quick release that addresses situations where Ethash with capped DAG on 4GBs would crash after 5-10 mins when running at 4078-4080MB.
+
+Release notes:
+- Ethash: improved probability for high (4078-4080MB) ethash 4GB capped allocation running stable over time.
+
 Changes in v0.7.20
 
 Highlights:

diff --git a/USAGE.txt b/USAGE.txt
@@ -1,4 +1,4 @@
-          Team Red Miner version 0.7.20
+          Team Red Miner version 0.7.21
 Usage: teamredminer [OPTIONS]
 Options:
   -a, --algo=ALGORITHM      Selects the mining algorithm.  Currently available:

diff --git a/doc/ETHASH_4GB_HOWTO.txt b/doc/ETHASH_4GB_HOWTO.txt
@@ -1,6 +1,7 @@
 TeamRedMiner Ethash 4GB Status
 ==============================
 
+v1.3 - 2020-12-17 - Moved the extended mining section.
 v1.2 - 2020-12-13 - Rewrote Linux section before epoch 382.
 v1.1 - 2020-10-12 - Added Linux section and info around extended mining.
 v1.0 - 2020-10-04 - First version, Windows only.
@@ -112,6 +113,51 @@ Linux Instructions
 
    Fourth choice: shut down and sell the gpus.
 
+=========================================================================
+Extended Mining
+=========================================================================
+TRM v0.7.14 adds support for "extended mining". This means that you
+can continue to mine with 4GB gpus even when they can't store the full
+DAG for the epoch. However, since the full DAG isn't available, some
+hashes will be discarded and your hashrate will decrease for every
+additional epoch.
+
+This mode is enabled using the argument "--eth_4g_max_alloc=N". Please
+see the description in the --help output (or USAGE.txt), or in the
+instructions above. Windows users should try "--eth_4g_max_alloc=374",
+Linux users should try "--eth_4g_max_alloc=4078". If you get
+allocation errors on startup, or the miner crashes after the same
+amount of time every run, lower the number slightly until it
+works. For example, on amdgpu-pro 20.10, our tests crashed after
+exactly 7 mins every run. Lowering the value from 4078 to 4076 and it
+ran for days. Amdgpu-pro 19.30 could use 4078 with no issues.
+
+NOTE: extended mining means that the optimal intensities will change
+with each epoch. Therefore, the miner will reinitiate the auto-tune
+process for every epoch switch during extended mining unless manual
+intensities were given with --eth_config when the miner was started.
+
+This is an example table with 2 x Nitro+ 470 4GBs mining at 29.65 MH/s
+each at full speed, i.e. 59.30 MH/s total, having 4078MB of DAG buffer
+space available. Power draw will stay roughly the same, so your
+efficiency will take about the same hit as the hashrate.
+
+Epoch  DAG MB  DAG %    Hashrate  Loss %
+381    4072    100.00%  59.30       0.0%
+382    4080    99.95%   58.38      -1.6%
+383    4088    99.76%   54.89      -7.4%
+384    4096    99.56%   51.46     -13.2%
+385    4104    99.37%   48.29     -18.6%
+386    4112    99.17%   45.17     -23.8%
+387    4120    98.98%   42.17     -28.9%
+388    4128    98.79%   39.35     -33.6%
+389    4136    98.60%   36.80     -37.9%
+390    4144    98.41%   34.23     -42.3%
+395    4184    97.47%   22.46     -62.1%
+400    4224    96.54%   12.55     -78.8%
+
+Happy mining!
+
 =========================================================================
 Windows
 =========================================================================
@@ -254,47 +300,3 @@ Windows instructions
 
    Fifth choice: shut down and sell the gpus.
 
-=========================================================================
-Extended Mining
-=========================================================================
-TRM v0.7.14 adds support for "extended mining". This means that you
-can continue to mine with 4GB gpus even when they can't store the full
-DAG for the epoch. However, since the full DAG isn't available, some
-hashes will be discarded and your hashrate will decrease for every
-additional epoch.
-
-This mode is enabled using the argument "--eth_4g_max_alloc=N". Please
-see the description in the --help output (or USAGE.txt), or in the
-instructions above. Windows users should try "--eth_4g_max_alloc=374",
-Linux users should try "--eth_4g_max_alloc=4078". If you get
-allocation errors on startup, or the miner crashes after the same
-amount of time every run, lower the number slightly until it
-works. For example, on amdgpu-pro 20.10, our tests crashed after
-exactly 7 mins every run. Lowering the value from 4078 to 4076 and it
-ran for days. Amdgpu-pro 19.30 could use 4078 with no issues.
-
-NOTE: extended mining means that the optimal intensities will change
-with each epoch. Therefore, the miner will reinitiate the auto-tune
-process for every epoch switch during extended mining unless manual
-intensities were given with --eth_config when the miner was started.
-
-This is an example table with 2 x Nitro+ 470 4GBs mining at 29.65 MH/s
-each at full speed, i.e. 59.30 MH/s total, having 4078MB of DAG buffer
-space available. Power draw will stay roughly the same, so your
-efficiency will take about the same hit as the hashrate.
-
-Epoch  DAG MB  DAG %    Hashrate  Loss %
-381    4072    100.00%  59.30       0.0%
-382    4080    99.95%   58.38      -1.6%
-383    4088    99.76%   54.89      -7.4%
-384    4096    99.56%   51.46     -13.2%
-385    4104    99.37%   48.29     -18.6%
-386    4112    99.17%   45.17     -23.8%
-387    4120    98.98%   42.17     -28.9%
-388    4128    98.79%   39.35     -33.6%
-389    4136    98.60%   36.80     -37.9%
-390    4144    98.41%   34.23     -42.3%
-395    4184    97.47%   22.46     -62.1%
-400    4224    96.54%   12.55     -78.8%
-
-Happy mining!