AMD Radeon RX 460 vs MSI Radeon RX 470 Gaming 4GB: What is the difference?
40points
AMD Radeon RX 460
46points
MSI Radeon RX 470 Gaming 4GB
vs
54 facts in comparison
AMD Radeon RX 460
MSI Radeon RX 470 Gaming 4GB
Why is AMD Radeon RX 460 better than MSI Radeon RX 470 Gaming 4GB?
- 164MHz faster GPU clock speed?
1090MHzvs926MHz - 45W lower TDP?
75Wvs120W - 100MHz faster memory clock speed?
1750MHzvs1650MHz - 400MHz higher effective memory clock speed?
7000MHzvs6600MHz - 106mm narrower?
170mmvs276mm - 29mm shorter?
111mmvs140mm
Why is MSI Radeon RX 470 Gaming 4GB better than AMD Radeon RX 460?
- 2.84 TFLOPS higher floating-point performance?
4.99 TFLOPSvs2.15 TFLOPS - 19.
8 GPixel/s higher pixel rate?
39 GPixel/svs19.2 GPixel/s - 2x more VRAM?
4GBvs2GB - 98.3 GTexels/s higher texture rate?
155.9 GTexels/svs57.6 GTexels/s - 99.2GB/s more memory bandwidth?
211.2GB/svs112GB/s - 128bit wider memory bus width?
256bitvs128bit - 1152 more shading units?
2048vs896 - 2700million more transistors?
5700 millionvs3000 million
Which are the most popular comparisons?
AMD Radeon RX 460
vs
Nvidia GeForce GTX 750 Ti
MSI Radeon RX 470 Gaming 4GB
vs
Asus Radeon RX 550 4GB
AMD Radeon RX 460
vs
Nvidia GeForce GTX 1050
MSI Radeon RX 470 Gaming 4GB
vs
Nvidia GeForce GT 1030 DDR4
AMD Radeon RX 460
vs
AMD Radeon RX 550
MSI Radeon RX 470 Gaming 4GB
vs
Nvidia GeForce RTX 3050 Ti Laptop
AMD Radeon RX 460
vs
AMD Radeon RX 560
MSI Radeon RX 470 Gaming 4GB
vs
AMD Radeon RX 5700 XT
AMD Radeon RX 460
vs
MSI GeForce GTX 1050 Ti
MSI Radeon RX 470 Gaming 4GB
vs
AMD Radeon RX 6400
AMD Radeon RX 460
vs
Nvidia GeForce GTX 960
MSI Radeon RX 470 Gaming 4GB
vs
Sapphire Radeon RX 470
AMD Radeon RX 460
vs
AMD Radeon RX Vega 8
MSI Radeon RX 470 Gaming 4GB
vs
AMD Radeon R5
AMD Radeon RX 460
vs
Nvidia GeForce GTX 1060
MSI Radeon RX 470 Gaming 4GB
vs
AMD Radeon R9 290X
AMD Radeon RX 460
vs
AMD Radeon R9 380
MSI Radeon RX 470 Gaming 4GB
vs
AMD Radeon HD 7850
AMD Radeon RX 460
vs
AMD Radeon R7 260X
Price comparison
User reviews
Overall Rating
AMD Radeon RX 460
2 User reviews
AMD Radeon RX 460
10.
0/10
2 User reviews
MSI Radeon RX 470 Gaming 4GB
0 User reviews
MSI Radeon RX 470 Gaming 4GB
0.0/10
0 User reviews
Features
Value for money
10.0/10
2 votes
No reviews yet
Gaming
8.5/10
2 votes
No reviews yet
Performance
9.0/10
2 votes
No reviews yet
Fan noise
8.0/10
2 votes
No reviews yet
Reliability
9.0/10
2 votes
No reviews yet
Performance
1.GPU clock speed
1090MHz
926MHz
The graphics processing unit (GPU) has a higher clock speed.
2.GPU turbo
1200MHz
1218MHz
When the GPU is running below its limitations, it can boost to a higher clock speed in order to give increased performance.
3.pixel rate
19.
2 GPixel/s
39 GPixel/s
The number of pixels that can be rendered to the screen every second.
4.floating-point performance
2.15 TFLOPS
4.99 TFLOPS
Floating-point performance is a measurement of the raw processing power of the GPU.
5.texture rate
57.6 GTexels/s
155.9 GTexels/s
The number of textured pixels that can be rendered to the screen every second.
6.GPU memory speed
1750MHz
1650MHz
The memory clock speed is one aspect that determines the memory bandwidth.
7.shading units
Shading units (or stream processors) are small processors within the graphics card that are responsible for processing different aspects of the image.
8.texture mapping units (TMUs)
TMUs take textures and map them to the geometry of a 3D scene. More TMUs will typically mean that texture information is processed faster.
9.render output units (ROPs)
The ROPs are responsible for some of the final steps of the rendering process, writing the final pixel data to memory and carrying out other tasks such as anti-aliasing to improve the look of graphics.
Memory
1.effective memory speed
7000MHz
6600MHz
The effective memory clock speed is calculated from the size and data rate of the memory. Higher clock speeds can give increased performance in games and other apps.
2.maximum memory bandwidth
112GB/s
211.2GB/s
This is the maximum rate that data can be read from or stored into memory.
3.VRAM
VRAM (video RAM) is the dedicated memory of a graphics card. More VRAM generally allows you to run games at higher settings, especially for things like texture resolution.
4.memory bus width
128bit
256bit
A wider bus width means that it can carry more data per cycle.
It is an important factor of memory performance, and therefore the general performance of the graphics card.
5.version of GDDR memory
Newer versions of GDDR memory offer improvements such as higher transfer rates that give increased performance.
6.Supports ECC memory
✖AMD Radeon RX 460
✖MSI Radeon RX 470 Gaming 4GB
Error-correcting code memory can detect and correct data corruption. It is used when is it essential to avoid corruption, such as scientific computing or when running a server.
Features
1.DirectX version
DirectX is used in games, with newer versions supporting better graphics.
2.OpenGL version
OpenGL is used in games, with newer versions supporting better graphics.
3.OpenCL version
Some apps use OpenCL to apply the power of the graphics processing unit (GPU) for non-graphical computing.
Newer versions introduce more functionality and better performance.
4.Supports multi-display technology
✔AMD Radeon RX 460
✔MSI Radeon RX 470 Gaming 4GB
The graphics card supports multi-display technology. This allows you to configure multiple monitors in order to create a more immersive gaming experience, such as having a wider field of view.
5.load GPU temperature
Unknown. Help us by suggesting a value. (AMD Radeon RX 460)
Unknown. Help us by suggesting a value. (MSI Radeon RX 470 Gaming 4GB)
A lower load temperature means that the card produces less heat and its cooling system performs better.
6.supports ray tracing
✖AMD Radeon RX 460
✖MSI Radeon RX 470 Gaming 4GB
Ray tracing is an advanced light rendering technique that provides more realistic lighting, shadows, and reflections in games.
7.
Supports 3D
✔AMD Radeon RX 460
✔MSI Radeon RX 470 Gaming 4GB
Allows you to view in 3D (if you have a 3D display and glasses).
8.supports DLSS
✖AMD Radeon RX 460
✖MSI Radeon RX 470 Gaming 4GB
DLSS (Deep Learning Super Sampling) is an upscaling technology powered by AI. It allows the graphics card to render games at a lower resolution and upscale them to a higher resolution with near-native visual quality and increased performance. DLSS is only available on select games.
9.PassMark (G3D) result
Unknown. Help us by suggesting a value. (AMD Radeon RX 460)
Unknown. Help us by suggesting a value. (MSI Radeon RX 470 Gaming 4GB)
This benchmark measures the graphics performance of a video card. Source: PassMark.
Ports
1.has an HDMI output
✔AMD Radeon RX 460
✔MSI Radeon RX 470 Gaming 4GB
Devices with a HDMI or mini HDMI port can transfer high definition video and audio to a display.
2.HDMI ports
More HDMI ports mean that you can simultaneously connect numerous devices, such as video game consoles and set-top boxes.
3.HDMI version
HDMI 2.0
HDMI 2.0
Newer versions of HDMI support higher bandwidth, which allows for higher resolutions and frame rates.
4.DisplayPort outputs
Allows you to connect to a display using DisplayPort.
5.DVI outputs
Allows you to connect to a display using DVI.
6.mini DisplayPort outputs
Allows you to connect to a display using mini-DisplayPort.
Price comparison
Cancel
Which are the best graphics cards?
AMD RX 480 vs RX 470 vs RX 460
All three AMD cards are affordable graphics cards which bring high-end gaming to the masses. The AMD RX 460, RX 470 and RX 480 are three cards that aim to bridge the gap between affordable and high-performance graphics cards.
The three cards are all based on the Polaris architecture, but will appeal to three different types of users. Read on to find out which AMD Polaris card is best for you.
Also see:
AMD RX 480, 470, 460 UK release date, price, features and specification.
Updated 8 August with RX 460 release. The new cards are now on sale from retailers including
Overclockers UK, and prices range from £99 to £135 depending on whether the card has 2GB or 4GB of RAM.
AMD RX 480 vs RX 470 vs RX 460 UK price and availability: How much do the AMD RX 480, 470 and 460 cost and where to buy?
The AMD RX 480 and RX 470 are currently available from a variety of UK retailers, such as
Overclockers UK,
eBuyer,
Scan and
Maplin.
The RX 460 launched on 8 August.
The RX 480 is available in both 4GB and 8GB VRAM versions. The RX 470 with 4GB VRAM, and the RX 460 comes in 2GB and 4GB VRAM models.
Below is a list of the UK and US prices (prices vary according to manufacturer and features):
AMD RX 480 UK price
- 4GB VRAM: $199 / £180 inc VAT
- 8GB VRAM: $239 / £220 inc VAT
AMD RX 470 UK price
- 4GB VRAM: $179 / £170 inc VAT
AMD RX 460 UK price
- 2GB VRAM: $99 / £99 inc VAT
- 4GB VRAM: $129 / £135 inc VAT
Looking at the above pricing structure, we see the AMD RX 460 really aimed at those who want a budget system. The RX 470 and RX 480 are aimed at gamers who want a flawless full-HD experience.
Also read:
Nvidia GeForce GTX 1080 & 1070 vs AMD Radeon RX 480.
AMD RX 480 vs RX 470 vs RX 460: Full Specifications
All three Polaris cards will run on the new and optimised 14nm FinFET chips. This makes all three cards a lot more efficient than their predecessors, but also allows them to perform better. In order to compare the specs of the three AMD Polaris cards we’ve listed the specs of each below:
AMD RX 480 specs
- Stream Processors: 2304
- AMD CUs: 36
- Core clock: 1120MHz
- Boost clock: 1266MHz
- VRAM: 4 & 8GB GDDR5
- TFLOP: 5.
8 - Memory clock: 7Gbps (4GB) & 8Gbps (8GB)
- Memory bus width: 256-bit
- Memory bandwidth (GB/s): 224 (4GB) & 256 (8GB)
- TDP: 150W
- Transistors: 5.7b
- Manufacturing process: 14nm FinFET
- Power: 1x 6-pin
- Standard card length: 243mm
AMD RX 470 specs
- Stream Processors: 2048
- AMD CUs: 32
- Core clock: 926MHz
- Boost clock: 1206MHz
- VRAM: 4GB GDDR5
- TFLOP: 4.9
- Memory clock: 6.6Gbps
- Memory bus width: 256-bit
- Memory bandwidth (GB/s) 211
- TDP: 120W
- Transistors: 5.7b
- Manufacturing process: 14nm FinFET
- Power: 1x 6-pin
AMD RX 460 specs
- Stream Processors: 896
- AMD CUs: 14
- Core clock: 1090MHz
- Boost clock: 1200MHz
- VRAM: 2 & 4GB GDDR5
- TFLOP: 2.2
- Memory clock: 7Gbps
- Memory bus width: 128-bit
- Memory bandwidth (GB/s): 112
- TDP: 75W
- Transistors: 3.
5b (unknown) - Manufacturing process: 14nm FinFET
- Power: None
Looking at the specs, the RX 480 is naturally the best card out of the bunch. It boasts an impressive stream processor count and has a lot of VRAM to cope with intensive games. It’s safe to say that the RX 480 is a VR-capable graphics card, with the card’s memory modules helping it cope with VR games.
AMD says the RX 470 and RX 460 are VR-capable. We’ll have to wait untill we can run our benchmarks until we can verify this, but both will be fantastic cards for full-HD gaming. The RX 470 is priced closely to the RX 480, making it a card that doesn’t quite make sense for gamers wanting a new graphics card: just stretch your budget and get an RX 480.
To represent the specifications, we’ve put the new RX cards against their predecessors:
Which resolutions will the AMD Polaris cards are able to do?
The RX 480 will be able to drive a 4K (3840×2160) resolution at 60fps. It will also be able to play anything under that, such as WQHD (2560×1440) and full-HD (1920×1080) at 144fps with ease.
The RX 470 will also be able to deliver the same resolutions as the RX 480, however will struggle to keep up a solid FPS performance at higher resolutions such as at 4K and WQHD. However, the RX 470 is aimed at providing a flawless full-HD gaming experience, meaning 144fps should be easily attainable.
The RX 460 on the other hand is the slowest card of the bunch and has the lowest amount of VRAM. It won’t be able to drive 30fps at 4K, and may not be able to fully cope at 60fps at WQHD. At full-HD, the card might also struggle to perform on AAA game titles at 144fps. This comes from the RX 460 being aimed at “eSports” gamers and those who don’t necessarily need a beautiful gaming experience, but want something that’s low-budget and works at lower resolutions.
This comes from a lot of eSports gamers not really needing the horsepower found in higher-end graphics cards, but want a card that can deliver consistent performance. CS:GO professionals often game on a 4:3 ratio and play at a 1024×768 resolution in order to get the most FPS.
In this respect, the RX 460 will be suited for them and other casual gamers who want to game at lower resolutions.
Power
In the past AMD’s problem has been power input and heat output in their graphics cards. With the new 14nm FinFET architecture, AMD have a much lower power draw requirement, making the cards a lot more efficient and cheaper to run.
Despite the RX 480 receiving a lot of flak through its increased 95W PCIe power draw from the motherboard’s slot, the card is still an efficient card to run, with a TDP of around 150W.
The RX 470 has a 120W TDP, where like the RX 480 will run on a single 6-pin PCIE connection. It should be mentioned that third-party manufacturers such as MSI and Gigabyte among others might also choose to use a 8-pin configuration in order to drive more power for overclocking needs.
The RX 460 is the one that stands out from the crowd, as it requires only 75W, which means it can run on the motherboard’s PCIe slot and doesn’t require additional power from the PSU.
On that note, the RX 460 runs on Polaris 11, rather than the Polaris 10 which the RX 470 and RX 480 run on.
Other features
The RX 460, 470 and 480 include support for HDR (high-dynamic-range) rendering, which allows for better lighting scenarios in games. This makes gaming a little more pleasant and realistic.
All three cards support AMD FreeSync, HDMI 2.0b, DisplayPort 1.3/1.4, Direct X12 and Vulkan, and have H.265, HEVC encoding and decoding capabilities – which keeps up with current display trends.
Interestingly enough, the DVI input has been dropped by AMD, however third-party manufacturers have brought it back in a few of their RX 480 variants. The RX 470 has shared the same fate, but the RX 460 still has a DVI slot included on AMD’s reference board.
Read next:
Nvidia GeForce GTX 1080 vs GTX 1070.
RX 460 vs RX 470 ⚙️
0x1011.191MH/s100W0.112MH/W
Argon2d-ninja0KH/s113W0KH/W
Argon2d4096—KH/s—W—KH/W
Astralhash12.
783MH/s123W0.104MH/W
Autolykos252.01MH/s71W0.733MH/W
BCD9.471MH/s75W0.126MH/W
BMW512356.13MH/s82W4.343MH/W
BeamHashII13.694H/s60W0.228H/W
BeamHashIII14.025H/s73W0.192H/W
Blake (2b)0.97GH/s84W0.012GH/W
Blake (2s)2.355GH/s89W0.026GH/W
Blake (2s-Kadena)0.407GH/s94W0.004GH/W
C1110.281MH/s87W0.118MH/W
CNReverseWaltz1025H/s59W17.
373H/W
Chukwa50.642KH/s104W0.487KH/W
Chukwa218.333KH/s64W0.286KH/W
Circcash925.724KH/s74W12.51KH/W
CryptoNight0.361KH/s44W0.008KH/W
CryptoNightAlloy345.375H/s45W7.675H/W
CryptoNightArto679.428H/s45W15.098H/W
CryptoNightB2N1056.375H/s—W—H/W
CryptoNightConceal1421.75H/s46W30.908H/W
CryptoNightFast1394.864H/s67W20.819H/W
CryptoNightFastV21389.
5H/s49W28.357H/W
CryptoNightGPU560.16H/s79W7.091H/W
CryptoNightHaven821.725H/s74W11.104H/W
CryptoNightHeavy980.607H/s68W14.421H/W
CryptoNightHeavyX364.367H/s74W4.924H/W
CryptoNightItalo907.6H/s—W—H/W
CryptoNightLiteV71.249KH/s58W0.022KH/W
CryptoNightR720.25H/s51W14.123H/W
CryptoNightSaber815.203H/s63W12.94H/W
CryptoNightStelliteV4666.205H/s61W10.
921H/W
CryptoNightStelliteV51549.354H/s—W—H/W
CryptoNightTurtle5.828KH/s66W0.088KH/W
CryptoNightUPX222.9KH/s48W0.477KH/W
CryptoNightV70.69KH/s59W0.012KH/W
CryptoNightV8691.275H/s55W12.569H/W
CryptoNightWOW687.778H/s53W12.977H/W
CryptoNightZLS841.355H/s84W10.016H/W
Cuckaroo29S2.08H/s106W0.02H/W
Cuckaroo29b2.21H/s58W0.038H/W
CuckooBFC46.
439H/s85W0.546H/W
CuckooCycle1.838H/s72W0.026H/W
Dedal7.685MH/s69W0.111MH/W
Eaglesong0.305GH/s91W0.003GH/W
Equihash0.254KH/s54W0.005KH/W
Equihash(125,4)13.898H/s110W0.126H/W
Equihash(144,5)22.98H/s86W0.267H/W
Equihash(150,5)9.133H/s62W0.147H/W
Equihash(192,7)13.945H/s64W0.218H/W
Equihash(210,9)82.334H/s56W1.
47H/W
Equihash(96,5)11.06KH/s75W0.147KH/W
Equihash+Scrypt8.535KH/s71W0.12KH/W
Etchash31.568MH/s70W0.451MH/W
Ethash31.568MH/s70W0.451MH/W
Globalhash32.395MH/s86W0.377MH/W
HMQ17254.909MH/s71W0.069MH/W
Handshake0.113GH/s101W0.001GH/W
HeavyHash135.319MH/s73W1.854MH/W
Hex7.644MH/s116W0.066MH/W
HoneyComb21.083MH/s90W0.
234MH/W
Jeonghash6.322MH/s83W0.076MH/W
KAWPOW8.671MH/s110W0.079MH/W
KangarooTwelve0.787GH/s118W0.007GH/W
Lyra2REv227.314MH/s118W0.231MH/W
Lyra2REv331.185MH/s117W0.267MH/W
Lyra2vc0ban25.635MH/s117W0.219MH/W
Lyra2z2.5MH/s117W0.021MH/W
NeoScrypt0.787MH/s118W0.007MH/W
Octopus5.044MH/s100W0.05MH/W
PHI161213.408MH/s90W0.
149MH/W
PHI23.93MH/s109W0.036MH/W
Padihash5.859MH/s118W0.05MH/W
Pawelhash5.558MH/s62W0.09MH/W
Phi512.058H/s95W0.127H/W
ProgPow7.598MH/s101W0.075MH/W
ProgPowSERO8.393MH/s72W0.117MH/W
ProgPowZ8.405MH/s62W0.136MH/W
RandomKEVA430.963H/s—W—H/W
RandomSFX470.376H/s71W6.625H/W
RandomX393.7H/s56W7.
03H/W
SHA-256csm632.357MH/s86W7.353MH/W
SHA3d158.396TH/s90W1.76TH/W
Skein2258.049MH/s91W2.836MH/W
Skunkhash20.939MH/s118W0.177MH/W
SonoA1.2MH/s118W0.01MH/W
Tellor0.16GH/s78W0.002GH/W
TimeTravel1017.146MH/s74W0.232MH/W
Tribus37.556MH/s77W0.488MH/W
Ubqhash20.825MH/s95W0.219MH/W
Verthash0.411MH/s45W0.
009MH/W
VerusHash3.902MH/s77W0.051MH/W
X11k1.578MH/s91W0.017MH/W
X16R7.99MH/s109W0.073MH/W
X16RT8.18MH/s107W0.076MH/W
X16RTVEIL8.352MH/s74W0.113MH/W
X16Rv26.806MH/s79W0.086MH/W
X16S7.546MH/s92W0.082MH/W
X177.616MH/s71W0.107MH/W
X17R6.486MH/s86W0.075MH/W
X186.233MH/s70W0.089MH/W
X21S5.
754MH/s72W0.08MH/W
X22i4.451MH/s72W0.062MH/W
X25X0.833MH/s68W0.012MH/W
Xevan2.479MH/s90W0.028MH/W
Zhash22.7H/s59W0.385H/W
cuckARoo291.51H/s69W0.022H/W
cuckARood292.17H/s70W0.031H/W
cuckARoom292.593H/s82W0.032H/W
cuckAToo310.425H/s102W0.004H/W
cuckAToo320.145H/s65W0.002H/W
vProgPow4.
088MH/s76W0.054MH/W
AMD Radeon RX 460 (Desktop) vs AMD Radeon RX 470 (Desktop)
Die folgenden Benchmarks basieren auf unseren Spieletests mit Testnotebooks. Die Performance dieser Grafikkarte bei den gelisteten Spielen ist abhängig von der verwendeten CPU, Speicherausstattung, Treiber und auch Betriebssystem. Dadurch müssen die untenstehenden Werte nicht repräsentativ sein. Detaillierte Informationen über das verwendete System sehen Sie nach einem Klick auf den fps-Wert.
log 30. 13:21:05
#0 checking url part for id 7375 +0s … 0s
#1 checking url part for id 7374 +0s … 0s
#2 not redirecting to Ajax server +0s … 0s
#3 did not recreate cache, as it is less than 5 days old! Created at Tue, 27 Sep 2022 17:27:11 +0200 +0s … 0s
#4 linkCache_getLink using $NBC_LINKCACHE +0.086s … 0.086s
#5 linkCache_getLink using $NBC_LINKCACHE +0.
003s … 0.089s
#6 linkCache_getLink using $NBC_LINKCACHE +0s … 0.089s
#7 linkCache_getLink using $NBC_LINKCACHE +0s … 0.089s
#8 composed specs +0s … 0.089s
#9 did output specs +0s … 0.089s
#10 start showIntegratedCPUs +0s … 0.089s
#11 getting avg benchmarks for device 7375 +0.03s … 0.12s
#12 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.12s
#13 got single benchmarks 7375 +0.008s … 0.129s
#14 getting avg benchmarks for device 7374 +0s … 0.129s
#15 linkCache_getLink using $NBC_LINKCACHE +0s … 0.13s
#16 got single benchmarks 7374 +0.007s … 0.136s
#17 got avg benchmarks for devices +0s … 0.136s
#18 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.137s
#19 linkCache_getLink using $NBC_LINKCACHE +0s … 0.138s
#20 linkCache_getLink using $NBC_LINKCACHE +0s … 0.138s
#21 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.138s
#22 linkCache_getLink using $NBC_LINKCACHE +0s … 0.139s
#23 linkCache_getLink no uid found +0.001s … 0.139s
#24 linkCache_getLink using $NBC_LINKCACHE +0s … 0.139s
#25 linkCache_getLink using $NBC_LINKCACHE +0s … 0.14s
#26 linkCache_getLink using $NBC_LINKCACHE +0s … 0.14s
#27 linkCache_getLink no uid found +0s … 0.14s
#28 linkCache_getLink using $NBC_LINKCACHE +0s … 0.14s
#29 linkCache_getLink no uid found +0s … 0.141s
#30 linkCache_getLink using $NBC_LINKCACHE +0s … 0.141s
#31 linkCache_getLink using $NBC_LINKCACHE +0s … 0.141s
#32 linkCache_getLink using $NBC_LINKCACHE +0s … 0.141s
#33 linkCache_getLink no uid found +0s … 0.141s
#34 linkCache_getLink using $NBC_LINKCACHE +0s … 0.142s
#35 linkCache_getLink no uid found +0s … 0.142s
#36 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.142s
#37 linkCache_getLink using $NBC_LINKCACHE +0s … 0.143s
#38 linkCache_getLink no uid found +0s … 0.143s
#39 linkCache_getLink using $NBC_LINKCACHE +0s … 0.143s
#40 linkCache_getLink using $NBC_LINKCACHE +0s … 0.143s
#41 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.144s
#42 linkCache_getLink no uid found +0s … 0.144s
#43 linkCache_getLink using $NBC_LINKCACHE +0s … 0.145s
#44 linkCache_getLink using $NBC_LINKCACHE +0s … 0.145s
#45 linkCache_getLink using $NBC_LINKCACHE +0s … 0.145s
#46 linkCache_getLink using $NBC_LINKCACHE +0s … 0.146s
#47 linkCache_getLink using $NBC_LINKCACHE +0s … 0.146s
#48 linkCache_getLink using $NBC_LINKCACHE +0s … 0.146s
#49 linkCache_getLink using $NBC_LINKCACHE +0s … 0.147s
#50 linkCache_getLink using $NBC_LINKCACHE +0s … 0.147s
#51 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.147s
#52 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#53 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#54 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#55 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#56 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#57 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#58 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#59 min, max, avg, median took s +0s … 0.15s
#60 before gaming benchmark output +0s … 0.15s
#61 Got 462 rows for game benchmarks. +0.023s … 0.173s
#62 composed SQL query for gamebenchmarks +0s … 0.173s
#63 linkCache_getLink using $NBC_LINKCACHE +0s … 0.173s
#64 linkCache_getLink using $NBC_LINKCACHE +0s … 0.173s
#65 linkCache_getLink using $NBC_LINKCACHE +0s … 0.173s
#66 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.173s
#67 linkCache_getLink using $NBC_LINKCACHE +0s … 0.173s
#68 linkCache_getLink using $NBC_LINKCACHE +0s … 0.173s
#69 linkCache_getLink using $NBC_LINKCACHE +0s … 0.173s
#70 linkCache_getLink using $NBC_LINKCACHE +0s … 0.173s
#71 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#72 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#73 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#74 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#75 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#76 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#77 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#78 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#79 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#80 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#81 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.174s
#82 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#83 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#84 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#85 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#86 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#87 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#88 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#89 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#90 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#91 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#92 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#93 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#94 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#95 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#96 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.175s
#97 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#98 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#99 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#102 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#104 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#105 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#107 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#110 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.175s
#111 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#112 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#113 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#114 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#116 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#123 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#124 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.175s
#125 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#126 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#127 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#128 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#129 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#130 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#133 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#134 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#137 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#138 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.176s
#139 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#140 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#141 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#143 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#144 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#145 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#146 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#147 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#148 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#149 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#150 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#151 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#152 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.177s
#153 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#154 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#155 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#156 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#157 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#158 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#160 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#161 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#162 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#163 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#164 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#165 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#166 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.177s
#167 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#168 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#169 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#171 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#172 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#173 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#174 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#175 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#176 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#179 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#180 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.177s
#181 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#182 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#183 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#184 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#185 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#186 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#187 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#188 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#189 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#191 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#192 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#193 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#194 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.178s
#195 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#196 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#197 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#198 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#199 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#200 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#201 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#202 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#203 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#204 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#205 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#206 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#207 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#208 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.178s
#209 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#210 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#211 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#212 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#213 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#214 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#215 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#216 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#217 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#218 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#219 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#220 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#221 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#222 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.178s
#223 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#224 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#225 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#226 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#227 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#228 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#229 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#230 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#231 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#232 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#233 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#234 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#235 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#236 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.179s
#237 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#238 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#239 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#240 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#241 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#242 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#243 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#244 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#245 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#246 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#247 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#248 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#249 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#250 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.179s
#251 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#252 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#253 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#254 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#255 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#256 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#257 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#258 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#259 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#260 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#261 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#262 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#263 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#264 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.179s
#265 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#266 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#267 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#268 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#269 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#270 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#271 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#272 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#273 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#274 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#275 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#276 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#277 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#278 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.18s
#279 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#280 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#281 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#282 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#283 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#284 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#285 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#286 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#287 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#288 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#289 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#290 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#291 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#292 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#293 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.18s
#294 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#295 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#296 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#297 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#298 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#299 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#300 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#301 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#302 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#303 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#304 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#305 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#306 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#307 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#308 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.18s
#309 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#310 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#311 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#312 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#313 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#314 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#315 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#316 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#317 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#318 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#319 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#320 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#321 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#322 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.181s
#323 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#324 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#325 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#326 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#327 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#328 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#329 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#330 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#331 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#332 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#333 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#334 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#335 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#336 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.181s
#337 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#338 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#339 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#340 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#341 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#342 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#343 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#344 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#345 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#346 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#347 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#348 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#349 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#350 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.182s
#351 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#352 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#353 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#354 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#355 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#356 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#357 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#358 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#359 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#360 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#361 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#362 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#363 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#364 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.182s
#365 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#366 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#367 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#368 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#369 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#370 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#371 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#372 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#373 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#374 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#375 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#376 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#377 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#378 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.182s
#379 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#380 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#381 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#382 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#383 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#384 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#385 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#386 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#387 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#388 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#389 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#390 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#391 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#392 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.183s
#393 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#394 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#395 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#396 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#397 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#398 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#399 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#400 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#401 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#402 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#403 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#404 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#405 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#406 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.184s
#407 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#408 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#409 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#410 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#411 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#412 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#413 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#414 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#415 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#416 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#417 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#418 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#419 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#420 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.184s
#421 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#422 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#423 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#424 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#425 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#426 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#427 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#428 linkCache_getLink using $NBC_LINKCACHE +0s … 0.185s
#429 linkCache_getLink using $NBC_LINKCACHE +0s … 0.185s
#430 linkCache_getLink using $NBC_LINKCACHE +0s … 0.185s
#431 linkCache_getLink using $NBC_LINKCACHE +0s … 0.185s
#432 got data and put it in $dataArray +0.003s … 0.188s
#433 linkCache_getLink using $NBC_LINKCACHE +0.033s … 0.221s
#434 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.221s
#435 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#436 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#437 linkCache_getLink using $NBC_LINKCACHE +0.038s … 0.259s
#438 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s
#439 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s
#440 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s
#441 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s
#442 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s
#443 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s
#444 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s
#445 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.26s
#446 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s
#447 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s
#448 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.26s
#449 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s
#450 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.26s
#451 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s
#452 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s
#453 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s
#454 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s
#455 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s
#456 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s
#457 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.261s
#458 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s
#459 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s
#460 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s
#461 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s
#462 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.261s
#463 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.262s
#464 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s
#465 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s
#466 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.262s
#467 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.263s
#468 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s
#469 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s
#470 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s
#471 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s
#472 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s
#473 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s
#474 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s
#475 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s
#476 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.263s
#477 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.264s
#478 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s
#479 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s
#480 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s
#481 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s
#482 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s
#483 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s
#484 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.265s
#485 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s
#486 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s
#487 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s
#488 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.265s
#489 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s
#490 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.266s
#491 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s
#492 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.266s
#493 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s
#494 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s
#495 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s
#496 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s
#497 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s
#498 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s
#499 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s
#500 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.267s
#501 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s
#502 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s
#503 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s
#504 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.267s
#505 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s
#506 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s
#507 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s
#508 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.268s
#509 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s
#510 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s
#511 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s
#512 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s
#513 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s
#514 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s
#515 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s
#516 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.268s
#517 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s
#518 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.268s
#519 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s
#520 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s
#521 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s
#522 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s
#523 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s
#524 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s
#525 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.269s
#526 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s
#527 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s
#528 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s
#529 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s
#530 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s
#531 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s
#532 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.269s
#533 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s
#534 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.27s
#535 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s
#536 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s
#537 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s
#538 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s
#539 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s
#540 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s
#541 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s
#542 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.271s
#543 linkCache_getLink using $NBC_LINKCACHE +0s … 0.271s
#544 linkCache_getLink using $NBC_LINKCACHE +0s … 0.271s
#545 linkCache_getLink using $NBC_LINKCACHE +0s … 0.271s
#546 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.271s
#547 linkCache_getLink using $NBC_LINKCACHE +0s … 0.271s
#548 linkCache_getLink using $NBC_LINKCACHE +0s … 0.271s
#549 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.272s
#550 linkCache_getLink using $NBC_LINKCACHE +0s … 0.272s
#551 linkCache_getLink using $NBC_LINKCACHE +0s … 0.272s
#552 linkCache_getLink using $NBC_LINKCACHE +0s … 0.272s
#553 linkCache_getLink using $NBC_LINKCACHE +0s … 0.272s
#554 linkCache_getLink using $NBC_LINKCACHE +0s … 0.272s
#555 linkCache_getLink using $NBC_LINKCACHE +0s … 0.272s
#556 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.272s
#557 linkCache_getLink using $NBC_LINKCACHE +0s … 0.272s
#558 linkCache_getLink using $NBC_LINKCACHE +0s … 0.272s
#559 linkCache_getLink using $NBC_LINKCACHE +0s … 0.272s
#560 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.273s
#561 linkCache_getLink using $NBC_LINKCACHE +0s … 0.273s
#562 linkCache_getLink using $NBC_LINKCACHE +0s … 0.273s
#563 linkCache_getLink using $NBC_LINKCACHE +0s … 0.273s
#564 linkCache_getLink using $NBC_LINKCACHE +0s … 0.273s
#565 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.274s
#566 linkCache_getLink using $NBC_LINKCACHE +0s … 0.274s
#567 linkCache_getLink using $NBC_LINKCACHE +0s … 0.274s
#568 linkCache_getLink using $NBC_LINKCACHE +0s … 0.274s
#569 linkCache_getLink using $NBC_LINKCACHE +0s … 0.274s
#570 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.275s
#571 linkCache_getLink using $NBC_LINKCACHE +0s … 0.275s
#572 linkCache_getLink using $NBC_LINKCACHE +0s … 0.275s
#573 linkCache_getLink using $NBC_LINKCACHE +0s … 0.275s
#574 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.275s
#575 linkCache_getLink using $NBC_LINKCACHE +0s … 0.275s
#576 linkCache_getLink using $NBC_LINKCACHE +0s … 0.275s
#577 linkCache_getLink using $NBC_LINKCACHE +0s … 0.275s
#578 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.275s
#579 linkCache_getLink using $NBC_LINKCACHE +0s … 0.275s
#580 linkCache_getLink using $NBC_LINKCACHE +0s … 0.275s
#581 linkCache_getLink using $NBC_LINKCACHE +0s … 0.275s
#582 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.276s
#583 linkCache_getLink using $NBC_LINKCACHE +0s … 0.276s
#584 linkCache_getLink using $NBC_LINKCACHE +0s … 0.276s
#585 linkCache_getLink using $NBC_LINKCACHE +0s … 0.276s
#586 linkCache_getLink using $NBC_LINKCACHE +0s … 0.276s
#587 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.277s
#588 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.277s
#589 linkCache_getLink using $NBC_LINKCACHE +0s … 0.277s
#590 linkCache_getLink using $NBC_LINKCACHE +0s … 0.277s
#591 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.277s
#592 linkCache_getLink using $NBC_LINKCACHE +0s … 0.277s
#593 linkCache_getLink using $NBC_LINKCACHE +0s … 0.277s
#594 linkCache_getLink using $NBC_LINKCACHE +0s … 0.277s
#595 linkCache_getLink using $NBC_LINKCACHE +0s … 0.277s
#596 linkCache_getLink using $NBC_LINKCACHE +0s … 0.277s
#597 linkCache_getLink using $NBC_LINKCACHE +0s … 0.278s
#598 linkCache_getLink using $NBC_LINKCACHE +0s … 0.278s
#599 linkCache_getLink using $NBC_LINKCACHE +0s … 0.278s
#600 linkCache_getLink using $NBC_LINKCACHE +0s … 0.278s
#601 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.278s
#602 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.278s
#603 linkCache_getLink using $NBC_LINKCACHE +0s … 0.278s
#604 linkCache_getLink using $NBC_LINKCACHE +0s … 0.278s
#605 linkCache_getLink using $NBC_LINKCACHE +0s … 0.278s
#606 linkCache_getLink using $NBC_LINKCACHE +0s … 0.278s
#607 linkCache_getLink using $NBC_LINKCACHE +0s … 0.278s
#608 linkCache_getLink using $NBC_LINKCACHE +0s … 0.278s
#609 linkCache_getLink using $NBC_LINKCACHE +0s … 0.278s
#610 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.279s
#611 linkCache_getLink using $NBC_LINKCACHE +0s … 0.279s
#612 linkCache_getLink using $NBC_LINKCACHE +0s … 0.279s
#613 linkCache_getLink using $NBC_LINKCACHE +0s … 0.279s
#614 linkCache_getLink using $NBC_LINKCACHE +0s … 0.279s
#615 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.28s
#616 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.28s
#617 linkCache_getLink using $NBC_LINKCACHE +0s … 0.28s
#618 linkCache_getLink using $NBC_LINKCACHE +0s … 0.28s
#619 linkCache_getLink using $NBC_LINKCACHE +0s … 0.28s
#620 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.28s
#621 linkCache_getLink using $NBC_LINKCACHE +0s … 0.28s
#622 linkCache_getLink using $NBC_LINKCACHE +0s … 0.281s
#623 linkCache_getLink using $NBC_LINKCACHE +0s … 0.281s
#624 linkCache_getLink using $NBC_LINKCACHE +0s … 0.281s
#625 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.281s
#626 linkCache_getLink using $NBC_LINKCACHE +0s … 0.281s
#627 linkCache_getLink using $NBC_LINKCACHE +0s … 0.281s
#628 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.282s
#629 linkCache_getLink using $NBC_LINKCACHE +0s … 0.282s
#630 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.282s
#631 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.283s
#632 linkCache_getLink using $NBC_LINKCACHE +0s … 0.283s
#633 linkCache_getLink using $NBC_LINKCACHE +0s … 0.283s
#634 linkCache_getLink using $NBC_LINKCACHE +0s … 0.283s
#635 linkCache_getLink using $NBC_LINKCACHE +0s … 0.283s
#636 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.283s
#637 linkCache_getLink using $NBC_LINKCACHE +0s … 0.283s
#638 linkCache_getLink using $NBC_LINKCACHE +0s … 0.283s
#639 linkCache_getLink using $NBC_LINKCACHE +0s … 0.283s
#640 linkCache_getLink using $NBC_LINKCACHE +0s … 0.283s
#641 linkCache_getLink using $NBC_LINKCACHE +0s … 0.283s
#642 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.284s
#643 linkCache_getLink using $NBC_LINKCACHE +0s … 0.284s
#644 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.284s
#645 linkCache_getLink using $NBC_LINKCACHE +0s … 0.284s
#646 linkCache_getLink using $NBC_LINKCACHE +0s … 0.284s
#647 linkCache_getLink using $NBC_LINKCACHE +0s … 0.284s
#648 linkCache_getLink using $NBC_LINKCACHE +0s … 0.284s
#649 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.285s
#650 linkCache_getLink using $NBC_LINKCACHE +0s … 0.285s
#651 linkCache_getLink using $NBC_LINKCACHE +0s … 0.285s
#652 linkCache_getLink using $NBC_LINKCACHE +0s … 0.285s
#653 linkCache_getLink using $NBC_LINKCACHE +0s … 0.285s
#654 linkCache_getLink using $NBC_LINKCACHE +0s … 0.285s
#655 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.286s
#656 linkCache_getLink using $NBC_LINKCACHE +0s … 0.286s
#657 linkCache_getLink using $NBC_LINKCACHE +0s … 0.286s
#658 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.286s
#659 linkCache_getLink using $NBC_LINKCACHE +0s … 0.286s
#660 linkCache_getLink using $NBC_LINKCACHE +0s … 0.286s
#661 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.286s
#662 linkCache_getLink using $NBC_LINKCACHE +0s … 0.286s
#663 linkCache_getLink using $NBC_LINKCACHE +0s … 0.286s
#664 linkCache_getLink using $NBC_LINKCACHE +0s … 0.286s
#665 linkCache_getLink using $NBC_LINKCACHE +0s … 0.286s
#666 linkCache_getLink using $NBC_LINKCACHE +0s … 0.286s
#667 linkCache_getLink using $NBC_LINKCACHE +0s … 0.286s
#668 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.287s
#669 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#670 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.288s
#671 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#672 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.288s
#673 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.288s
#674 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#675 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#676 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.289s
#677 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#678 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#679 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#680 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.29s
#681 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#682 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#683 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.29s
#684 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#685 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#686 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.29s
#687 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.291s
#688 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#689 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#690 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#691 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#692 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.292s
#693 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.292s
#694 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.293s
#695 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#696 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#697 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#698 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.294s
#699 linkCache_getLink using $NBC_LINKCACHE +0s … 0.294s
#700 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.294s
#701 linkCache_getLink using $NBC_LINKCACHE +0s … 0.294s
#702 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.294s
#703 linkCache_getLink using $NBC_LINKCACHE +0s … 0.295s
#704 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.295s
#705 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.296s
#706 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.296s
#707 linkCache_getLink using $NBC_LINKCACHE +0s … 0.296s
#708 linkCache_getLink using $NBC_LINKCACHE +0s … 0.296s
#709 linkCache_getLink using $NBC_LINKCACHE +0s … 0.297s
#710 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.297s
#711 linkCache_getLink using $NBC_LINKCACHE +0s … 0.297s
#712 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.298s
#713 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.298s
#714 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.298s
#715 benchmarks composed for output. +0s … 0.298s
#716 calculated avg scores. +0s … 0.299s
#717 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.301s
#718 return log +0.002s … 0.304s
AMD Radeon RX 460 (Desktop) vs AMD Radeon RX 470 (Laptop)
Die folgenden Benchmarks basieren auf unseren Spieletests mit Testnotebooks. Die Performance dieser Grafikkarte bei den gelisteten Spielen ist abhängig von der verwendeten CPU, Speicherausstattung, Treiber und auch Betriebssystem. Dadurch müssen die untenstehenden Werte nicht repräsentativ sein. Detaillierte Informationen über das verwendete System sehen Sie nach einem Klick auf den fps-Wert.
log 30. 13:21:09
#0 checking url part for id 7375 +0s … 0s
#1 checking url part for id 7586 +0s … 0s
#2 not redirecting to Ajax server +0s … 0s
#3 did not recreate cache, as it is less than 5 days old! Created at Tue, 27 Sep 2022 17:27:11 +0200 +0s .
.. 0s
#4 linkCache_getLink using $NBC_LINKCACHE +0.083s … 0.083s
#5 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.085s
#6 linkCache_getLink using $NBC_LINKCACHE +0s … 0.086s
#7 linkCache_getLink using $NBC_LINKCACHE +0s … 0.086s
#8 composed specs +0s … 0.086s
#9 did output specs +0s … 0.086s
#10 start showIntegratedCPUs +0s … 0.086s
#11 getting avg benchmarks for device 7375 +0.028s … 0.113s
#12 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.114s
#13 got single benchmarks 7375 +0.007s … 0.121s
#14 getting avg benchmarks for device 7586 +0s … 0.121s
#15 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.122s
#16 got single benchmarks 7586 +0.004s … 0.126s
#17 got avg benchmarks for devices +0s … 0.126s
#18 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.126s
#19 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.127s
#20 linkCache_getLink using $NBC_LINKCACHE +0s … 0.127s
#21 linkCache_getLink using $NBC_LINKCACHE +0s … 0.127s
#22 linkCache_getLink using $NBC_LINKCACHE +0s … 0.128s
#23 linkCache_getLink no uid found +0s … 0.128s
#24 linkCache_getLink using $NBC_LINKCACHE +0s … 0.128s
#25 linkCache_getLink no uid found +0s … 0.129s
#26 linkCache_getLink using $NBC_LINKCACHE +0s … 0.129s
#27 linkCache_getLink using $NBC_LINKCACHE +0s … 0.129s
#28 linkCache_getLink using $NBC_LINKCACHE +0s … 0.13s
#29 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.13s
#30 linkCache_getLink using $NBC_LINKCACHE +0s … 0.131s
#31 linkCache_getLink using $NBC_LINKCACHE +0s … 0.131s
#32 linkCache_getLink using $NBC_LINKCACHE +0s … 0.131s
#33 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#34 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.132s
#35 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#36 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#37 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#38 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#39 min, max, avg, median took s +0s … 0.134s
#40 before gaming benchmark output +0s … 0.134s
#41 Got 278 rows for game benchmarks. +0.013s … 0.146s
#42 composed SQL query for gamebenchmarks +0s … 0.146s
#43 linkCache_getLink using $NBC_LINKCACHE +0s … 0.147s
#44 linkCache_getLink using $NBC_LINKCACHE +0s … 0.147s
#45 linkCache_getLink using $NBC_LINKCACHE +0s … 0.147s
#46 linkCache_getLink using $NBC_LINKCACHE +0s … 0.147s
#47 linkCache_getLink using $NBC_LINKCACHE +0s … 0.147s
#48 linkCache_getLink using $NBC_LINKCACHE +0s … 0.147s
#49 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.147s
#50 linkCache_getLink using $NBC_LINKCACHE +0s … 0.147s
#51 linkCache_getLink using $NBC_LINKCACHE +0s … 0.147s
#52 linkCache_getLink using $NBC_LINKCACHE +0s … 0.147s
#53 linkCache_getLink using $NBC_LINKCACHE +0s … 0.147s
#54 linkCache_getLink using $NBC_LINKCACHE +0s … 0.147s
#55 linkCache_getLink using $NBC_LINKCACHE +0s … 0.147s
#56 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.148s
#57 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#58 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#59 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#60 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#61 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#62 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#63 linkCache_getLink using $NBC_LINKCACHE +0s … 0.
148s
#64 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#65 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#66 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#67 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#68 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#69 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#70 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#71 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#72 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#73 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#74 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#75 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#76 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#77 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#78 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.149s
#79 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#80 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#81 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#82 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#83 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#84 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#85 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#86 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#87 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#88 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#89 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#90 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#91 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#92 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#93 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.149s
#94 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#95 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#96 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#97 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#98 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#99 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#102 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#104 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#105 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#107 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#108 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.15s
#109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#110 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#111 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#112 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#113 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#114 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#116 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#123 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.151s
#124 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#125 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#126 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#127 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#128 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#129 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#130 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#133 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#134 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#137 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.151s
#138 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#139 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#140 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#141 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#143 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#144 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#145 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#146 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#147 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#148 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#149 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#150 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#151 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.152s
#152 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#153 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#154 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#155 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#156 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#157 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#158 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#160 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#161 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#162 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#163 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#164 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#165 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.152s
#166 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#167 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#168 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#169 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#171 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#172 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#173 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#174 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#175 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#176 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#179 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.153s
#180 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#181 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#182 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#183 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#184 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#185 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#186 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#187 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#188 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#189 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#191 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#192 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#193 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.154s
#194 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#195 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#196 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#197 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#198 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#199 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#200 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#201 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#202 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#203 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#204 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#205 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#206 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#207 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.154s
#208 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#209 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#210 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#211 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#212 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#213 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#214 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#215 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#216 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#217 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#218 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#219 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#220 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#221 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.155s
#222 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#223 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#224 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#225 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#226 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#227 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#228 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#229 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#230 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#231 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#232 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#233 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#234 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#235 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.156s
#236 got data and put it in $dataArray +0.006s … 0.162s
#237 linkCache_getLink using $NBC_LINKCACHE +0.031s … 0.193s
#238 linkCache_getLink using $NBC_LINKCACHE +0s … 0.193s
#239 linkCache_getLink using $NBC_LINKCACHE +0s … 0.193s
#240 linkCache_getLink using $NBC_LINKCACHE +0s … 0.193s
#241 linkCache_getLink using $NBC_LINKCACHE +0.009s … 0.203s
#242 linkCache_getLink using $NBC_LINKCACHE +0s … 0.203s
#243 linkCache_getLink using $NBC_LINKCACHE +0s … 0.203s
#244 linkCache_getLink using $NBC_LINKCACHE +0s … 0.203s
#245 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.203s
#246 linkCache_getLink using $NBC_LINKCACHE +0s … 0.203s
#247 linkCache_getLink using $NBC_LINKCACHE +0s … 0.203s
#248 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.204s
#249 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.204s
#250 linkCache_getLink using $NBC_LINKCACHE +0s … 0.204s
#251 linkCache_getLink using $NBC_LINKCACHE +0s … 0.204s
#252 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.205s
#253 linkCache_getLink using $NBC_LINKCACHE +0s … 0.205s
#254 linkCache_getLink using $NBC_LINKCACHE +0s … 0.205s
#255 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.205s
#256 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.206s
#257 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.207s
#258 linkCache_getLink using $NBC_LINKCACHE +0s … 0.207s
#259 linkCache_getLink using $NBC_LINKCACHE +0s … 0.207s
#260 linkCache_getLink using $NBC_LINKCACHE +0s … 0.207s
#261 linkCache_getLink using $NBC_LINKCACHE +0s … 0.207s
#262 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.207s
#263 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.208s
#264 linkCache_getLink using $NBC_LINKCACHE +0s … 0.208s
#265 linkCache_getLink using $NBC_LINKCACHE +0s … 0.208s
#266 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.208s
#267 linkCache_getLink using $NBC_LINKCACHE +0s … 0.208s
#268 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.209s
#269 linkCache_getLink using $NBC_LINKCACHE +0s … 0.209s
#270 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.209s
#271 linkCache_getLink using $NBC_LINKCACHE +0s … 0.209s
#272 linkCache_getLink using $NBC_LINKCACHE +0s … 0.209s
#273 linkCache_getLink using $NBC_LINKCACHE +0s … 0.21s
#274 linkCache_getLink using $NBC_LINKCACHE +0s … 0.21s
#275 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.211s
#276 linkCache_getLink using $NBC_LINKCACHE +0s … 0.211s
#277 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.211s
#278 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.212s
#279 linkCache_getLink using $NBC_LINKCACHE +0s … 0.212s
#280 linkCache_getLink using $NBC_LINKCACHE +0s … 0.212s
#281 linkCache_getLink using $NBC_LINKCACHE +0s … 0.212s
#282 linkCache_getLink using $NBC_LINKCACHE +0s … 0.212s
#283 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.212s
#284 linkCache_getLink using $NBC_LINKCACHE +0s … 0.212s
#285 linkCache_getLink using $NBC_LINKCACHE +0s … 0.212s
#286 linkCache_getLink using $NBC_LINKCACHE +0s … 0.212s
#287 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.213s
#288 linkCache_getLink using $NBC_LINKCACHE +0s … 0.213s
#289 linkCache_getLink using $NBC_LINKCACHE +0s … 0.213s
#290 linkCache_getLink using $NBC_LINKCACHE +0s … 0.213s
#291 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.214s
#292 linkCache_getLink using $NBC_LINKCACHE +0s … 0.214s
#293 linkCache_getLink using $NBC_LINKCACHE +0s … 0.214s
#294 linkCache_getLink using $NBC_LINKCACHE +0s … 0.214s
#295 linkCache_getLink using $NBC_LINKCACHE +0s … 0.214s
#296 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.214s
#297 linkCache_getLink using $NBC_LINKCACHE +0s … 0.214s
#298 linkCache_getLink using $NBC_LINKCACHE +0s … 0.214s
#299 linkCache_getLink using $NBC_LINKCACHE +0s … 0.214s
#300 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.215s
#301 linkCache_getLink using $NBC_LINKCACHE +0s … 0.215s
#302 linkCache_getLink using $NBC_LINKCACHE +0s … 0.215s
#303 linkCache_getLink using $NBC_LINKCACHE +0s … 0.215s
#304 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.216s
#305 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.216s
#306 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.217s
#307 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#308 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.218s
#309 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#310 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#311 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.219s
#312 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#313 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#314 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#315 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#316 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.22s
#317 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#318 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.221s
#319 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.221s
#320 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#321 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.222s
#322 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#323 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.222s
#324 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#325 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#326 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#327 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#328 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.223s
#329 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#330 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#331 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#332 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.224s
#333 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.224s
#334 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#335 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.225s
#336 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#337 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#338 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.225s
#339 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#340 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#341 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.226s
#342 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#343 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#344 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.227s
#345 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#346 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#347 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.228s
#348 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#349 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#350 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.229s
#351 linkCache_getLink using $NBC_LINKCACHE +0s … 0.229s
#352 linkCache_getLink using $NBC_LINKCACHE +0s … 0.229s
#353 linkCache_getLink using $NBC_LINKCACHE +0s … 0.229s
#354 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.229s
#355 linkCache_getLink using $NBC_LINKCACHE +0s … 0.229s
#356 linkCache_getLink using $NBC_LINKCACHE +0s … 0.229s
#357 linkCache_getLink using $NBC_LINKCACHE +0s … 0.229s
#358 linkCache_getLink using $NBC_LINKCACHE +0s … 0.229s
#359 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.23s
#360 linkCache_getLink using $NBC_LINKCACHE +0s … 0.23s
#361 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.231s
#362 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.231s
#363 linkCache_getLink using $NBC_LINKCACHE +0s … 0.231s
#364 linkCache_getLink using $NBC_LINKCACHE +0s … 0.231s
#365 linkCache_getLink using $NBC_LINKCACHE +0s … 0.231s
#366 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.232s
#367 linkCache_getLink using $NBC_LINKCACHE +0s … 0.232s
#368 linkCache_getLink using $NBC_LINKCACHE +0s … 0.232s
#369 linkCache_getLink using $NBC_LINKCACHE +0s … 0.232s
#370 linkCache_getLink using $NBC_LINKCACHE +0s … 0.232s
#371 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.233s
#372 linkCache_getLink using $NBC_LINKCACHE +0s … 0.233s
#373 linkCache_getLink using $NBC_LINKCACHE +0s … 0.233s
#374 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.234s
#375 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.234s
#376 linkCache_getLink using $NBC_LINKCACHE +0s … 0.234s
#377 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.235s
#378 linkCache_getLink using $NBC_LINKCACHE +0s … 0.235s
#379 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.236s
#380 linkCache_getLink using $NBC_LINKCACHE +0s … 0.236s
#381 linkCache_getLink using $NBC_LINKCACHE +0s … 0.236s
#382 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.237s
#383 linkCache_getLink using $NBC_LINKCACHE +0s … 0.237s
#384 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.238s
#385 linkCache_getLink using $NBC_LINKCACHE +0s … 0.238s
#386 linkCache_getLink using $NBC_LINKCACHE +0s … 0.238s
#387 linkCache_getLink using $NBC_LINKCACHE +0s … 0.238s
#388 linkCache_getLink using $NBC_LINKCACHE +0s … 0.238s
#389 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.239s
#390 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.24s
#391 linkCache_getLink using $NBC_LINKCACHE +0s … 0.24s
#392 linkCache_getLink using $NBC_LINKCACHE +0s … 0.24s
#393 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.241s
#394 linkCache_getLink using $NBC_LINKCACHE +0s … 0.241s
#395 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.241s
#396 linkCache_getLink using $NBC_LINKCACHE +0s … 0.241s
#397 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.242s
#398 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.243s
#399 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.244s
#400 linkCache_getLink using $NBC_LINKCACHE +0s … 0.244s
#401 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.245s
#402 linkCache_getLink using $NBC_LINKCACHE +0s … 0.245s
#403 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.245s
#404 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.246s
#405 benchmarks composed for output. +0s … 0.246s
#406 calculated avg scores. +0s … 0.246s
#407 linkCache_getLink using $NBC_LINKCACHE +0.058s … 0.305s
#408 return log +0.002s … 0.307s
AMD RX 470 & RX 460 Full Specs, New Release Date | GamersNexus
AMD says the majority of its buyers prefer GPUs in the $100-$300 price-range, and as such, the company has shifted its launch away from “halo” products and toward that affordable segment. The focus for the RX 470 is on players sticking with 1080p, allowing the RX 480 to focus on the 1440p gamers.
The RX 470 uses the Polaris 10 GPU and has the same architecture as the RX 480, including compute pre-emption and asynchronous shaders, but is cut-down in stream processor count and clock-rate. The RX 470 will host 32 CUs, as opposed to the 36 CUs of the RX 480, and that puts us at 2048 stream processors.
Knowing that each CU has 64 stream processors, none of this is actually new information yet – we’d already reported/calculated all this in our RX 480 review.
The new stuff, though, is the clock-rate: The RX 470 will operate at 1206MHz boosted and 926MHz base with its 2048 stream processors. 128 TMUs are on the 470 – for perspective, the 480 had 144 – and it’s operating with 32 ROPs. Memory operates on a 256-bit interface with a 6.6Gbps effective memory speed, and will run a capacity of 4GB of GDDR5. The memory bandwidth comes out to 211GB/s. Display interfaces include HDMI 2.0 and DisplayPort support for HDR (1.4) and HBR (1.3). TDP is listed as 120W.
AMD RX 460, RX 470, & RX 480 Specs
| AMD RX 480 | AMD RX 470 | AMD RX 460 | |
| Architecture | Polaris 10 | Polaris 10 | Polaris 11 |
| Compute Units (CUs) | 36 | 32 | 14 |
| Stream Processors | 2304 | 2048 | 864 |
| Base / Boost Clock | 1120MHz / 1266MHz | 926MHz / 1206MHz | 1090MHz / 1200MHz |
| COMPUTE Performance | >5 TFLOPS | Up to 4. 9TFLOPs |
Up to 2.2TFLOPs |
| Graphics Command Processor (GCP) | 1 | 1 | 1 |
| ACEs | 4 | 4 (?) | 2 |
| HWS | 2 | 2 (?) | 2 |
| TMUs | 144 | 128 | 56 |
| ROPs | 32 | 32 | 16 |
| Geometry Processors | 4 | 4 (?) | 2 |
| Peak Texture Filter Rate | 182.3GT/s | 154.4GT/s | 57.6GT/s |
| Peak Pixel Filter Rate | 40.5GP/s | 38.6GP/s | 19.2GP/s |
| L2 Cache | 2MB | ? | 1MB |
| LSU | 576x32b | ? | 256x32b |
| VRAM Capacity | 4GB GDDR5 @ 7Gbps 8GB GDDR5 @ 8Gbps |
4GB GDDR5 | 2GB GDDR5 |
| Memory Interface | 256-bit | 256-bit | 128-bit |
| Memory Speed | 7Gbps (4GB model) 8Gbps (8GB model) |
6. 6Gbps |
7Gbps |
| Memory Bandwidth | 224GB/s (4GB model) 256GB/s (8GB model) |
211GB/s | 112GB/s |
| TDP | 150W | 120W* | 75W |
| Power Connectors | 6-pin | 6-pin | None (Slot only) |
| Display Port | 1.3 HBR / 1.4 HDR | 1.3/1.4 HDR | 1.3/1.4 HDR |
| Release Date | June 29 | August 4 | August 8 |
Polaris 10 vs. Polaris 11 Specs & Architecture
| Polaris 10 | Polaris 11 | |
| Compute Units (CUs) | 36 | 16 |
| COMPUTE Performance | “>5 TFLOPS” | “>2 TFLOPS” |
| Memory Interface | 256-bit | 128-bit |
| Architecture | Gen 4 GCN | Gen 4 GCN |
| Playback Support | 4K encode/decode | 4K encode/decode |
| Output Standard | DP1. 3/1.4 HDR |
DP1.3/1.4 HDR |
Just a reminder: Don’t fall for the trap that so many people do. You cannot compare AMD and nVidia cards numbers-for-numbers, because the architecture is different. This goes for cores as much as it goes for TDP. AMD and nVidia differ in their calculation of TDP; 120W does not = 120W between brands. TDP is also not a measurement of actual power draw – you’ll need to wait for our tests for that.
Also, note that AMD’s specified TDP for the RX 470 has changed. The card was originally slated for a 110W TDP (during the Macau press event, just before Computex), but has now been moved to a 120W TDP. Consider also that the TMU count has dropped from 64 to 56, and that the memory speed has dropped to 6.6Gbps from 7Gbps. These original metrics were provided well before finalization of the card, so it’s likely that the changes were just a result of creating a press presentation months in advance of launch.
The memory subsystem of the RX 470 is the same as the RX 480, aside from the effective speed.
Check our written review on that card for more on delta color compression and other memory efficiency increases.
The RX 470 will be available on August 4th and is priced at… to be determined. AMD’s holding prices until release date, or slightly before. The company tells us that the RX 470 offers approximately 1.5x gains over the generations-past 270.
AMD has provided an internal RX 470 benchmark (vs. R7 270, despite the typographical error in AMD’s slide):
The above shows the RX 470’s comparative performance in Battlefield 4, DOOM, Fallout 4, Hitman, and Total War: Warhammer — but take the tests with a grain of salt, as they are conducted internally by AMD. We’ll validate in our own lab once we’ve got a card. GN doesn’t have an R7 270, but we do have the R9 270X and may revive the old dog for these tests.
Some alleged leaked photos of RX 470 partner cards have already been released, shown here:
As for the RX 460, that card will be on Polaris 11, will host 14 CUs with 896 stream processors, clocked at 1200MHz boost and 1090MHz base.
The RX 460 will have 56 TMUs and 16 ROPs. Performance is up to 2.2TFLOPs – again, Polaris 11 – and memory will run at an effective 7Gbps on 2GB or 4GB of GDDR5, with the interface 128-bits wide. That puts memory bandwidth at 112GB/s. We’ve seen some confusion lately as to how memory bandwidth is calculated; just as a reminder, it’s pretty simple: You first divide the bus by 8 to convert bits to bytes, then multiply the actual memory speed – not the same as the effective speed – by the quotient, by 2 for DDR, and by 2 again for GDDR5. That gives us 112GB/s.
TDP for the RX 460 is less than 75W, so it can function entirely off of PCIe slots. Price is also TBD. the card will be available on August 8th.
AMD’s presentation suggests that the RX 460 is targeted at eSports gaming, and further states that the card pushes «90+ FPS [at] 1080p High Settings.»
We also asked about notebook chips. Like the GTX 980, AMD will be bringing its full Polaris chips to laptops.
They are not cut-down models. The notebook models will have lower GPU TDP and a lower throttle point on thermals (e.g. 35W on notebook versus 48W on desktops, for the chip), but will otherwise be the same. It will be up to manufacturers to provide adequate cooling solutions, as is always the case. TDP has gotten so low these days that it’s possible to actually put desktop parts into notebooks, dropping the suffixed -M branding. AMD is hoping to leverage the 470 and 460 to get back into the notebook arena.
We’ll be testing both the 4GB and 8GB models of the RX 470. It’s possible that the card may become ROPs limited in many games, but we generally do see some differences in 1% low metrics when running VRAM-intensive games.
AMD missed launch on the RX 470 and 460, which were targeted at, quote, “Mid-July” and “End of July,” respectively. AMD has moved the cards to August 4 and August 8 for launch, respectively. We are still waiting on pricing information. The RX 470 & RX 460 will be partner cards.
There will be no «reference» model.
Host: Steve “Lelldorianx” Burke
Video: Andrew “ColossalCake” Coleman
0022 2.2 vs 2
170mm vs 240mm
- 3.01 TFLOPS higher than FLOPS?
5.16 TFLOPS vs 2.15 TFLOPS - 21.1 GPixel/s higher pixel rate?
40.3 GPixel/s vs 19.2 GPixel/s - 250MHz faster memory speed?
2000MHz vs 1750MHz - 1000MHz higher effective clock speed?
8000MHz vs 7000MHz - 2x more VRAM?
4GB vs 2GB - 103.7 GTexels/s higher number of textured pixels? more memory bandwidth?
256GB/s vs 112GB/s - 128bit wider memory bus?
256bit vs 128bit
What are the most popular comparisons?
AMD Radeon RX 460
vs
Nvidia GeForce GTX 750 Ti
Sapphire Nitro+ Radeon RX 470 4GB
vs
AMD Radeon RX 570
AMD Radeon RX 460
vs
Nvidia GeForce GTX 1050
Sapphire Nitro+ Radeon RX 470 4GB
vs
Sapphire Radeon RX 470
AMD Radeon RX 460
vs
AMD Radeon RX 550
Sapphire Nitro+ Radeon RX 470 4GB
vs
MSI GeForce GTX 1050 Ti
AMD Radeon RX 460
vs
AMD Radeon RX 560
Sapphire Nitro+ Radeon RX 470 4GB
VS
SAPPHire Pulse Radeon RX 570
AMD Radeon RX 460
VS
MSI GTX 1050 TI
SAPPHIRENE NITROMENED+ RADEN RADEN RADEN0003
PowerColor Red Devil Radeon RX 470
AMD Radeon RX 460
vs
Nvidia GeForce GTX 960
Sapphire Nitro+ Radeon RX 470 4GB
vs
PNY GeForce XLR8 GTX 1650 Gaming OC
AMD Radeon RX 460
VS
AMD Radeon RX Vega 8
Sapphire Nitro+ Radeon RX 470 470 470 40003
VS
GIGABYTE GTX 1650 OC
AMD RADEON RX 460 9000
NVIDIA GEFR0003
Sapphire Nitro+ Radeon RX 470 4GB
vs
Gigabyte Radeon RX 570
AMD Radeon RX 460
vs
AMD Radeon R9 380
Sapphire Nitro+ Radeon RX 470 4GB
vs
MSI Radeon RX 470 Gaming X 4GB
AMD Radeon RX 460
vs
AMD Radeon R7 260X
Sapphire Nitro+ Radeon RX 470 4GB
vs
Sapphire Radeon RX 480 8GB0 Pricing0245 10.
0 /10
2 Votes
Reviews not yet
Games
8.5 /10
2 Votes
Reviews still not
9000 9000 9000 9000 /10 9000 /10 9000 /10 9000 /10 9000 /10 VOTES
reviews not yet
fan noise
8.0 /10
2 Votes
reviews yet there are no
Reliability
245 9.0
/10
2 Votes
Reviews not yet
Productivity
1. TECTION FRIENTS GP
1090MHz
1143MHz
GPU (GPU) has a higher tact frequency.
2.turbo GPU
1200MHz
1260MHz
When the GPU is running below its limits, it can jump to a higher clock speed to increase performance.
3.pixel rate
19.2 GPixel/s
40.3 GPixel/s
The number of pixels that can be displayed on the screen every second.
4.flops
2.15 TFLOPS
5.16 TFLOPS
FLOPS is a measurement of GPU processing power.
5.texture size
57.6 GTexels/s
161.3 GTexels/s
Number of textured pixels that can be displayed on the screen every second.
6.GPU memory speed
1750MHz
2000MHz
Memory speed is one aspect that determines memory bandwidth.
7.shading patterns
Shading units (or stream processors) are small processors in a video card that are responsible for processing various aspects of an image.
8.textured units (TMUs)
TMUs accept textured units and bind them to the geometric layout of the 3D scene. More TMUs generally means texture information is processed faster.
9 ROPs
ROPs are responsible for some of the final steps of the rendering process, such as writing the final pixel data to memory and for performing other tasks such as anti-aliasing to improve the appearance of graphics.
Memory
1.memory effective speed
7000MHz
8000MHz
The effective memory clock frequency is calculated from the memory size and data transfer rate. A higher clock speed can give better performance in games and other applications.
2.max memory bandwidth
112GB/s
256GB/s
This is the maximum rate at which data can be read from or stored in memory.
3.VRAM
VRAM (video RAM) is the dedicated memory of the graphics card. More VRAM usually allows you to run games at higher settings, especially for things like texture resolution.
4.memory bus width
128bit
256bit
Wider memory bus means it can carry more data per cycle. This is an important factor in memory performance, and therefore the overall performance of the graphics card.
5.
GDDR memory versions
Later versions of GDDR memory offer improvements such as higher data transfer rates, which improve performance.
6. Supports memory troubleshooting code
✖AMD Radeon RX 460
✖Sapphire Nitro+ Radeon RX 470 4GB
Memory troubleshooting code can detect and fix data corruption. It is used when necessary to avoid distortion, such as in scientific computing or when starting a server.
Functions
1.DirectX version
DirectX is used in games with a new version that supports better graphics.
2nd version of OpenGL
The newer version of OpenGL, the better graphics quality in games.
OpenCL version 3.
Some applications use OpenCL to use the power of the graphics processing unit (GPU) for non-graphical computing. Newer versions are more functional and better quality.
4. Supports multi-monitor technology
✔AMD Radeon RX 460
✔Sapphire Nitro+ Radeon RX 470 4GB
The video card has the ability to connect multiple screens. This allows you to set up multiple monitors at the same time to create a more immersive gaming experience, such as a wider field of view.
5. GPU temperature at boot
Unknown. Help us offer a price. (AMD Radeon RX 460)
Unknown. Help us offer a price. (Sapphire Nitro+ Radeon RX 470 4GB)
Lower boot temperature — this means that the card generates less heat and the cooling system works better.
6.supports ray tracing
✖AMD Radeon RX 460
✖Sapphire Nitro+ Radeon RX 470 4GB
Ray tracing is an advanced light rendering technique that provides more realistic lighting, shadows and reflections in games.
7.Supports 3D
✔AMD Radeon RX 460
✔Sapphire Nitro+ Radeon RX 470 4GB
Allows you to view in 3D (if you have a 3D screen and glasses).
8.supports DLSS
✖AMD Radeon RX 460
✖Sapphire Nitro+ Radeon RX 470 4GB
DLSS (Deep Learning Super Sampling) is an AI based scaling technology. This allows the graphics card to render games at lower resolutions and upscale them to higher resolutions with near-native visual quality and improved performance. DLSS is only available in some games.
9. PassMark result (G3D)
Unknown. Help us offer a price. (AMD Radeon RX 460)
Unknown. Help us offer a price. (Sapphire Nitro+ Radeon RX 470 4GB)
This test measures the graphics performance of a graphics card. Source: Pass Mark.
Ports
1.has HDMI output
✔AMD Radeon RX 460
✔Sapphire Nitro+ Radeon RX 470 4GB
Devices with HDMI or mini HDMI ports can stream HD video and audio to the connected display.
2.HDMI connectors
More HDMI connectors allow you to connect multiple devices at the same time, such as game consoles and TVs.
HDMI 3.Version
HDMI 2.0
HDMI 2.0
New HDMI versions support higher bandwidth, resulting in higher resolutions and frame rates.
4. DisplayPort outputs
Allows connection to a display using DisplayPort.
5.DVI outputs
Allows connection to a display using DVI.
Mini DisplayPort 6.outs
Allows connection to a display using Mini DisplayPort.
Price Match
Cancel
Which graphics cards are better?
AMD Radeon RX 460 vs AMD Radeon RX 470 (mobile) comparison, which is better? AMD Radeon RX 460 vs AMD Radeon RX 470 Mobile
AMD Radeon RX 460
83%
DeviceList Score
vs
AMD Radeon RX 470 Mobile
81%
DeviceList Score
benefits and comparison table. Find out which one to choose in 2022.
AMD Radeon RX 460 benefits
Comparison winner
|
Value for money |
|
62. 26% (71.8%) better than vs 36.2% |
|
Release price |
|
$86 -463.99 $ (-84.4%) better than vs $549.99 |
|
Core frequency |
|
1090 MHz 164 MHz (17.7%) better than vs 926 MHz |
|
Boost frequency |
|
1200 MHz 126 MHz (11.7%) better than vs 1074 MHz |
|
Power consumption (TDP) |
|
75 W -10 W (-11.8%) better than vs 85 W |
2%
AMD Radeon RX 470 Mobile Benefits
|
Number of shaders |
|
2048 1152 (128. vs 896 |
|
Maximum memory |
|
8 GB 6 GB (300%) better than vs 2 GB |
|
Memory bus width |
|
256 bit 128 bits (100%) better than vs 128 bit |
|
Memory bandwidth |
|
224 112 (100%) better than vs 112 |
6%) better than | General information | |
|
Price-quality ratio The sum of all the advantages of the device divided by its price. The more%, the better the quality per unit price in comparison with all analogues. |
|
| 62.2%
26% (71.8%) better than |
36.2% |
|
Architecture |
|
GCN 4. 0 |
GCN 4.0 |
|
Codename |
|
| Baffin | Ellesmere |
|
Type |
|
| Desktop | For laptops |
|
Release price |
|
| $86
-463.99 $ (-84.4%) better than |
$549.99 |
|
Number of shaders |
|
| 896 | 2048
1152 (128.6%) better than |
|
Core clock |
|
| 1090MHz
At 164 MHz (17.7%) better than |
926 MHz |
|
Boost frequency |
|
| 1200 MHz
At 126 MHz (11.7%) better than |
1074 MHz |
|
Number of transistors |
|
| 3.000 million | 5.700 million |
|
Process |
|
| 14 nm | 14 nm |
|
Interface |
|
PCIe 3. 0 x8 |
MXM-B (3.0) |
|
Power Demand (TDP) Calculated thermal power indicates the average heat dissipation in load operation, |
|
| 75W
-10 W (-11.8%) better than |
85 W |
|
Length |
|
| 170 mm | n/a |
|
Additional power connectors |
|
| no | n/a |
|
FreeSync |
|
| + | + |
|
DisplayPort 1.3 HBR / 1.4 HDR Ready |
|
| + | + |
|
Video connectors |
|
| 1x DVI, 1x HDMI, 1x DisplayPort | No outputs |
|
DirectX |
|
| 12 (12_0) | 12 (12_0) |
|
Floating point performance |
|
2. 150 gflops |
4.399 gflops |
| benchmark |
| 9 | GDDR5 | |
|
Maximum memory Large amount of video memory allows you to run demanding games with a lot of textures, |
||
| 2 GB | 8 GB
6 GB (300%) better than |
|
|
Memory bus width The wider the video memory bus, the more data is transferred to the GPU per unit of time and the better performance in demanding games. |
||
| 128bit | 256 bit
128 bit (100%) better than |
|
|
Shared memory |
||
| — | — | |
|
Memory frequency A high memory frequency has a positive effect on the speed of a video card with a large amount of data. |
||
| 7000 MHz | 7000 MHz | |
|
Memory bandwidth The higher the data transfer bandwidth, the more effective amount of RAM the PC can use. |
||
| 112 | 224
112 (100%) better than |
|
AMD Radeon RX 470 and RX 460 Specs Confirmed — NVIDIA WORLD NVIDIA
AMD has confirmed the specifications for its second and third Polaris architecture graphics cards, the Radeon RX 470 and Radeon RX 460, in a leaked presentation.
With the release of new mid-range graphics cards from NVIDIA, AMD has entered an active phase of the battle for this market segment.
In addition to preparing a new interim version based on Polaris10, the company decided to again talk about the benefits of the Radeon RX 460 and Radeon RX 470 accelerators, which included DirectX 12 and FreeSync, and also announced a price reduction for them.
Radeon RX 460 now has a base price of $100 and RX 470 is now $170. Recall that NVIDIA’s competitive solutions, GeForce GTX 1050 and GTX 1050 Ti, are sold at a base price of $110 and $140, respectively.
A number of AMD manufacturing partners have already cut prices. For example, the Radeon RX 460 4GB can already be found on sale for $120, and some versions with 2 GB of memory are sold for $100.
AMDRadeon RX video card market 460470
1 Comment has released a major update to the release version of its popular AIDA64 diagnostic and test utility.
This version of the utility suite supports the latest versions of Windows 10 and the latest hardware solutions, including AMD RX 400 series and NVIDIA GTX 1050 series graphics cards.
The new version prompts users to define global hotkeys, allowing them to enable and disable hardware monitoring panels and switch between different information pages on the secondary display. Also, using these hotkeys, you can enable and disable the recording of graphs in the log file.
AIDA64 v5.80 adds a resolution control that allows you to accurately display graphs without blurring lines when Windows zoom is enabled.
Full list of changes is given below:
- Added 64-bit tests with AVX and FMA acceleration for AMD A-Series Bristol Ridge APUs.
- Added hotkeys for switching between pages, starting/stopping logging and displaying the gauges panel.
- Improved DPI scaling to better support high resolution screens and OLED panels.
- Added support for Corsair and Razer RGBLED mouse pads.
- Added support for Microsoft Windows 10 Redstone RS2 Insider Preview.
- Improved support for AMD Zen Summit Ridge.
- Improved support for Intel Apollo Lake.
- Added support for Samsung PM851 and SanDisk X400 SSDs.
- Improved NVMe SSD support.
- Added support for CUDA 8.0.
- Detailed AMD Radeon RX 400 GPUs.
- Detailed NVIDIA GeForce GTX 1050, GeForce GTX 1050 Ti, and GeForce GTX 1060 GPUs.
Extreme Engineer for engineers with permission to use on an unlimited number of PCs, which can be purchased from the AIDA64 online store. 96 stream processors, 48 texture units, 16 ROPs and 4 or 2 gigabytes of GDDR5 video memory. The GPU frequency will be 1200 MHz.
Although the leak is not complete, we know that the games we tested ran at 1080p on Ultra settings. As a result, the RX 470 achieved 64 fps in Battlefield 4, 107 fps in DOOM, and 77 fps in Fallout 4. games other than the RX 470. Games are known to run at 1080p, but it is not known what detail and post-processing quality was set. RX 460 map scored 107 fps in Dota 2, 170 fps in CSGO, 109 in Overwatchfps, and in GTA V — 74 frames per second.
The RX 470 is expected to go on sale this month, but sales of the RX 460 are not yet known.
graphics cardsAMDRadeon RX 460470
comment on related news
Kit Guru
In its announcement at E3, AMD confirmed the specifications of the Polaris10 Ellesmere and Polaris1 Baffin graphics chips.
These graphics chips will be used in at least three desktop graphics cards: Radeon RX 480, RX 470 and RX 460. Two older solutions, RX 480 and RX 470, will be based on Ellesmere GPUs. This chip contains 2304 stream processors in 36 compute units. Also, these processors will work with 256-bit GDDR5 memory.
As for the Baffin processor, it will contain 1024 stream processors in 16 compute units. The RX 460 graphics card will work with 128-bit GDDR5 memory with an expected bandwidth of 128 GB/s.
AMDPolarisRadeon RX graphics cards 460470480
comment on related news
TechPowerUp
At E3, AMD CEO Lisa Su will feature a full line of Radeon RX graphics accelerators at Polaris.
The previously announced first solution in the lineup was the RX 480. At the time, the company said the card would be VR capable at a price of $199.
Now, the company has announced the preparation of the RX 470 and RX 460 graphics cards.
The first of them is called a power-efficient solution for gaming at 1080p, and the second is an excellent GPU for e-sports. Overall, the entire Radeon RX lineup will deliver superior graphics performance under $300 with 1080p 60fps rendering capability. The first of the cards in the lineup, the RX480, will be released on 29June. A release date for the RX 470 and RX 460 has yet to be announced, nor has AMD’s manufacturing partners or graphics card specs been named.
graphics cardsAMDRadeon RX 460470480
comment on related news
Kit Guru
TechPowerUp notes that AMD still has effective leverage to compete with NVIDIA.
In addition to dumping the price of the Radeon RX 480, the company can also play on the price of the junior solution of the series — Radeon RX 470. only 150 dollars. According to rumors, the accelerator will receive 2048 stream processors distributed in 32 computing units, which is slightly less than 2304 shaders in the RX 480.
Also, the younger solution will receive a slower memory with a speed of 7 Gb / s and a bandwidth of 224 Gb / s. The most spectacular figure in the specification of the accelerator will be its power consumption, which will be only 110 watts. So the RX 470 should be faster than the R9 380X, and given the specs, it should offer superior 1080p gaming performance for just $150.
AMDRadeon RX 470
market has released an update to its incredibly powerful and popular information and test utility AIDA64, which has received the number 6.75.
The company also began to release two new products under the similar AIDA64 Network Audit 6.75 brand. This utility consists of special tools for network auditing, collection and management of tools for corporate networks.
The new version of the utility received, basically, replenishment of its own database. Hardware support has also been improved and bugs fixed.The full list of changes in AIDA64 6.75 is below:
- Improved support for AMD Zen 4 processors and AM5 motherboards.
- Added GPU details for AMD Radeon RX 6650 XT, 6750 XT, 6950 XT.
- Added GPU details to Glenfly Arise.
- Added GPU details for NVIDIA GeForce RTX 4090 and GeForce GTX 1630.
- Fixed SMTP TLS 1.2 support.
The utility, as usual, is offered in four editions, which can be purchased on the developers’ website.
Download AIDA64 6.75 utility.
test APU graphics cardsAMDNVIDIARadeonAIDA64benchmarksutilities
comment on related news
TechPowerUp
Prices for graphics cards are rapidly declining, and given the performance of graphics cards, 3DCenter decided to conduct a study and understand how much they really cost.
At the beginning of 2021, video card manufacturers decided that it was worth raising the recommended cost, expecting that they would never be as cheap as before. But how expensive are these maps in reality? Considering the amount of data collected, the 3DCenter website conducted an analysis of the cost of accelerators.
The NVIDIA RTX 3070 video card was taken as the basis for the calculations, and considering the performance of the entire model range, it was concluded that most of the company’s accelerators are too expensive. High-end cards are especially overrated. And here is the best situation with the RTX 3060 Ti. This accelerator costs less than you might expect from it, given the performance. This is probably why this card is still hard to find in stores.
366% 61% 731 GeForce RTX 3080 12GB ? ~344% – 687 GeForce RTX 3080 10GB 699 330% 94% 659 GeForce RTX 3070 Ti 599 271% 90% 541 GeForce RTX 3070 499 250% 100% 499 GeForce RTX 3060 Ti 399 217% 109% 433 GeForce RTX 3060 329 165% 100% 329 For AMD and the Radeon RX 6000 series, the situation is even worse. 
The RX 6800 costs the most adequately, however, it is also overpriced, while the rest of the video cards are disproportionately expensive.
322% 99% 643 Radeon RX 6800 579 278% 96% 555 Radeon RX 6750 XT 549 234% 85% 467 Radeon RX 6700 XT 479 221% 92% 441 Radeon RX 6650 XT 399 167% 84% 333 Financial -Cardicard -Cardnvidia
Comment similar news
VideoCardz
AMD, AMD expanded its play video cards with the new Radeon RX 6700 model. As it is easy to guess, the product will reduce the performance of RX 6650 XT and RX 6700 XT.
The new graphics card has 10 GB of video memory, 36 compute units and 80 MB of Infinity Cache.
It allows you to output a picture with a resolution of 4K at 120 Hz or 8K at 60 Hz when connected via HDMI 2.1. Radeon RX 6700
Basically, the RX 6700 is a simplified version of the RX 6700 XT, with 10% fewer compute units (36 vs. 40), lower clock speed, narrower memory bus (160 vs. buffer. In general, this is a slower solution. The other side of the coin, in addition to the price, will be much lower power consumption, 175 W versus 230 W.
Clearly the card is built to provide superior gaming performance for those who can’t get enough of the RX 6650 XT and for whom the RX 6700 XT is too expensive. True, the price of the new card is still unknown. It is also unknown when and under what brands it will be produced. There are only rumors that the RX 6700 from Colorful will definitely be released.
GPUsAMDRadeon RX 6700
comment on related news
Overclock 3D
Frank Azor, chief gaming and marketing architect at AMD, posted an interesting infographic illustrating the company’s financial potential.
This slide shows all Radeon RX 6000 series graphics cards, including the RX 6×50 XT update. Each of these cards is pitted against a similarly priced NVIDIA RTX 30 series solution. This comparison includes all cards in the series, with the exception of the RTX 3090 Ti.
AMD vs. NVIDIA
Price and Performance Comparison According to AMD, the company’s best graphics card, the Radeon RX 6950 XT, offers 80% more performance per dollar than the GeForce RTX 3090 while consuming 15W less. As for the upper segment, RTX 3070-3080, here the performance is comparable to AMD solutions. The situation is changing in the middle and budget segment, where AMD products are again pulling ahead noticeably.
Considering how quickly the price of graphics cards changes these days, as well as the fact that the prices for comparison were taken from one online store (Newegg), at the time of publication the situation may have changed. Either way, this infographic provides a great insight into AMD’s marketing position and success.
financevideocardsAMDNVIDIA
comment on related news
Videocardz
According to early rumors, AMD is preparing the next generation of multi-chip graphics processors. At least, it concerned the upper part of the line. Fresh rumors are already talking about the number of chiplets in the GPU.
The RDNA 3 architecture promises more than the traditional performance increase compared to RDNA 2: additional gains can also be obtained due to the design of the GPU itself, which should become multi-chip, for the first time in the gaming world. This design should not only allow for easier scaling of solutions, but also reduce scrap and cost compared to traditional monolithic solutions.
AMD
GPU production technologies Insider @Greymon55 reported that the AMD Navi 31 GPU will be built using two 5nm GCD — Graphics Complex Dies and four Memory Complex Dies (MCD — Memory Complex Dies) , manufactured according to 6 nm standards), as well as one communication controller.
There are seven chiplets on a GPU die in total. At present, there is no official information about AMD’s planned manufacturing processes. It was only said that GPUs would be produced using “modern technologies”.
AMD is expected to release the first graphics cards based on the RDNA 3 architecture in the second half of 2022.
rumorsRDNA 3chipletsGPUNavi 31video cardsAMD
comment on related news
Overclock 3D
AMD’s Radeon RX 6000 graphics card lineup offers a fairly wide selection. The firm recently introduced the lower-end RX 6400 accelerator, but it turned out that there was still room for innovation.
Komachi Ensaka pointed to a previously unknown graphics card while demonstrating changes to the latest AMD GPU Performance API. AMD GPU Performance API 3.10 has been noted to support «additional GPUs and APUs, including AMD Radeon RX 6300, 6400, and 6500 GPUs» .
Radeon RX6400
Obviously, this will be the slowest card in the series. It will be based on the Navi 24 GPU with less than 768 active stream processors. This means that the chip will be manufactured using TSMC N6 technology and should use 16 MB of Infinity Cache. Since the RX 6400 uses 4GB of VRAM, expect the RX 6300 to only have 2GB of 64-bit GDDR6 memory. However, this is just an assumption.
Given the expected performance of this solution, expect the RX 6300 to be exclusive to OEM builders, but the possibility of a future retail market, as happened with the RX 6400, is not ruled out.
rumors KitGuru
AMD CEO Lisa Su has officially confirmed that next-generation Ryzen and Radeon products will be released this year.
The company is developing new CPU architectures, Zen 4, and GPUs, RDNA3, that will power Ryzen 7000 series CPUs and Radeon RX 7000 series graphics cards. production capacity.
This increase in production capacity will allow the company to successfully pass 2022. AMD CEO Lisa Su
Both product lines are scheduled to be released in late 2022, with limited impact on the company’s 2022 earnings. But even so, AMD expects to make $21.5 billion in profit, up 31% from 2021. This increase in profits also means a significant increase in deliveries, which was the likely reason for the additional booking of production from TSMC.
Along with Zen 4, AMD plans to release a new AM5 platform that will support PCIe 5.0 interface and DDR5 memory. As for the Zen 4 architecture itself, compared to the current Zen 3, it will receive big changes, which will significantly increase performance.
Zen 4RDNA 3Ryzen 7000Radeon RX 7000CPUvideo cardsAMD
Overclock 3D
Insider Greymon55 has published information about the timing of the release of new AMD products. This insider has already changed his nickname three times, so it is difficult to recognize him as a well-known informant.
Radeon RX 6500 XT
As for the entry-level graphics card, AMD hasn’t decided yet when it will release it. We are talking about the RX 6500 model, without the XT, and it will sell for under $130. This card will receive a Navi 24 GPU with 768 stream processors and 4 GB of GDDR6 video memory with a bus width of 64 bits. If these specs are correct, then the expected accelerator will be the first retail accelerator to feature the RDNA2 architecture and require no additional power.
Reporting on the Radeon RX 6X50XT, he notes that this updated series will appear in June or July. These graphics cards are expected to feature 18Gb/s GDDR6 memory, which is currently exclusive to the RX 6500XT/RX 6900XT models.
This means that the RX 6X50XT update will go on sale just a few months before the arrival of the RDNA3 architecture.
rumorsRadeon RX 6500videocardsAMDRadeon
comment on similar news
Videocardz
AMD’s latest low-end graphics cards are getting more negative feedback from consumers due to their poor performance and limitations associated with the PCIe configuration.
AMD’s decision to release entry-level mobile GPUs as desktop solutions had a terrible effect. Reviewers post bad reviews for the $200 RX 6500XT graphics card. And the reason is not only that it cannot be bought for this money or even cannot be found on sale.
The main reasons for dissatisfaction were low performance in ray tracing tasks, as well as limitations that arise when working on platforms with PCIe Gen3. Intel has just moved to PCIe Gen 4, so if you’re looking for a low-end graphics solution, you’re probably running a legacy or low-end PCIe 3.0 platform. Due to the fact that only 4 PCIe lanes are routed on the video card, the transition to the previous generation leads to a sharp drop in performance, which is more than 10%.
AMD Navi GPU
In addition, the Navi 24 GPU also lacks hardware video encoding and decoding capabilities. And this is also true for professional video cards based on it, including the PRO W6400, W6500M and W6300M models.
And it seems that the main reason for all this trouble lies in the fact that Navi 24 was not supposed to appear as a standalone solution.
It had to be paired with an AMD Rembrandt (Ryzen 6000) APU, which, of course, provides PCIe Gen4 support, and even the necessary hardware video encoding acceleration. This information was confirmed by one of AMD’s chief architects, John Bridgman. The Navi 24 GPU belongs to the lower segment. It consists of 5.4 billion transistors and covers an area of 107 mm2. It has 1024 stream processors, 64 texture units, 32 ROPs and 16 ray accelerators. RX 6500XT cards are already on sale, Radeon PRO W6400W are coming soon, and Navi 24 laptops should be available from February.
Radeon RX 6500 XTNavi 24videocardsAMD
1080
The TechPowerUp website has released a new version of its own popular GPU-Z utility designed to get all available information about your video card and monitor its parameters.
The new version of the GPU-Z utility, number 2.44, received changes regarding information about the Resizable BAR technology, and also added support for a huge number of video cards, both AMD and NVIDIA.
GPU-Z
The list of changes in GPU-Z 2.44.0 is as follows:
- Improved Resizable BAR detection.
- Resizable BAR is now reported in the advanced panel.
- GPU-Z will report «Vista 64» instead of «Vista64» as operating system.
- Screenshots are now loaded via https.
- Added vendor definition for Vastarmor.
- Fixed some GeForce RTX 3060 cards being labeled as LHR.
- Updated AMD Radeon RX 6600 release date.
- Added support for NVIDIA GeForce RTX 3050, RTX 3080 12 GB, RTX 3070 Ti Mobile, RTX 3050 Ti Mobile (GA106), RTX 2060 12 GB, GT 1010, MX550, GTX 1650 Mobile (TU117-B), RTX A2000 (GA106-B), RTX A4500, A10G, A100 80 GB PCIe, CMP170HX, CMP70HX.
- Added support for AMD Radeon RX 6400, RX 6500 XT, RX 6300M, RX 6500M, W6300M, W6500M, W6600M.
- Added support for non-K Intel Alder Lake processors, mobile Alder Lake, and Rocket Lake Xeon.
You can download the free GPU-Z utility from our website.
video cardsAMDNVIDIAGPU-Zutils
comment on related news
TechPowerUp
Rumors began to appear on the web that AMD may be preparing an interim update for RDNA2 video cards, the series of which will receive the Radeon 6RX5 XT series number.
According to user Wjm47196, who regularly reports insider information, AMD Radeon RX 6×50 XT graphics cards are indeed real. They will be based on Navi 21 (currently RX 6900XT and 6800) and Navi 22 (RX 6700XT) and will be released in Q2 2022. They will be on sale for one or two quarters, after which the RDNA3 generation of cards will be released.
AMD Radeon 6800 XT
graphics card The Navi 21/22 cores in the upgraded lineup are expected to be built at TSMC’s factories with updated 6nm technology, and they may also receive a memory upgrade. Early rumors said that instead of using 16Gb/s GDDR6 memory, the updated cards will get 18Gb/s memory.
The release of the Radeon RX 6×50 XT series appears to be a response to NVIDIA’s upgrade of accelerators and the release of RTX 3080 12GB, RTX 3090 Ti, and possibly RTX 3070 Ti with 16GB VRAM.
In addition, both manufacturers are trying to get the most out of their products in anticipation of the release of Arc Alchemist video accelerators from Intel. rumorsAMDRadeon
video cards comment on related news
KitGuru
AMD introduced the new Radeon PRO W6400 professional graphics card, which is based on the Navi 24 GPU.
This is the core processor that opens the range of modern AMD accelerators. Its TDP is only 50W, but this chip stands out as the world’s first 6nm solution for professionals. The Radeon PRO W6400 graphics card followed the similar desktop and gaming variant of the Radeon RX 6500 XT.
Radeon PRO W6400 graphics card
The announced graphics card is equipped with 768 stream processors, which is even less than the Radeon RX 6400, available only to OEM builders. The W6400 also received 4 GB of GDDR6 video memory with a 64-bit wide bus.
At the same time, the model has a full-size PCIe 4.
0 slot, from which only 4 lines are routed, which is also true for the RX 6500 XT. Therefore, when using these cards with motherboards with a PCIe 3.0 bus, there may be a lack of speed. Thus, the older PRO W6000X series graphics card is used exclusively in Apple Mac, while the «original» models based on three processors: W6800 with Navi 21, W6600 with Navi 23, and now W6400 with Navi 24 are sold at retail . It remains only to wait for one of the older models, based on Navi 22.
So far, nothing is known about the video capabilities of the Radeon PRO W6400 accelerator. The price of the card has not yet been announced.
video cardsAMDRadeon Pro
comment on related news
Videocardz
AMD is preparing to introduce its first graphics processor, which is manufactured using the new 6nm TSMC technology. And it was not the advanced processor of the new RX 7000 series, but a small chip for a budget series of accelerators.
This chip is called Navi 24. It is based on the RDNA2 architecture that is used in the entire RX 6000 series. The chip contains 1024 stream processors and 16 compute units (8 WGPs). It will be installed on the RX 6500 XT video card with 4 GB of video memory with a 64-bit bus. In addition, the GPU itself contains 16 MB of cache. This video card will have a full profile and occupy the classic two slots.
AMD Navi 24 GPU
In addition, the Navi 24 GPU will also be used in the entry-level RX 6400, which not only has a half-height profile, but also occupies a single slot.
Radeon RX 6500 XT video card Radeon 6400 video card
VideoCardz has published images of these video cards, and judging by the SMD elements near the PCIe interface, it can be argued that the video cards will use only 4 PCIe bus lines. However, given their low performance, this should be enough.
GPURadeon RX 6500 XT6400Navi 24video cardsAMD
comment related news
The company has confirmed that the card will get only 4 GB of GDDR6 video memory and only two video outputs, one HDMI 2.
1 and one DP 1.4. The video card supports 8K resolution at 60 fps, but in games it will behave more than modestly. The 6500 XT and RX 6400 are entry-level graphics cards suitable for 1080p esports gaming or home entertainment.
Lenovo
According to rumors, this video card will be based on the Navi 24 GPU, and 4 GB of video memory will be connected via a 64-bit bus. On paper, the memory subsystem looks very weak, and the use of Infinity Cache can further limit its capabilities.
In fact, despite the low performance, the card may become popular. In any case, it’s nice to see that manufacturers have begun to pay attention to the budget segment.
Radeon RX 6500 XTVIDVIDEOOKAMDLENOVO
Comment similar news
FUDZILLA
GPRO series from Sapphire can be found in workstations, but new models of these accelerators, GPRO X080 and X060, are intended for mining. The company claims that the older model will provide 38 MHz/s of Ethash algorithm performance at 165 watts.
The Sapphire GPRO X080 graphics card is based on the Navi 22 GPU with 2304 stream processors at 2132 MHz. The card has 10 GB of GDDR6 memory with a 160-bit bus and a bandwidth of 16 GB/s. The card works with PCIe 4.0×16 interface and is supported exclusively by Linux. The accelerator does not have a video output, so you won’t be able to play on it.
Sapphire GPRO X080 Mining Accelerator
As for the Sapphire GPRO X060, it is based on a stripped-down version of Navi 23 XL with 1792 stream processors at 2044 MHz. The board will receive 8 GB of GDDR6 memory with a 128-bit bus and a bandwidth of 14 Gb / s. The card has HDMI and DisplayPort video outputs.
Sapphire GPRO X060 Mining Accelerator
In terms of price, Sapphire GPRO X080 will be offered for 750 euros and GPRO X060 for 550 euros. The new accelerators will be shipped exclusively as part of large farms, so don’t count on the opportunity to purchase such a card for home mining.
miningvideocardsAMDSapphire
comment on related news
Video cards based on RDNA2 architecture will now cost $20-$40 more.
The new price will take effect from the next shipment of GPUs to production partners, that is, the effect of the rise in price will be noticeable in retail in a week or two after that, although suppliers and sellers can raise the price in advance. Radeon RX 6000
In fact, prices for AMD Radeon RX 6000 graphics cards have already increased by 9% in November compared to October. The next rise in prices is associated solely with the expectation of increased demand, traditional for the winter holidays.
It is noteworthy that according to the source, TSMC is not going to raise the price of pancakes with GPU. In addition, AMD does not raise the price of any other product made using the same 7nm technology, such as the Ryzen 5000 series processors, so AMD is solely responsible for the expected price flip.
MarketGPU video cardsAMDRadeon RX 6000
comment on related news0003
Micron now supplies its own graphics memory for the production of RX 6000 series graphics cards, which contain 16 GB GDDR6 modules for a total capacity of 16 GB.
This means that AMD has a new supplier of video memory. AMD RX 6000 series graphics cards
AMD RX 6600 and RX 6700 graphics cards equipped with Micron memory will be available for sale soon, which should help AMD produce more accelerators and increase their retail availability in Q4 2021.
GDDR6 video memory of AMDMicron
video cards its parameters.
The new version of the GPU-Z utility, number 2.43, received only 5 changes, which is not surprising, because only 4 days have passed since the last release. However, the application contains not only bug fixes, but also additions to the database.
GPU-Z
The list of changes in GPU-Z 2.43.0 is as follows:
- It is now possible to read the power consumption limits in NVIDIA Ampere cards for laptops in the Advanced -> NVIDIA BIOS menu.
- Fixed a crash on startup on some older Radeon cards.
- Fixed execution block counter for Intel Rocket Lake.
- Fixed crash function when taking a screenshot under Windows XP.
The bug first appeared in version 2.39. - Added support for NVIDIA Quadro RTX 3000 (TU106-B).
You can download the free GPU-Z utility from our website. September 27, 2021 The update was numbered 2.42.0.
In anticipation of the release of a new series of central processors, the release of a fresh version of the utility seems to be quite reasonable. As you might expect, it adds support for Intel Alder Lake-S CPU integrated graphics, as well as several new graphics cards from both NVIDIA and AMD.
GPU-Z 2.42.0
Changes in GPU-Z 2.42.0 are listed below:
- Added support for Intel Alder Lake and Tiger Lake Server.
- Added display for NVIDIA cards with reduced hashrate in the GPU name field, for example, «GA102 (LHR)».
- Added support for RTX 3060 variant based on GA104.
- Added support for detecting Resizable BAR technology in Radeon RX 5000 series cards.
- Added «-log» command line option that sets the name of the sensor log file and starts logging after the utility is run.
- Improved read stability of EVGA iCX sensors.
- Radeon HD 5000 Series cards will now display the ATI logo.
- Fixed an issue where DirectX 12 support was not displayed on AMD Navi 2x cards.
- Fixed a crash when taking a screenshot.
- Fixed crash in render test.
- Fixed a crash on some systems when reporting Resizable BAR.
- Fixed memory frequency reading on some AMD APUs.
- Added Intel Tiger Lake release date.
- Added support for NVIDIA RTX 3050 Ti Mobile (GA106), T1200 Mobile, GRID K340, GRID M30, Q12U-1.
- Added support for AMD Radeon Pro W6800X, Barco MXRT-8700.
- You can download the free GPU-Z utility from our website.
Tiger LakeGPUvideo cardsAMDIntelNVIDIAGPU-Zutilities
0001
In the second half of 2016, AMD pleased gamers with the release of a new video card — the Radeon RX 460, which appeared on the market after the RX 470 and RX 480 versions. This card is less productive, but very affordable in price, which allows even a schoolchild to save up for her, saving money from breakfast, and enjoy clear and smooth graphics during the game.
Let’s figure out what other advantages besides the cost the RX 460 has. AMD’s new video card differs from its predecessors by the Polaris 11 processor, which, with only 123 mm of usable area, is equipped with three billion transistors. This 14nm GPU can be compared to Bonaire, but it seems to be much faster. The table shows the main differences in the technical specifications of the latest three versions of Radeon RX video cards:
Let’s list the main differences of the new video card from AMD:
- lower die height, which was achieved by reducing the metal layers. With this feature, the Radeon RX 460 promises to be a great graphics adapter for laptops;
- Unlike the Polaris 10, the Polaris 11 features power-saving mechanisms (such as gating some areas of the GPU) that allow the card to run without additional power;
- card has a processing capacity of 2.2 TFLOPs at a base frequency of 1.090 MHz and a 1.200 MHz Boots frequency;
- card consumes less than 75 W of power, however, almost all manufacturers have added one more 6-pin connector to the package;
The
The
PowerColor version of the RX 460 Red Dragon does not have additional power supply
In Polaris 11, the number of shader units has been reduced from four (Polaris 10) to two, and now there are 7 active compute components in each of them, although Polaris 10 had 9.
The GPU has 64 stream processors and 4 texturing units each CU, that is, a total of 896 shaders and 56 texture units. The chip has two rendering backends, both shader units, each with four ROPs. This works out to 16 pixels per clock, which is half the number of pixels in the RX 480 and 470 models. Differences between models from different manufacturers
Asus
The company has pleased gamers with its new ROG Strix Radeon RX 460 OC. It differs from the reference characteristics declared by AMD in a higher pixel fill rate — 20.1 MP/s versus 19.2 MP/s. The cooling system is dual-slot, it includes a radiator and 2 fans. The card is not compatible with 32-bit OS.
Gigabyte
Gigabyte has released its version of the Radeon RX 460, a WindForce 2X OC graphics card with 2 GB of memory. It is based on Gigabyte’s own design PCB and comes with a 4+1 phase power subsystem, eliminating the need for additional power.
The cooling system consists of an aluminum radiator, blown by two 80mm fans.
Sapphire
Sapphire introduced two versions of the video card at once: Radeon RX 460 2GB and Nitro Radeon RX 460 4GB. The 2 GB card is equipped with a 3+1 power subsystem, as well as an aluminum heatsink and two fans, just like the model from Gigabyte.
The Sapphire Nitro Radeon RX 460 4GB version features a 4+1 phase power subsystem. In the cooling system, in addition to an aluminum radiator and two fans, there are 6 mm heat pipes passing through a copper base.
MSI
MSI AMD Radeon RX 460 is available in 2GB and 4GB memory options. The cooling system includes one radiator and one fan.
XFX
XFX released two variations of the card: Radeon RX 460 True OC and XFX Radeon RX 460 Double Dissipation. The cards are made in XFX corporate design, equipped with 3+1 power supply subsystems, one 6-pin connector. They differ only in the amount of memory and cooling systems.
The Radeon RX 460 True OC has 2 GB of memory, one fan, and an aluminum heatsink.
The Radeon RX 460 Double Dissipation has 4 GB of memory, two fans, a heat sink, two heat pipes with direct contact with the GPU. PowerColor
The PowerColor version is made to be as cheap as possible: one fan, plain plastic, no backplate. In principle, all this on this video card is not particularly necessary.
Summing up, it can be noted that the differences between models from different manufacturers are not cardinal. However, when purchasing a card with a large amount of memory, it is better to give preference to bundles with an additional power connector. Otherwise, the overclocking capabilities provided by the 4GB models will quickly run into power shortages when overclocking.
Comparison of 2 GB and 4 GB versions in games
Let’s compare two AMD Radeon RX 460 cards from HIS, which differ from each other in memory capacity: one card has 2 GB, and the second has 4 GB. Performance analysis is carried out using benchmarks of the most popular games today.
Dirt Rally
In the rally simulator Dirt Rally, the screen refresh rate of both cards was in the range of 45-50 FPS. Of course, the 2 GB card’s buffer filled up very quickly, while the 4 GB card’s buffer was only half used. But this did not affect the smoothness of the gameplay.
Far Cry Primal
In Far Cry Primal at the highest settings, both cards ran the game at 30 FPS. At the same time, a more capacious card slowed down, lagging behind the 2 GB model by several frames.
Rainbow Six Siege
But the Rainbow Six Siege benchmark immediately demonstrated the advantage of the 4 GB model. At high settings, it turned out to be more productive than the 2 GB model by an average of 20%. In some moments, the gap was 23 FPS! At lower settings, the cards behave the same, but the picture quality is not encouraging.
Rise of the Tomb Rider
In Rise of the Tomb Rider, the 2 GB card performed better again at very high display settings.
Hitman
Hitman «went» only at medium settings. Still, the game requires more powerful cards. In testing, the 4GB card came out ahead by 14% or 7 FPS. It also used less system resources compared to a 2 GB card.
Grand Theft Auto 5
When testing maps using the GTA 5 benchmark on high graphics settings, the maps also showed no noticeable differences in picture quality and gameplay smoothness. At the same time, the FPS indicator fluctuated between 55-60 FPS, which allows you to enjoy excellent graphics without any problems and not notice any slowdowns.
Summarizing the data obtained, we can conclude that both one and the other card are quite suitable for demanding toys. The advantage of a card with a large amount of memory becomes apparent when it is necessary to process large packets of information at once. If the data comes in small packets, then 2 GB of memory is enough even for games with careful graphic design and high definition images.
The 4 GB card proved superior in more demanding games and also took up less system memory resources. But, if the buyer does not plan to use the card at maximum settings and wants to save money, a 2 GB card will not disappoint him at all and will allow him to play the same games without losing picture smoothness.
What is the Radeon RX 460 suitable for? Although reviews on popular hardware sites often feature more expensive graphics adapters, with the RX 460 you can play League of Legends, as well as Overwatch and Dota 2 without any problems. The card easily allows you to get a Full HD picture and supports the DirectX 12 API and Vulkan.
With the release of the card, AMD focused primarily on eSports fans: the Radeon RX 460 allows you to run most online games even on the most modest computers. The card is much cheaper than more productive models from Nvidia, but the quality and smoothness of the picture are in no way inferior. Due to the limited power consumption, the video card does an excellent job of showing HD movies even on low-powered computers.
AMD Radeon RX 460 and RX 470 Preview
At a private show where I was allowed to look, AMD demonstrated two new budget segment video cards: AMD Radeon RX 470 and AMD Radeon RX 460. We can immediately say that they are not able to compete with the entire 1000th series from NVIDIA, and these video cards are created not for this. According to AMD, most users have a video card in the $100-$300 price segment. It’s hard to argue, but AMD’s emphasis on the low price category can be seen in the 400th line.
«Game technology should be accessible to everyone» -AMD
AMD Radeon RX 460
The RX 460 will ship with 2GB/4GB DDR5 memory. Power consumption below 75 watts is the positive side of the video card. The rest of the characteristics are not knocked out of the scope of good or bad. 128-bit memory bus, 2.2 TFLOPS — all within the framework of a budget video card. AMD positions the RX 460 as a gaming graphics card for popular multiplayer games.
What for then the version on 4 GB? Not a single card justified its increase in memory, the RX 460 is unlikely to be a discovery in this regard: (example of the GeForce GTX 9 review60 2 and 4 GB).Specifications AMD Radeon RX 460
As a solution for undemanding games, the RX 460 will find its niche for several reasons. Firstly, the RX 460 will be the most affordable gaming card for 2016-2017, and secondly, it can handle most popular games.
1080p90+ frames at high settings
AAA games
Judging by the frame rate in multiplayer games, the RX 460 performance will be slightly behind the GTX 950. Obviously, the RX 460 is more powerful than the GPU installed in the current generation consoles (where AAA titles run at 720p-1080p30fps), but inferior to all gaming solutions, even the 900th series from NVIDIA. Therefore, at medium quality settings in most games that have already been released, you can get at least 30+ frames.
You can independently place it in your rating of video cards.+20% against R9(R7?) 260X
Now ask yourself this question, do you need a budget October 2013 graphics card with a 20% performance boost? The budget graphics card will show a slight boost in modern games compared to the 2013 AMD graphics card. If you don’t face such a sharp financial issue, but want to get a significant increase with an AMD card, then we advise you to take a closer look at the older RX 470 or even 480 model (AMD Radeon RX 480 review).
AMD Radeon RX 470
«Brilliant HD Gaming» is the slogan under which AMD introduced the second novelty RX 470. Here you already have a 256-bit memory bus, and 4GB DDR5, and almost 5 TFLOPS, and the bandwidth is twice as high as that of the RX 460 — all this with modest 120 watts. Before us is a real gaming video card with good characteristics.
The RX 470 promises to pull all released AAA projects at 1080p and 60+ frames.
Let’s try to figure it out, shall we? We already have information about the RX 480, which literally walks on the edge of the desired «60 + FPS», sometimes not getting it in the same games from Ubisoft: HITMAN (2016), Far Cry Primal, The Division, etc. If you look for tests on the Internet, it turns out that there are quite a lot of such games. I remind you that the RX 480 video card is older and more powerful than the RX 470, so you should not fully believe in it.Smooth lay…
Now we will try to understand how it will fit into the market. RX 470, again in my opinion, will take place between the GTX 960 and GTX 970. Why can’t the RX 470 be more powerful than the GTX 970, because its older version RX 480 is already somewhere inferior to the GTX 970. Why can’t it be weaker than the GTX 960 because it greatly outperforms the R9 380, which is similar in performance to the GTX 960 in many ways.
Comparison with R9 270.
The total number of frames is very pleasing. Is it like that? We are again shown a comparison with the previous generation video card, which was released almost 3 years ago. The superiority here is twofold, but is such a comparison objective? The first reviews of the RX 470 will show if the game is worth the candle. If the RX 470 manages to match the performance of the GTX 970, it will be a big breakthrough for AMD, but it will still be a generation behind, and we will have competition and price cuts. If the RX 470 stays closer to the GTX 960, NVIDIA’s dominance will remain both on the facts and on the price tag.
Technology
API Vulkan
A new API created with the participation of AMD themselves. They promise an increase in productivity of 20% -30%. On the one hand, it’s good, on the other hand, the API is currently implemented in several games, and the number of such games will not grow much.
History with the Mantle API repeats itself.
Radeon Wattman
AMD software for adjusting fan speed, temperature, load, and even overclocking.HEVC
Support for a new codec for video compression. HEVC algorithms will reduce data transfer by up to 50%. This will allow you to transmit higher quality video materials at the same bitrate.Total
RX 460
The cost of the RX 460 according to various sources is $100/$120 for the 2GB/4GB version. Considering the exchange rate, it is a pity to give even $100 for such a card, and it will be more expensive on the shelves in Russia. Still, it would be unfair not to say that the RX 460 will find its buyer. We have the lowest cost and satisfactory performance in popular online games.
RX 470
The RX 470 is priced at $150, which is a small amount.
In terms of performance, there is no diamond here, but the video card can be a good choice between budget and top-end solutions. The RX 470 has everything you need to play modern games at the right level at an affordable price.AMD RX 550, RX 560, and RX 570
On April 18, AMD announced that its mid-range RX 4xx series GPUs will be updated. We recently talked about the RX 580, but in addition to it, AMD will also release improved versions of the RX 460 and RX 470, as well as a completely new card — the RX 550. In this article, we will try to consider what new AMD has added to its video cards, and also try to understand how this will affect gamers who buy mid-range GPUs.
RX 560 and RX 570
Both cards are updated versions of the RX 460 and RX 470 that AMD released about a year ago. Anandtech and Hot Hardware have already published their reviews of the RX 570, and their numbers show roughly the same pattern as for the RX 580: performance is increased by about 12%, GPUs are quieter (due to improved cooling), and they run much less often.
throttling is observed (from «throttling»; this is a protective feature that limits access to the maximum level of performance while software that uses 3D is running). But the unpleasant moment is that these video cards began to require more power. However, the Anandtech review shows that the RX 570 is better than the RX 580 — the gap in gluttony between the old RX 470 and the new RX 570 is 10% less than between the RX 480 and RX 580. Since the frequency of the RX 570 is less than on the RX 580, this confirms our theory that Polaris has almost exhausted its overclocking reserves. We don’t know how much is left, but we are sure that as performance increases, these chips will require more and more power. In terms of price, the RX 570 sits between the upper end of the GTX 1050 Ti price range and the lower end of the 3GB GTX 1060. And if the 1050 Ti can be retired after the introduction of the RX 570, then nothing definite can be said about the GTX 1060 3GB not yet possible.
The Eurogamer results show that the AMD card wins in some tests and not in others. As for the RX 560, it differs slightly from its predecessor, namely the number of stream processors and a higher frequency. 9dollars.
RX 550 aka Polaris 12
Finally, AMD has released a brand new card — the RX 550 — aimed at the sub-$100 market. AMD and NVIDIA have been ignoring this niche for several years now. most people buying hardware in this price range use integrated graphics cards. AMD cards in this price range were based on Cape Verde (GCN 1.0) or Oland (GCN 1.x is a variant between GCN 1.0 and 1.1 with some, but not all, Hawaii features).
There is very little information about the RX 550. We know that it is based on a new GPU called Polaris 12, has 512 cores, 2 GB of VRAM and a turbo frequency of 1175 MHz. The memory bus is still 128-bit, and the number of texture units is reportedly 32.
The decisive factor in the performance of the RX 550 seems to be the number of raster operations units (ROPs).
The R7 250X was significantly faster than the R7 250 precisely because it was equipped with 640:40:16, while its brother had 384:24:8. If AMD equips the RX 550 with sixteen ROPs, then the R7 250X will be left to swallow dust. But if AMD is limited to only eight ROPs, the prospect of pushing the R7 250X becomes rather vague. Either way, the RX 550 will be faster than the R7 250 anyway. low-profile version, which can be useful for system units with the SFF form factor and in other situations where compactness is important for a video card. It is also clear that this GPU will compete in the notebook market, where low power consumption is almost always in demand.
In conclusion
AMD doesn’t offer anything particularly new with this update, but both the RX 560 and RX 570 cards should be much faster than their predecessors, which should strengthen the company’s position in its eternal confrontation with NVIDIA.
As for the RX 550, it is unlikely to become a golden antelope for AMD.
- Improved support for AMD Zen 4 processors and AM5 motherboards.