[Update] todxx/teamredminer: AMD GPU Optimized Cryptocurrency Miner | navi team – Vietnamnhanvan

navi team: นี่คือโพสต์ที่เกี่ยวข้องกับหัวข้อนี้

teamredminer v0.8.6.3

This is an optimized miner for AMD GPUs created by todxx and kerney666.

Download is available in the github releases section.

TRM official website: https://www.teamredminer.com

TRM discord server: https://discord.gg/RGykKqB

Below is a list of mining operating systems and management software that have built-in support for teamredminer:

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

This miner includes the following algorithms and their respective dev fees:

Algorithm
Fee

Ethash on Polaris GPUs
0.75%

Ethash on all other GPUs
1.0%

Kawpow
2.0%

Verthash
2.0%

Autolykos2
2.0%

Nimiq
2.5%

Cryptonight R
2.5%

Cryptonight v8 upx2
2.5%

Cryptonight v8 turtle
2.5%

Cryptonight v8 half
2.5%

Cryptonight v8 double
2.5%

Cryptonight v8 rwz
2.5%

Cryptonight v8
2.5%

Cryptonight heavy
2.5%

Cryptonight haven
2.5%

Cryptonight saber
2.5%

Cryptonight conceal
2.5%

Chukwa-512 (Turtlecoin)
2.5%

Chukwa-1024 (Turtlecoin)
2.5%

x16r
2.5%

x16rv2
2.5%

x16s
2.5%

x16rt
2.5%

MTP
2.5%

Cuckatoo31
2.5%

Cuckarood29
2.5%

Lyra2rev3
2.5%

Lyra2z
3.0%

Phi2
3.0%

GPUs supported and tested:

  • Navi – RX 5700(XT)/5600(XT)/5500(XT) for supported algos in the table below.
  • Big Navi – RX 6900XT, RX 6800(XT), RX 6700(XT), RX6600XT – same support as for Navi.
  • Vega – RX Vega 64/56, Vega FE, Radeon VII (Vega 2)
  • Polaris – RX 580/480/570/470/560/460/550
  • Fiji – R9 Fury/Fury X/Nano, MI8 (supported but with very limited testing).
  • Tonga/Antigua – R9 285/285X/380/380X, W7100, S7150 (beta support from 0.8.2. Only ethash+kawpow available.)

Some algorithms are not supported on some GPU architectures and/or drivers. Below is the compatiblity table:

Navi
Vega
Polaris
Fiji
Tonga

Ethash
Y
Y
Y
Y
Y

Kawpow
Y
Y
Y
Y
Y

Verthash
Y
Y
Y
Y
N

Autolykos2
Y
Y
Y
Y
Y

Firopow
Y
Y
Y
Y
Y

Nimiq
Y
Y
Y
Y
N

Cryptonight R
N
L
L
L
N

Cryptonight v8 upx2
N
L
L
L
N

Cryptonight v8 turtle
N
L
L
L
N

Cryptonight v8 half
N
L
L
L
N

Cryptonight v8 double
N
L
L
L
N

Cryptonight v8 rwz
N
L
L
L
N

Cryptonight v8
N
L
L
L
N

Cryptonight heavy
N
L
L
L
N

Cryptonight haven
N
L
L
L
N

Cryptonight saber
N
L
L
L
N

Cryptonight conceal
N
L
L
L
N

Chukwa-512
N
L
L
L
N

Chukwa-1024
N
L
L
L
N

x16r
N
Y
Y
Y
N

x16rv2
N
Y
Y
Y
N

x16s
N
Y
Y
Y
N

x16rt
N
Y
Y
Y
N

MTP
Y
Y
Y
Y
N

Cuckatoo31
N
Y
Y
Y
N

Cuckarood29
N
Y
Y
Y
N

Lyra2rev3
N
L
L
L
N

Lyra2z
N
L
L
L
N

Phi2
N
L
L
L
N

Support legend:

  • Y = Supported
  • N = Not supported
  • L = Limited support: algos are supported on windows and linux with amdgpu-pro drivers, not supported on ROCm drivers.

The miner reports GPU hash rates every 30 seconds. These are the full GPU hash rates before dev fee deduction (your pool hashrate will be slightly lower).

The miner includes a read-only api based on the sgminer-5.5 API. Both the json and text formats are supported. For more details, we refer to the sgminer api documentation.
The miner also includes a Claymore miner compatible API with support for a subset of the API.

For reporting bugs and/or for features requests, please open an issue on this project’s github issue tracker.

For example command lines please see the batch/shell scripts in the miner download packages.
For command line options see the USAGE.txt file that comes with the miner.

Changes in v0.8.6.3

Release notes:

  • Autolykos2: emergency release to support larger pad size from block 614400. Some GPUs (mainly Vegas) will need higher core clocks to achieve the same performance as previous versions due to larger pads breaking some previous optimizations. More optimizations to come in future releases.
  • Autolykos2: added argument –autolykos_ignore_diff for certain pools that aren’t compatible with the ERGO reference miner pool implementation.
  • Progpow: fixed wrong –help text for –prog_micro_tune.

Changes in v0.8.6.2

Release notes:

  • Firopow/MTP: added a synthetic algo ‘mtp_firopow’ that will use the correct algo given the system time and shut down the miner at the time of the Firo fork on Oct 26.
  • Ethash/progpow: split the ethash and progpow algos into separate binaries, mainly for some Vegas that ran into stability issues going from 0.8.5 to 0.8.6.
  • Autolykos2: added support for Tonga.
  • Advanced SSL usage: changed the default SSL behavior to not provide a SNI hostname during handshake. See the updated –help section on the -o argument for how to force a SNI hostname being sent.

Changes in v0.8.6.1

Internal test version – unreleased.

Changes in v0.8.6

Release notes:

  • Firopow: new algo added for Firo’s upcoming fork (see start_firo.sh/bat). Only testnet mining is available before the fork, see start_firo_testnet.sh/bat.
  • Firopow/kawpow: rewrote tuning guide (see KAWPOW_FIROPOW_TUNING.txt).
  • Firopow/kawpow: slight hashrate improvements, mainly from choosing full gpu tuning by default and adding a micro-tuning mechanism for Polaris gpus (see new argument –prog_micro_tune).
  • Autolykos2: added high score support and display of submitted share difficulty.
  • General: fixed Radeon VII support on recent win drivers. NOTE: HBCC must be DISABLED for all Vegas.
  • General: fixed broken fan control for Navis on some driver versions.
  • General: improved Windows compute mode enable with automatic elevation (with –uac) and restart of gpus.

Changes in v0.8.5

Release notes:

  • General: added Windows clocks/voltage/built-in timings control (beta functionality). See section in –help and CLOCKS_VOLTAGE_CONTROL.txt.
  • General: fixed some issues with Windows fan control, mostly for Big Navi gpus.
  • General: added mem temp limits (stop/resume), see –mem_temp_limit and –mem_temp_resume.
  • Ethash: added support for forcing ethash pool hashrate reports (see –eth_hash_report).
  • Ethash: fixed hashrate reports for Crazypool when using failover pools.
  • Autolykos2: added extranonce subscription support for e.g. Nicehash.

Changes in v0.8.4

Release notes:

  • General: Added fix for failure to load GPU kernels on newer drivers, e.g. Big Navi on Adrenalin 21.6.x.
  • Emergency patch: fixed Haven mining generating mostly hw errs after the recent hard fork.

Changes in v0.8.3

Release notes:

  • General: added Autolykos2 algo for ERGO (very good target for Vega 56/64, see the AUTOLYKOS_TUNING.txt guide).
  • General: improved and simplified dual ZIL mining for ethash/kawpow/verthash/autolykos2 (see the new DUAL_ZIL_MINING.txt guide).

Changes in v0.8.2.1

Release notes:

  • Bugfix: fixed windows issue with intermittently reading zero gpu stats and blasting fans (bug in 0.8.2).
  • Verthash: added –verthash_max_uploads=N to control the upload of the verthash table to gpus at startup. Some chipsets get issues running > 4 gpus concurrently. Typical error is that multiple gpus die immediately at startup when running the full rig, but work fine if you only run 3-4 gpus.
  • Verthash: fixed support for 550 2GB gpus.

Changes in v0.8.2

Release notes:

  • General: added Verthash algo for Vertcoin.
  • General: added Tonga and Antigua support for ethash and kawpow.
  • General: extended support to 24 gpus (previously max 16 gpus possible).
  • General: better handling of driver issues related to gpu clocks/temps stats.
  • General: now showing sensor power in stats output.
  • General: fixed device name parsing in ROCm 4.1 and newer win drivers.
  • API: added sensor power, jnct temp and mem temp to API output.
  • Ethash: added –eth_micro_delay for weaker psus (see help section for details).
  • Ethash: fixed watchdog DEAD gpus on small gpus building kawpow DAG.
  • Kawpow: now working fully with MiningPoolHub, regardless of bad seedhash values.

Changes in v0.8.1.1

Release notes:

  • Patched v0.8.1 with new devices ids for 6700XT support.

Changes in v0.8.1

Release notes:

  • General: basic Big Navi support added (ethash, kawpow, mtp, nimiq supported algos).
    See the ETHASH_TUNING_GUIDE.txt for a short section on Big Navis.
    Driver support missing on Windows for fan control and mem temp.
  • Ethash: display gpus now use A-mode by default to prevent failed allocation and low hashrates.
  • Stats: handling of negative temperatures under Linux.
  • Eth+zil: added new pool strategy ‘min_epoch’ for dual pool connection switching (see start_zil_eth.bat/.sh example script).

Changes in v0.8.0

Biggest release in a long while with rewritten ethash kernels and new mining modes for all gpu types!

Users are highly(!) recommended to take a few minutes to read the 0.7-to-0.8 migration guide and the new ethash tuning guide. Key highlights:

  • Polaris: Efficiency and slight hashrate increase. B-mode reintroduced for added hash. B-mode must be enabled with –eth_aggr_mode or –eth_config=Bxxx.

  • Vega 56/64: greatly improved base kernel for efficiency. New B-mode that can shave off additional 1-2W on top of the A-mode kernel. B-mode must be enabled manually with –eth_config (–eth_aggr_mode does not apply). Tuning numbers have changed – do NOT keep your old static –eth_config values.

  • Radeon VII: huge boost with its new C-mode but requires a special Linux setup. Can now do 100 MH/s on most air cooled VIIs. See tuning guide.

  • 5700/5700XT: can shave off as much as 8-9W(!) of power using the new B-mode and dropping core clk+voltage. B-mode now the default mining mode. Unless you retune your core clk+voltage you will see a tiny power draw increase instead and not benefit from the upgrade, so read the migration guide.

  • 5600XT: new B-mode has a much smaller effect. A-mode remains the default mining mode. See new tuning guide for more details.

  • The dag cache is NOT compatible with the new B/C-modes. ETH+ZIL switchers have to choose between caching the epoch 0 dag and using the new mining modes.

  • Ethash 4GB kernels NOT rewritten in this release, performance remains the same as in 0.7.x.

  • See the migration guide for hashrate and power draw comparisons between 0.7.21 and 0.8.0.

Release notes:

  • Ethash: VII kernel rewrite and new C-mode with boost feature (see guide).
  • Ethash: Navi kernel slight optimization and new B-mode for lower core clock and power.
  • Ethash: Vega kernel rewrite and new B-mode for lower core clock and power.
  • Ethash: Polaris kernel rewrite and new B-mode for slightly higher perf.
  • Ethash: added share processing timeout and default for Binance pool (see –pool_share_limit_ms).
  • Claymore API: fixed leak that stopped serving requests after 32k api calls.
  • Claymore API: added password support (see –cm_api_password).
  • Logging: added log rotation support (see –log_rotate).
  • Logging: log files now contain the miner welcome message so the version is stored.
  • Kawpow: now mining ok at MiningPoolHub even though their seedhash is broken.
  • Fan control: added min/max fan speed range (see –fan_control).
  • General: added argument to turn off duplicate pci bus id filtering (see –allow_dup_bus_ids).

Changes in v0.7.23

None – discarded as internal test version.

Changes in v0.7.22

Highlights:

  1. NAVI KERNEL REWRITE! Over the last month we’ve been working on new kernels. The first one released is for Navi. The main feature is lower power consumption, hashrate will remain about the same but depends somewhat on clocks. NOTE: please let the miner retune any existing –eth_config arguments for all Navi gpus, the new values will be significantly lower.

  2. Claymore API now supported, meaning you can use EthMan to monitor TRM rigs.

Release notes:

  • Ethash: Kernel rewrite for Navi. Should now be more stable and use less power. Vega/Polaris still in the works.
  • General: Slightly reworked init procedure again to address some rigs running better on <= 0.7.18 than >= 0.7.19.
  • General: Added Claymore compatible API, see the –cm_api_listen option.

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:

ETH is now approaching the start of the 4GB death with the upcoming switch to epoch 382. TRM was the first miner to add support for mining with 4GB gpus with a partial DAG, here called “extended mining”. However, it has always required manual configuration. This release adds a default conservative cap at 4072MB for DAG storage on 4GB gpus for out-of-the-box execution of the miner. For maximum performance, miners are still advised to manually tune their rig(s) with the –eth_4g_max_alloc argument. Most rigs runs stable with a higher value than 4072, which makes a significant difference for upcoming ETH epochs.

For more detailed instructions, our Ethash 4GB guide has also been updated and is available at https://github.com/todxx/teamredminer/blob/master/doc/ETHASH_4GB_HOWTO.txt

Release notes:

  • Ethash: added default capped DAG allocation for 4GBs at 4072MB (see –eth_4g_max_alloc).
  • Ethash: bugfix for crashes using –eth_dag_cache on 4GB gpus.

Changes in v0.7.19

Highlights:

  1. Ethash solo-miner share high-score list added, use –high_score to enable.

  2. Ethash single buffer dag for a small power save. Only available on recent drivers and should in theory always be an improvement. It is not verified 100% stable yet and therefore not the default in this version. Enable with –eth_dag_buf=A to test.

  3. Miner gpu initialization procedure rewritten. The init procedure should now hopefully be much more stable, especially on Navis in general and even more so for 5600(XT)s.

Release notes:

  • General: added adjustable ratio support for quota and load_balance pool strategies (see –pool_ratio).
  • General: rewrote the miner init procedure to be more stable in general.
  • General: fixed issue where output blocking could cause mining work to stop.
  • General: reduced main binary size.
  • Ethash: reintroduced single DAG buffer support for recent drivers allowing large single allocations (see –eth_dag_buf).
  • Ethash: added high score list of the 15 highest value shares found since start (see –high_score).
  • Ethash: small improvements in keeping the gpu busy over epoch switches.
  • Ethash: fixed bug that would cause deadlocks in rare occasions.
  • Ethash: bugfix – dag cache wasn’t enabled for 4GB gpus.

Changes in v0.7.18

  1. Support for the ETC fork added. Run with “-a etchash” for easiest support, see “–eth_variant_mode” in the help for more info.

  2. ETH+ZIL miners: add “–eth_dag_cache=0” to use a second dag cache and prebuild epoch 0 immediately at miner start.

  3. Ethash miners relying on ramp-up and stagger for stability: the default mode of these tweaks has been changed to off. They now need to be enabled with –eth_ramp_up and –eth_stagger. While helping a number of rigs, these tweaks caused increased instability of others, making the choice of a good default mode difficult.

See also  JAKIRO WITH IMBA Macropyre AMPLIFIED WildAxes AND ROSH KILLING SpiritSiphon - DOTA 2 CHC | macropyre

Release notes:

  • Added etchash support (see algo etchash and –eth_variant_mode).
  • Added dag cache support, mostly intended for eth+zil mining (see –eth_dag_cache).
  • Fixed hex char parsing in enable/disable submenu, can now work with >= 10 gpus.
  • Changed the default for ethash ramp-up and staggering to false (see –eth_ramp_up and –eth_stagger).
  • Added check for broken win setups with duplicated opencl platforms and/or devices.

Changes in v0.7.17

Release notes:

  • BETA: Added fan control, see –help section or USAGE.txt. Enable with –fan_control.
  • Fixed deadlock bug that could happen when using multiple pools with the failover strategy.
  • Added option for not sending stale shares (see –no_stale_submit).
  • Added watchdog check for early gpu init hangs.
  • Added example watchdog scripts for win/linux.

Changes in v0.7.16c

BETA RELEASE – small fixes for Turtlecoin’s new algo chukwa2.

Release notes:

  • Chukwa2: fixed kernels loading for Radeon VII gpus.
  • Chukwa2: fixed mem footprint for 2GB gpus.

Changes in v0.7.16b

BETA RELEASE – adds Turtlecoin’s new algo chukwa2. Not tested as rigorously as other versions. Only use for the Turtlecoin fork.

NOTE: Navi gpus are NOT supported on chukwa2 for now. Support will be added if there’s sufficient interest.

Release notes:

  • Added algo trtl_chukwa2 for the Turtlecoin fork on 2020-10-22.

Changes in v0.7.15

Small bugfix release.

Release notes:

  • Ethash: fixed bug for ZIL (epoch 0) mining on 4GB gpus (bug appeared in 0.7.14).
  • Ethash: reverted to v0.7.10 kernels for stability purposes except for ROCm-based rigs.

Changes in v0.7.14

This release wraps up our work for 4GB gpus mining ethash. Linux 4GB are verified to mine up to and including epoch 381 on drivers 18.50/19.30/19.50/20.10. After that, we have added support for extended mining from epoch 382 and up. Extended mining is a trade-off between hashrate and being able to mine at all, gpus will lose additional hashrate for every extra epoch. Please see the Linux section in the ETHASH_4GB_HOWTO.txt for more details and instructions.

Release notes:

  • Ethash: verified Linux support for 4GB gpus up to and including epoch 381.
  • Ethash: added support for extended 4GB mining from epoch 382 and up.
  • Kawpow: cleaned up false hw errs for some block heights.

Changes in v0.7.13

  1. Windows user with 4GB rigs – see the new guide ETHASH_4GB_HOWTO.txt for instructions.

Release notes:

  • Added better default Windows dag allocation strategy on 4GB gpus.
  • Added experimental support for resetting gpus before mining (Windows only).
  • Added argument for manual adjustment of 4GB dag allocation (see –eth_4g_alloc_adjust=X,Y,Z,…).
  • Added protection against broken dev servers with additional random server selection mechanism.

Changes in v0.7.12

  1. Bugfix release: v0.7.11 could crash with rejected ethash shares.

Release notes:

  • Fixed print format bug on ethash rejected shares.

Changes in v0.7.11

  1. Ethash additions: printing share diff in GH (always enabled), hashrate watchdog (see –eth_hashwatch).
  2. Better debug support: –long_timestamps, –pool_debug.
  3. We’ve found certain motherboard/bios combinations that due to kernel and/or driver bugs have issues with the first or last gpu in rigs. If you see excessive hw errors reported on a single gpu, and switching around gpus still always generates errors in the first or last gpu, try using –eth_dag_alloc_patch.

Release notes:

  • Added DAG allocation patch under linux for certain mobo/bios combinations (see –eth_dag_alloc_patch).
  • Added ethash hashrate watchdog (see –eth_hashwatch).
  • Added ethash abort mechanism for Vegas on ROCm (see –eth_direct_abort). Not useful in other contexts.
  • Added pool traffic debug (use –pool_debug).
  • Added print of share difficulty for ethash family algos. Unit is always GH.
  • Added microsec timestamp resolution in logs (use –long_timestamps).
  • Regression bug: argon2/chukwa was broken in 0.7.10, now working again.
  • Turned off compute mode checks for non-Polaris gpus.

Changes in v0.7.10

Release notes:

  1. Ethash 4GB rigs, especially on win, should use –eth_alloc_epoch=N with N being the max epoch that the gpus can allocate. This will avoid DAG reallocation issues.
  2. For Navi rigs having issues with eth+zil or Nicehash mining with frequent DAG switching, try using –eth_dag_slowdown=9.
  • Added default log filename (trm__<yyyymmdd_hhmmss>.log)
  • Added ethash forced initial allocated epoch ( –eth_alloc_epoch=N). Note: HIGHLY recommended for 4GB rigs.
  • Added ethash family DAG build slowdown configuration (–eth_dag_slowdown=N, default value 4).
  • Added ethash family DAG build staggering across gpus (disable with –eth_no_stagger).
  • Added ethash family intensity ramp-up (disable with –eth_no_ramp_up).
  • Added option for forcing dev fee region (see –dev_location).
  • Added MTP for Navi gpus.
  • Added MTP ramp-up after pad rebuild.
  • Fixed error printouts on failed watchdog script execution on Linux.
  • Stats: now shows more clocks and temps, and also adds gpu state in hashrate prints (see –short_stats to disable).
  • Added checks for and enabling compute mode and disabling crossfire on Windows (see –enable_compute).

Changes in v0.7.9

  • Fixes for mixed rig mining on Linux.
  • Added –eth_epoch argument for easier epoch testing.
  • Added –eth_aggr_mode for automatic aggressive ‘B’ mode on Polaris 8GB gpus.
  • Added –watchdog_disable argument.

Changes in v0.7.8

  • Upgrade for the upcoming Haven hard fork (July 20, 2020).
  • Tiny Nimiq optimizations (1-2% max, mostly Vega and Navi).
  • Fixed CPU usage issue when redirecting stdin to /dev/null.
  • Fixed pool name returned by API for Nimiq.

Changes in v0.7.7

  • Added support for Nimiq Polaris/Vega (dumb mode only).
  • Integrated a Nimiq node.js network proxy into the miner.
  • Fixed Nimiq bug that could lose shares, especially against lower vardiff pools.
  • Fixed Nimiq bug that could cause duplicate shares on startup for low-diff pools.
  • Fixed regression bug for ethash Nicehash, correct stratum mode now used again.
  • Added support for Nimiq Navi.
  • Added support for icemining Nimiq solo mining mode (set -p m=solo).

Changes in v0.7.6

  • Fixed broken keyboard input in tmux+screen sessions (e.g. Hive OS).
  • Added support for 5500(xt).
  • Fixed Linux watchdog support for hard driver crashes (script was not executed).
  • Fixed kawpow nicehash extranonce support.

Changes in v0.7.5

  • Fixed broken optimizations for kawpow in 0.7.4.

Changes in v0.7.4

  • Increased ethash support on 4GB GPUs up to epoch 380-383
  • Implemented split ethash dag buffers for 8GB GPUs to support DAGs over 4GB
  • Kawpow optimizations (Navi +2.25%, Vega +1.25%, Polaris +0.25%)
  • Added gpu enable/disable API support.
  • Windows TDR detection/handling/warning.
  • Monitor detection on Windows/Linux with intensity adjustment.
  • Fix for ethash pool hashrate reporting stopping after network outage.

Changes in v0.7.3

  • Emergency patch for 4GB cards to handle a few more ETC epochs.
    A more complete patch is coming out shortly.

Changes in v0.7.2

  • Fixed kawpow dag build DEAD gpu issue on windows Adrenalin 2020 drivers.
  • Fixed Navi 5600(xt) support on windows.
  • Fixed mining on Vegas on older amdgpu-pro drivers.
  • Fixed ADL reporting of stats on windows for newer cards.

Changes in v0.7.1

  • Fixed issue with VII ethash/kawpow on windows.

Changes in v0.7.0

  • Added kawpow algo for Ravencoin.
  • Added Navi support for kawpow and ethash.
  • Changed device ordering to be pcie bus based by default, added –opencl_order option.
  • Fixed issue with –list devices not working without other args.
  • Reformatted help message to hopefully make it easier to read.
  • Added multipool example scripts.
  • Removed ssl/tls server name verification (was re-added with TLS SNI fix)
  • Fixed an unhandled signal bug that would cause rare crashes.
  • Fixed multi-pool API bug.

Changes in v0.6.1

  • Added pool failover and load balancing.
  • Added better error messages when failing to allocate eth DAG buffers.
  • Added server name for TLS SNI.
  • Added automatic setting for environment variables for 4GB GPUs.
  • Extended maximum length of usernames and passwords (for some merged mining setups).
  • Added report of pool stats.
  • Changed initial pool auto detect mode to eth proxy.
  • Various fixes for submitting hashrate to pools.

Changes in v0.6.0

  • Added ethash support.
  • Relaxed ssl/tls cert chain verification.

Changes in v0.5.9

  • Added x16rv2 for the upcoming Ravencoin fork.
  • Optimization work on x16r: +8-10% hashrate depending on clocks.
  • Optimization work on x16r: mem clock no longer as important.
  • Issue fix: kernels split into multiple binaries to fix linux amdgpu-pro driver issues.

Changes in v0.5.8

  • Added Chukwa-512 algo For Turtlecoin (trtl_chukwa).
  • Issue fix: kernels not loaded properly for Conceal.
  • Issue fix: added logic for pool reconnect on N rejected shares in a row (see –pool_max_rejects=N).

Changes in v0.5.7

  • Added CN conceal algo for Conceal (CCX).
  • Added cuckarood29 algo for grin.

Changes in v0.5.6

  • MTP improvements for Vega and Polaris (+1-3% hashrate, improved efficiency, esp Polaris)

Changes in v0.5.5

  • Added cuckatoo31 algo for grin.

Changes in v0.5.4

  • Fixed API bug for MTP, crashing when using Awesome Miner.
  • Small MTP improvements, mostly for Polaris.

Changes in v0.5.3

  • Added MTP algo for Zcoin/XZC (please read MTP_MINING.txt before mining).
  • Further small stabilization fixes for CN variants, primarily 4MB algos.

Changes in v0.5.2

  • Bugfix release only, no new added algos or features.
  • Fix for 1-2% degraded hashrate on Radeon VIIs in some scenarios.
  • Fix for Radeon VII allocation bug, causing hw errs.
  • Fix for allocation bug causing crashes for some drivers and gpus.

Changes in v0.5.1

  • Added better support for CN intensities 16*15, use –allow_large_alloc under Linux.
  • Added –no_ntime_roll for mining x16rt on e.g. bsod.pw.
  • Added Tonga device recognition.
  • Better error reporting for pool communication issues.

Changes in v0.5.0

  • Added cryptonight 4MB variants: heavy, haven and saber.
  • Added x16 algo suite: x16r, x16s, x16rt (both gin and veil).
  • Auto-tuning mode for all CN variants, see bundled guide.
  • Manual key-driven CN tuning mode available inside the miner.
  • Additional data in miner stats console output.
  • Watchdog now detecting single stuck thread when mining CN.
  • Fix: in rare cases, poolside hash for compute algos (lyra2z, phi2, lyra2rev3) only reached ~95% of expected value.

Changes in v0.4.5

  • Added cryptonight v8 upx2 for the uPlexa coin fork.
  • Reworked init procedure, added retry logic on comm errors.
  • Added section on temps to the CN_MAX_YOUR_VEGA guide.
  • Added a new howto MAP_YOUR_GPUS describing how to map gpus between miner/tools/registry.

Changes in v0.4.4

  • Added * mode specifically for modded timings on Vega GPUs. Use with e.g. –cn_config=15*15. This mode is now the default for Vegas.
  • Introduced slow start/ramp-up. Threads increase their workload slowly at start or restart after e.g. a network outage.
  • Added interleave adjustment logic. Readjusts the two threads per gpu over time to make sure they don’t gravitate and get stuck.
  • Added support for forcing colors (–force_color) for windows redirected consoles (git bash, cygwin, node.js).
  • Added hotkey menu system (show stats, enable/disable gpu).

Changes in v0.4.3

  • Added cryptonight v8 turtle (–algo cnv8_trtl) algo for coins such as turtle coin and loki.
  • Added support for running CN mining single-threaded using Y+0 configurations.
  • Changed the auto config mode for Radeon VII to L30+0 as a temporary setting.

Changes in v0.4.2

  • Added cryptonight v8 half (–algo cnv8_half) algo for coins such as stellite and masari.
  • Added cryptonight v8 double (–algo cnv8_dbl) algo for coins such as x-cash.
  • Added cryptonight v8 reverse waltz (–algo cnv8_rwz) algo for coins such as graft.
  • Added support for running devices on multiple OpenCL platforms.
  • Fixed more issues with console colors on older windows versions.
  • Added more cpu verification optimization for CN/R. CN/R cpu usage should decrease ~70%.

Changes in v0.4.1

  • Removed server name verification for SSL connections. (Pools like supportxmr now work with SSL)
  • Fixed bug causing GPUs to fail to initialize on some systems.
  • Fixed bug causing GPUs to only run one thread (but display 2x hashrate)
  • Fixed bug where having GPU_MAX_WORKGROUP_SIZE set too high would cause GPUs to crash.
  • Fixed bug where older windows versions would get no console output.
  • Added work-around for driver bug in linux amdgpu-pro drivers resulting in low pool-side hash for polaris cards in rare cases.
  • Added some cpu verification optimizations. CN/R cpu usage should decrease about 15%.

Changes in v0.4.0

  • Added cryptonight R support. (–algo cnr)
  • Added support for ssl/tls pool connections using the stratum+ssl:// prefix.
  • Added colors (and an option to disable them).
  • Slight performance increase for lyra2rev3 (~0.5%).
  • Fix for occasional crashes when pool disconnects.
  • Added more messages regarding not being connected to dev pool.
  • Changed printing to not block mining progress if stdout writes block.

Changes in v0.3.10

  • Slight performace improvement for Vegas on lyra2rev3
  • Pool stratum protocol work-arounds for some pools, fixing duplicate share error.
  • Changed handling of unrecognized pool rpcs to be ignored instead of causing a reconnect.
  • Fix for duplicate shares on 480/580/Vega56 cards with lyra2rev3.

Changes in v0.3.9

  • Added support for lyra2rev3 amdgpu-pro and windows. ROCm support coming in later version.
  • Fixed API bug with not reporting dead GPUs

Changes in v0.3.8

  • Added support for fan speed and temperatures.
  • Added watchdog function for gpu init stuck, dead gpu, over-temp gpu, and non-responding pool.
  • Added new optional ‘L’ config prefix for low-end cards like lexa/baffin for a 10+% speed-up on some cards
  • Added an option for writing out a log file.
  • Added cycling through multi-entry dns records when connecting to pools.
  • Added a pool-connect timeout.
  • Added measurement and displaying of pool response times.
  • Added support for 80-byte headers for Phi2 algo (for non-LUX coins).
  • Slightly tuned the ‘+’ mode for polaris, some GPUs will show slight performance increase.
  • Fixed bug with API interface occasionally getting stuck.

Changes in v0.3.7

  • Redesigned GPU initialization, should now be less error prone.
  • Added clean shutdown to reduce driver/GPU crashes.
  • Added staggered GPU start-up to reduce GPU crashes.
  • Added CPU verification for CNv8 and associated –no_cpu_check option.
  • Fixed crash on pool authentication error.
  • Added –pool_broken_rpc work-around option for pools that violate json rpc spec.
  • Added option to reorder by PCIe bus numbers.
  • Added –list_devices option to show available devices.
  • Added changed stats formatting to indicate which numbers are accepted/rejected/hw-error shares.
  • Added uptime to stats.

Changes in v0.3.6

  • Added support for Rx550 cards (gfx804).
  • Improved stability on larger rigs, especially with weaker cpus.
  • Improved error reporting on failed initialization.

Changes in v0.3.5

  • Changed GPU initialization to be sequential by default and added –init_style option for faster init styles.
  • Fixed network buffer size issue preventing the use of very long usernames/passwords/rig_ids.
  • Added opencl platform auto-detection for AMD platforms when –platform is not specified.

Changes in v0.3.4

  • Added CryptoNight v8 (CNv2) support
  • Changed stats display to include pool hashrate and better formatting
  • Added parallel GPU initialization
  • Added output of submitted/accepted/rejected shares.
  • Changed hashrate reported to be full GPU hashrate (previously hashrate reported was after dev fee deduction)
See also  Souma bỏ thuốc vào đồ ăn và cái kết bay đồ.. | soma reddit

Changes in v0.3.3

  • ROCm support reintroduced
  • API support based on the sgminer API
  • Improved GPU platform detection
  • PCIe bus id printed on startup and is available over API
  • Added option for periodic stats interval

Changes in v0.3.2

  • Added windows support/build
  • Added vega PAL driver support
  • Removed ROCm support (temporarily)
  • Removed libjansson dependency

Changes in v0.3.1

  • Fixed phi2 issues causing rejected shares and low pool-side hashrate.

[NEW] AMD Big Navi and RDNA 2 GPUs: Everything We Know | navi team – Vietnamnhanvan

AMD Big Navi, RX 6000, Navi 2x, RDNA 2. Whatever the name, AMD’s latest GPUs promise big performance and efficiency gains, along with feature parity with Nvidia in terms of ray tracing support. Team Red finally puts up some serious competition in our GPU benchmarks hierarchy and provides several of the best graphics cards, going head to head with the Nvidia Ampere architecture.

AMD officially unveiled Big Navi on October 28, 2020, including specs for the RX 6900 XT, RTX 6800 XT, and RTX 6800. The Radeon RX 6800 XT and RX 6800 launched first, followed by the Radeon RX 6900 XT. In March 2021, AMD released the Radeon RX 6700 XT, and more recently the Radeon RX 6600 XT. So far, we haven’t seen a trimmed down Navi 22 variant (except in mobile), and AMD instead opted to create Navi 23, the smallest ‘Big Navi’ GPU to date at less than half the size of Navi 21. We’ve updated this article with revised details, though there are still future RDNA2 products yet to be revealed.

Based on what we’ve seen, Big Navi has finally put AMD’s high graphics card power consumption behind it. Or at least, Big Navi is no worse than Nvidia’s RTX 30-series cards, considering the 3080 and 3090 have the highest Nvidia TDPs for single GPUs ever. Let’s start at the top, with the new RDNA2 architecture that powers RX 6000 / Big Navi / Navi 2x. Here’s everything we know about AMD Big Navi, including the RDNA 2 architecture, specifications, performance, pricing, and availability.

Big Navi / RDNA2 at a Glance

  • Up to 80 CUs / 5120 shaders
  • 50% better performance per watt
  • Launched November 18 (RX 6800 series) and December 8 (RX 6900 XT)
  • Pricing of $379 to $999 for RX 6600 XT to RX 6900 XT
  • Full DirectX 12 Ultimate support

(Image credit: AMD)

The RDNA2 Architecture in Big Navi 

Every generation of GPUs is built from a core architecture, and each architecture offers improvements over the previous generation. It’s an iterative and additive process that never really ends. AMD’s GCN architecture went from first generation for its HD 7000 cards in 2012 up through fifth gen in the Vega and Radeon VII cards in 2017-2019. The RDNA architecture that powers the RX 5000 series of AMD GPUs arrived in mid 2019, bringing major improvements to efficiency and overall performance. RDNA2 doubled down on those improvements in late 2020.

First, a quick recap of RDNA 1 is in order. The biggest changes with RDNA 1 over GCN involve a redistribution of resources and a change in how instructions are handled. In some ways, RDNA doesn’t appear to be all that different from GCN. The instruction set is the same, but how those instructions are dispatched and executed has been improved. RDNA also added working support for primitive shaders, something present in the Vega GCN architecture that never got turned on due to complications.

Perhaps the most noteworthy update is that the wavefronts—the core unit of work that gets executed—have been changed from being 64 threads wide with four SIMD16 execution units, to being 32 threads wide with a single SIMD32 execution unit. SIMD stands for Single Instruction, Multiple Data; it’s a vector processing element that optimizes workloads where the same instruction needs to be run on large chunks of data, which is common in graphics workloads.

This matching of the wavefront size to the SIMD size helps improve efficiency. GCN issued one instruction per wave every four cycles; RDNA issues an instruction every cycle. GCN used a wavefront of 64 threads (work items); RDNA supports 32- and 64-thread wavefronts. GCN has a Compute Unit (CU) with 64 GPU cores, 4 TMUs (Texture Mapping Units) and memory access logic. RDNA implements a new Workgroup Processor (WGP) that consists of two CUs, with each CU still providing the same 64 GPU cores and 4 TMUs plus memory access logic.

How much do these changes matter when it comes to actual performance and efficiency? It’s perhaps best illustrated by looking at the Radeon VII, AMD’s last GCN GPU, and comparing it with the RX 5700 XT. Radeon VII has 60 CUs, 3840 GPU cores, 16GB of HBM2 memory with 1 TBps of bandwidth, a GPU clock speed of up to 1750 MHz, and a theoretical peak performance rating of 13.8 TFLOPS. The RX 5700 XT has 40 CUs, 2560 GPU cores, 8GB of GDDR6 memory with 448 GBps of bandwidth, and clocks at up to 1905 MHz with peak performance of 9.75 TFLOPS.

On paper, Radeon VII looks like it should come out with an easy victory. In practice, across a dozen games that we’ve tested, the RX 5700 XT is slightly faster at 1080p gaming and slightly slower at 1440p. Only at 4K is the Radeon VII able to manage a 7% lead, helped no doubt by its memory bandwidth. Overall, the Radeon VII only has a 1-2% performance advantage, but it uses 300W compared to the RX 5700 XT’s 225W.

In short, AMD was able to deliver roughly the same performance as the previous generation, with a third fewer cores, less than half the memory bandwidth and using 25% less power. That’s a very impressive showing, and while TSMC’s 7nm FinFET manufacturing process certainly warrants some of the credit (especially in regards to power), the performance uplift is mostly thanks to the RDNA architecture.

(Image credit: AMD)

That’s a lot of RDNA discussion, but it’s important because RDNA2 carries all of that forward, with several major new additions. First is support for ray tracing, Variable Rate Shading (VRS), and everything else that’s part of the DirectX 12 Ultimate spec. The other big addition is, literally, big: a 128MB Infinity Cache that help optimize memory bandwidth and latency. (Navi 22 has a 96MB Infinity Cache and Navi 23 gets by with a 32MB Infinity Cache.)

There are other tweaks to the architecture, but AMD made some big claims about Big Navi / RDNA2 / Navi 2x when it comes to performance per watt. Specifically, AMD said RDNA2 would offer 50% more performance per watt than RDNA 1, which is frankly a huge jump—the same large jump RDNA 1 saw relative to GCN. Even more importantly, AMD mostly succeeded. The RX 6600 XT ended up delivering slightly higher overall performance than the RX 5700 XT, while using 30% less power. Alternatively, the RX 6700 XT has the same 40 CUs as the RX 5700 XT, and it’s about 30% faster than the older card while using a similar amount of power.

The other major change with RDNA2 involves tuning the entire GPU pipeline to hit substantially higher clockspeeds. Previous generation AMD GPUs tended to run at substantially lower clocks than their Nvidia counterparts, and while RDNA started to close the gap, RDNA2 flips the tables and blows past Nvidia with the fastest clocks we’ve ever seen on a GPU. Game Clocks across the entire RX 6000 range are above 2.1GHz, and cards like the RX 6700 XT and RX 6600 XT can average speeds of around 2.5GHz while gaming. Clock speeds aren’t everything, but all else being equal, higher clocks are better, and the >20% boost in typical clocks accounts for a large chunk of the performance improvements we see with RDNA2 vs. RDNA GPUs.

Image 1 of 3

(Image credit: AMD)

Image 2 of 3

(Image credit: AMD)

Image 3 of 3

(Image credit: AMD)

RDNA2 / Big Navi / RX 6000 GPUs support ray tracing, via DirectX 12 Ultimate or VulkanRT. That brings AMD up to feature parity with Nvidia. AMD uses the same BVH approach to ray tracing calculations as Nvidia (it sort of has to since it’s part of the API). If you’re not familiar with the term BVH, it stands for Bounding Volume Hierarchy and is used to efficiently find ray and triangle intersections; you can read more about it in our discussion of Nvidia’s Turing architecture and its ray tracing algorithm.

AMD’s RDNA2 chips contain one Ray Accelerator per CU, which is similar to what Nvidia has done with it’s RT cores. Even though AMD sort of takes the same approach as Nvidia, the comparison between AMD and Nvidia isn’t clear cut. The BVH algorithm depends on both ray/box intersection calculations and ray/triangle intersection calculations. AMD’s RDNA2 architecture can do four ray/box intersections per CU per clock, or one ray/triangle intersection per CU per clock.

From our understanding, Nvidia’s Ampere architecture can do up to two ray/triangle intersections per RT core per clock, plus some additional extras, but it’s not clear what the ray/box rate is. In testing, Big Navi RT performance generally doesn’t come anywhere close to matching Ampere, though it can usually keep up with Turing RT performance. That’s likely due to Ampere’s RT cores doing more ray/box and ray/triangle intersections per clock.

AMD rendered image of the Navi 21 die. The Infinity Cache is the large green sections above and below the GPU cores.

(Image credit: AMD)

The Infinity Cache is perhaps the most interesting change. By including a whopping 128MB cache (L3, but with AMD branding), AMD should be able to keep basically all of the framebuffer cached, along with the z-buffer and the some recent textures. That will dramatically reduce memory bandwidth use and latency, and AMD claims the Infinity Cache allows the relatively tame GDDR6 16 Gbps memory to deliver an effective bandwidth that’s 2.17 times higher than the raw numbers would suggest.

The Infinity Cache also helps with ray tracing calculations. We’ve seen on Nvidia’s GPUs that memory bandwidth can impact RT performance on the lower tier cards like the RTX 2060, but it might also be memory latency that’s to blame. We can’t test AMD Big Navi performance in RT without the Infinity Cache, however, and all we know is that RT performance tends to lag behind Nvidia.

The Infinity Cache propagates down to the lower tier RDNA2 chips, but in different capacities. 128MB is very large, and based on AMD’s image of the die, it’s about 17 percent of the total die area on Navi 21. The CUs by comparison are only about 31 percent of the die area, with memory controllers, texture units, video controllers, video encoder/decoder hardware, and other elements taking up the rest of the chip. Navi 22 and Navi 23 have far lower CU counts, and less Infinity cache as well. Navi 22 has a 96MB L3 cache, while Navi 23 trims that all the way down to just 32MB. Interestingly, even with only one fourth the Infinity Cache, the RX 6600 XT still managed to outperform the RX 5700 XT at 1080p and 1440p — despite having 43% less raw bandwidth.

One big difference between AMD and Nvidia is that Nvidia also has Tensor cores in its Ampere and Turing architectures, which are used for deep learning and AI computations, as well as DLSS (Deep Learning Super Sampling). AMD doesn’t have a Tensor core equivalent, though its FidelityFX Super Resolution does offer somewhat analogous features and works on just about any GPU. Meanwhile, Intel’s future Arc Alchemist architecture will also have tensor processing elements, and XeSS will have a fall-back mode that runs using DP4a code on other GPUs.

AMD already has multiple Navi 2x products, though more variants may still be forthcoming. The RDNA2 architecture is also being used in some upcoming smartphone chips like the Samsung Exynos 2100, likely without any Infinity Cache and with far different capabilities in terms of performance. At present, AMD’s RX 6000 cards span the midrange to extreme performance categories, but even the lowest tier RX 6600 XT still carries a high-end price.

(Image credit: AMD)

RX 6000 / Big Navi / Navi 2x Specifications 

That takes care of all the core architectural changes. Now let’s put it all together and look at the currently announced RDNA2 / RX 6000 / Big Navi GPUs. AMD basically doubled down on Navi 10 when it comes to CUs and shaders, shoving twice the number of both into the largest Navi 21 GPU. At the same time, Navi 10 is relatively small at just 251mm square, and Big Navi is more than double that in its largest configuration. We’ll include the RX 5700 XT and Navi 10 in the following specs table as a point of reference.

AMD Radeon RX 6000 / Big Navi / Navi 2x Specifications
Graphics CardRX 6900 XTRX 6800 XTRX 6800RX 6700 XTRX 6600 XTRX 5700 XTArchitectureNavi 21Navi 21Navi 21Navi 22Navi 23Navi 10Process TechnologyTSMC N7TSMC N7TSMC N7TSMC N7TSMC N7TSMC N7Transistors (Billion)26.826.826.817.211.110.3Die size (mm^2)519519519336237251CUs807260403240GPU Cores512046083840256020482560Ray Accelerators8072604032N/ABase Clock (MHz)182518251700232119681605Boost Clock (MHz)225022502105258125891755VRAM Speed (Gbps)161616161614VRAM (GB)1616161288VRAM Bus Width256256256192128256ROPs12812896646464TMUs320288240160128160TFLOPS FP32 (Boost)2320.716.213.210.69Bandwidth (GBps)512512512384256448TDP (watts)300300250230230225Launch DateDec 2020Nov 2020Nov 2020Mar 2021Aug 2021Jul 2019Launch Price$999$649$579$479$379$399

The highest spec parts all use the same Navi 21 GPU, just with differing numbers of enabled functional units. Navi 21 has 80 CUs and 5120 GPU cores, and is more than double the size (519mm square) of the previous generation Navi 10 used in the RX 5700 XT. But a big chip means lower yields, so AMD has parts with 72 and 60 CUs as well.

The Radeon RX 6900 XT seems to be shipping in more limited quantities, but then all of the RDNA2 GPUs with the possible exceptions of the RX 6700 XT and RX 6600 XT have been hard to come by. Look at our GPU price index and you can see how many of each card has been sold (resold) on eBay during the past several months. The short summary is that Nvidia RTX 30-series GPUs are selling in far higher quantities.

See also  Điều Trị Sẹo Rỗ 5 Trong 1 - Trải Nghiệm Chỉ 1.800K - Bác Sĩ Thực Hiện - Hasaki.vn | hasaki

What’s interesting is how the die sizes and other features line up. Big Navi / RDNA2 adds support for ray tracing and other DX12 Ultimate features, which requires quite a few transistors. The very large Infinity Cache is also going to use up a huge chunk of die area, but it also helps overcome potential bandwidth limitations caused by the somewhat narrow 256-bit bus width on Navi 21. Ultimately, Navi 23 ends up with a slightly smaller die than Navi 10, but with similar performance and the additional new features.

Besides the already released cards, it’s interesting to note the gaps that still exist. RX 6700 XT remains the only card that uses Navi 22 (other than some mobile variants), and RX 6600 XT is the only card using Navi 23 so far. We will likely see additional card models in the future, like a non-XT RX 6600 and maybe even RX 6700, but AMD will probably wait until its supply of GPUs and other components improves before trying to launch more cards.

(Image credit: AMD)

One thing that has truly impressed with RDNA2 is the Infinity Cache. Not only does AMD give lots of VRAM for the various models (well, except maybe the RX 6600 XT, which feels a bit thin at 8GB for a $380 card), but the Infinity Cache truly does help with real-world performance. The RX 6700 XT as an example has less bandwidth than the RTX 3060 Ti and yet still keeps up with it in gaming performance, and the same goes for the RX 6800 XT vs. the RTX 3080.

At some point, we may also see an RX 6500 XT, though it may not be worth pursuing a lower tier GPU at this point. It would be interesting to see something like a 6GB card with a 96-bit interface and a 32MB Infinity Cache, but unless AMD can produce and sell such a card for under $200, we’re not particularly interested.

As far as a true budget Navi 2x card is concerned, no one is posting any real information on that yet. There might be a Navi 24 or something in the coming year, with only 20–24 CUs max. That would put it at the level of the Xbox Series S, at which point we’re not sure if it’s really worth including ray tracing support. We’ll have to see how things develop in the coming months, though, as 1080p with FSR might run fine on such a GPU.

Big Navi / Navi 2x Performance

Image 1 of 3

(Image credit: Tom’s Hardware)

Image 2 of 3

(Image credit: Tom’s Hardware)

Image 3 of 3

(Image credit: Tom’s Hardware)

With the official launches now complete, we have created the above charts using our own suite of 13 games run at three resolutions. All of the testing was done on a Core i9-9900K setup, with resizable BAR support enabled on the BIOS. The performance of RDNA2 and RX 6000 cards are good to great in rasterization games, but AMD generally comes up short of the competition in ray tracing workloads.

At the top, the RX 6900 XT goes up against the RTX 3090 and RTX 3080 Ti. AMD leads at 1080p, where the Infinity Cache benefits it the most, while the 3090 leads at 1440p and the 3080 Ti also comes out ahead of AMD’s best at 4K. The RX 6800 XT meanwhile takes down the RTX 3080, and the RX 6800 beats the RTX 3070 Ti. Further down the charts, the RX 6700 lands between the RTX 3060 Ti and RTX 3070, and the RX 6600 XT generally beats the RTX 3060 (except at 4K).

Of course, that’s only in traditional rasterization games. We’ve used a different suite of games with ray tracing enabled, and we’ve run benchmarks for each of the major GPU launches of the past year. The 10 games are the same as from the RX 6600 XT launch review (Bright Memory Infinite, Control, Cyberpunk 2077, Dirt 5, Fortnite, Godfall, Metro Exodus, Minecraft, Shadow of the Tomb Raider, and Watch Dogs Legion). Here’s the overall summary charts for 1440p and 1080p, running natively (without DLSS).

Image 1 of 2

(Image credit: Tom’s Hardware)

Image 2 of 2

(Image credit: Tom’s Hardware)

That… doesn’t look good for AMD. Granted, there are a couple of games (Godfall and Dirt 5) where AMD performance is far closer to what we saw in the earlier rasterization performance charts. However, those games only use one RT effect, ray traced shadows, and frankly the difference in image quality is pretty minor at best — just like in Shadow of the Tomb Raider. Also, those are two AMD promotional games, and Godfall at least has some questionable design decisions (it really runs poorly with less than 12GB VRAM, for example).

As more RT effects get used, Nvidia’s Ampere GPUs tend to widen their performance advantage. In our RT test suite, the RX 6900 XT is the fastest RDNA2 card and it ends up just slightly ahead of the RTX 3070 Ti, with the RX 6800 XT falling a hair behind the RTX 3070 Ti. The RX 6800 now lands between the RTX 3070 and RTX 3060 Ti, and the RX 6700 XT trails the RTX 3060 Ti and comes in about 10% ahead of the RTX 3060. Meanwhile, the RX 6600 XT clearly has problems, either from a lack of VRAM, the smaller Infinity Cache size, or maybe drivers — or likely from all of the above. We’ll have to revisit that in the future, like maybe once Windows 11 gets released.

Big Navi and RX 6000 Closing Thoughts

Image 1 of 18

(Image credit: AMD)

Image 2 of 18

(Image credit: AMD)

Image 3 of 18

(Image credit: AMD)

Image 4 of 18

(Image credit: AMD)

Image 5 of 18

(Image credit: AMD)

Image 6 of 18

(Image credit: AMD)

Image 7 of 18

(Image credit: AMD)

Image 8 of 18

(Image credit: AMD)

Image 9 of 18

(Image credit: AMD)

Image 10 of 18

(Image credit: AMD)

Image 11 of 18

(Image credit: AMD)

Image 12 of 18

(Image credit: AMD)

Image 13 of 18

(Image credit: AMD)

Image 14 of 18

(Image credit: AMD)

Image 15 of 18

(Image credit: AMD)

Image 16 of 18

(Image credit: AMD)

Image 17 of 18

(Image credit: AMD)

Image 18 of 18

(Image credit: AMD)

AMD provided a deeper dive into the RDNA2 architecture at Hot Chips 2021. We’ve used several of the slides in our latest updates, but the full suite is in the above gallery for reference.

AMD has a lot riding on Big Navi, RDNA2, and the Radeon RX 6000 series. After playing second fiddle to Nvidia for the past several generations, AMD is taking its shot at the top. AMD has to worry about more than just PC graphics cards, though. RDNA2 is the GPU architecture that powers the next generation of consoles, which tend to have much longer shelf lives than PC graphics cards. Look at the PS4 and Xbox One: both launched in late 2013 and are still in use today.

If you were hoping for a clear win from AMD, across all games and rendering APIs, that didn’t happen. Big Navi performs great in many cases, but with ray tracing it looks decidedly mediocre. Higher performance in games that don’t use ray tracing might be more important today, but a year or two down to road, that could change. Then again, the consoles have AMD GPUs and are more likely to see AMD-specific optimizations, so AMD isn’t out of the running yet.

Just as important as performance and price, though, we need actual cards for sale. There’s clearly demand for new levels of performance, and every Ampere GPU and Big Navi GPU so far has sold out as quickly as the products are available for purchase. There’s only so much silicon to go around, sadly. Samsung apparently can’t keep up with demand for Ampere GPUs, and TSMC has a lot more going on — it can only produce so many N7 wafers per month! Based on what we’ve seen in our GPU price index and the latest Steam Hardware Survey, Nvidia has sold probably ten times as many Ampere GPUs as AMD has sold RDNA2 cards.

The bottom line is that if you’re looking for a new high-end graphics card, Big Navi is a good competitor. But if you want something that can run every game at maxed out settings, even with ray tracing, at 4K and 60 fps? Not even the RTX 3090 can manage that, which means even while we’re plagued with shortages on all the current GPUs, we’re already looking toward the future next-gen GPUs.

Save us, Lovelace and RDNA3. You’re our only hope! And thankfully, Ethereum mining will no longer be a thing come next year (though a different coin might take its place).


CS:GO – NaVi vs. Team Liquid [Dust2] Map 1 – Semi-Final – ESL One Cologne 2019


We are celebrating 5 years in the Cathedral of CounterStrike. Join us on July 5 7 at ESL One Cologne 2019: https://esl.gg/Cologne2019
Subscribe to ESLCS and never miss out on your favourite teams:
https://www.youtube.com/channel/UCPq2…
Follow us:
https://twitter.com/ESLCS
https://www.facebook.com/ESLCS

นอกจากการดูบทความนี้แล้ว คุณยังสามารถดูข้อมูลที่เป็นประโยชน์อื่นๆ อีกมากมายที่เราให้ไว้ที่นี่: ดูเพิ่มเติม

CS:GO - NaVi vs. Team Liquid [Dust2] Map 1 - Semi-Final - ESL One Cologne 2019

NAVI s1mple – ЛУЧШИЙ ИГРОК @BLAST Premier Fall Final 2021 (MVP Movie)


Предлагаем к просмотру фрагмуви, посвященный выступлению Александра Костылева на BLAST Premier Fall Final 2021. Здесь — лучшие киллы в его исполнении, увидев которые у вас не останется сомнений, почему именно Саша s1mple стал MVP турнира!
We present to you a frag movie dedicated to Oleksandr Kostyliev’s MVP performance at the BLAST Premier Fall Final 2021. This video features Sasha s1mple’s best frags and after watching it, you will have no doubt as to why he was awarded the tournament’s MVP.
RAID: Shadow Legends ввели в свою игру чемпиона, прототипом которого стал Александр S1mple Костылев. Теперь можно получить в свою коллекцию Сашу в образе эльфа, стреляющего из лука и выиграть призы, скачав RAID. Больше информации тут https://ad.navi.gg/s1mpleinraid
RAID: Shadow Legends introduced a new champion and Alexander S1mple Kostylev became a prototype for it. Download RAID: SL to add Sasha to your collection and win prizes. More information here https://ad.navi.gg/s1mpleinraid
NAVI SHOP https://navi.gg/shop_ytd
Follow us:
https://bio.link/navi
NAVI CS:GO roster:
Oleksandr \”S1MPLE\” Kostyliev
Denis \”ELECTRONIC\” Sharipov
Kirill \”Boombl4\” Mikhailov
Ilya \”PERFECTO\” Zalutskiy
Valeriy \”B1T\” Vakhovskyi
Production Music courtesy of Epidemic Sound
www.epidemicsound.com
NAVI s1mple ЛУЧШИЙ ИГРОК BLAST Premier Fall Final 2021 (MVP Movie)
NaviMovie NaviCSGO CSGO

NAVI s1mple - ЛУЧШИЙ ИГРОК @BLAST Premier  Fall Final 2021 (MVP Movie)

NAVI B1ad3 – On the Edge. Острые Новости: Победа на Мажоре, Решафлы, Бласт


Решафлы на просцене и предстоящий BLAST — самые актуальные темы, которые мы выбрали для обсуждения вместе с B1ad3 в этом выпуске On the Edge.
In today’s episode of ‘On The Edge’ with B1ad3, we talk about the roster changes happening in the pro scene and the upcoming BLAST.
Philips OneBlade бреет щетину, не повреждая кожу. Идеальное решение для бритья без порезов и раздражения, а также подравнивания и стайлинга щетины любой длины. Создай свой стиль с официальным спонсором NAVI — Philips OneBlade! http://navi.gg/1blade
Philips OneBlade shaves your stubble without damaging your skin. Perfect solution for irritationfree shaving, trimming and styling any length of stubble. Create your own style with the official sponsor of NAVI — Philips OneBlade! http://navi.gg/1blade
0:00 Вступление
0:33 Что происходило после мажора?
1:50 Какой матч оказался самым интересным?
2:55 Решафлы
9:40 Подготовка к Бласту
NAVI SHOP https://navi.gg/shop_ytd
Follow us:
https://bio.link/navi
NAVI CS:GO roster:
Oleksandr \”S1MPLE\” Kostyliev
Denis \”ELECTRONIC\” Sharipov
Kirill \”Boombl4\” Mikhailov
Ilya \”PERFECTO\” Zalutskiy
Valeriy \”B1T\” Vakhovskyi
Production Music courtesy of Epidemic Sound
www.epidemicsound.com
NAVI B1ad3 On the Edge. Острые Новости: Победа на Мажоре, Решафлы, Бласт
NaviNEWS NaviCSGO CSGO

NAVI B1ad3 - On the Edge. Острые Новости: Победа на Мажоре, Решафлы, Бласт

Начинаем @BLAST Premier Fall Final как Чемпионы | НАВИ КСГО ВЛОГ


Врываемся на BLAST Premier! В свежем влоге обозреваем крутой медиадень и не менее крутой стартовый матч против BIG.
BLAST Premier is underway and our first vlog covers the media day and opener against BIG.
Philips OneBlade бреет щетину, не повреждая кожу. Идеальное решение для бритья без порезов и раздражения, а также подравнивания и стайлинга щетины любой длины. Создай свой стиль с официальным спонсором NAVI — Philips OneBlade! http://navi.gg/1blade
Philips OneBlade shaves your stubble without damaging your skin. Perfect solution for irritationfree shaving, trimming and styling any length of stubble. Create your own style with the official sponsor of NAVI — Philips OneBlade! http://navi.gg/1blade
NAVI SHOP https://navi.gg/shop_ytd
Follow us:
https://bio.link/navi
NAVI CS:GO roster:
Oleksandr \”S1MPLE\” Kostyliev
Denis \”ELECTRONIC\” Sharipov
Kirill \”Boombl4\” Mikhailov
Ilya \”PERFECTO\” Zalutskiy
Valeriy \”B1T\” Vakhovskyi
Production Music courtesy of Epidemic Sound
www.epidemicsound.com
Начинаем @BLAST Premier Fall Final как Чемпионы | НАВИ КСГО ВЛОГ
NaviVLOG NaviCSGO CSGO

Начинаем @BLAST Premier  Fall Final как Чемпионы | НАВИ КСГО ВЛОГ

Легчайшая против Heroic на @BLAST Premier Fall Final | НАВИ КСГО ВЛОГ


И вновь влог с BLAST Premier! Сегодня показываем матч против Heroic: каким был настрой ребят и как прошла игра.
Here is another BLAST Premier vlog! Today’s video gives you a glimpse into the mindset of the players and how the game against Heroic went down.
Наш секрет победы в моментальной реакции, идеальной коммуникации и точности в каждом движении. Наш секрет победы в Logitech G!
​http://navi.gg/logitechg
The secret of our victory in the instant reaction, perfect communication, and precise movements. The secret of our victory in Logitech G!
​http://navi.gg/logitechg
NAVI SHOP https://navi.gg/shop_ytd
Follow us:
https://bio.link/navi
NAVI CS:GO roster:
Oleksandr \”S1MPLE\” Kostyliev
Denis \”ELECTRONIC\” Sharipov
Kirill \”Boombl4\” Mikhailov
Ilya \”PERFECTO\” Zalutskiy
Valeriy \”B1T\” Vakhovskyi
Production Music courtesy of Epidemic Sound
www.epidemicsound.com
Легчайшая против Heroic на @BLAST Premier Fall Final | НАВИ КСГО ВЛОГ
NaviVLOG NaviCSGO CSGO

Легчайшая против Heroic на @BLAST Premier  Fall Final | НАВИ КСГО ВЛОГ

นอกจากการดูบทความนี้แล้ว คุณยังสามารถดูข้อมูลที่เป็นประโยชน์อื่นๆ อีกมากมายที่เราให้ไว้ที่นี่: ดูบทความเพิ่มเติมในหมวดหมู่Wiki

ขอบคุณมากสำหรับการดูหัวข้อโพสต์ navi team

Leave a Comment