Quadro RTX 4000 vs RTX 2080 Ti — Windows Hardware
McNeel Forum
felixrothermel0
(Felixrothermel0)
#1
So,
I have been using the RTX 4000 for a few months and also got an RTX 2080 Ti for my new PC. However, the 2080 Ti arrived early, so I tested both in the old PC and here are the results from Holomark.
Quadro:
Holomark 2 R6 v2,61
Total Score: 232556
Total Runtime: 1054.67 sec
GPU scores: 217460
GPU_01 — 533.30 fps — Cube 4 tests
GPU_02 — 56.20 fps — UDT Shape
GPU_03 — 625.00 fps — Wireframe
GPU_04 — 526.30 fps — Shaded
GPU_05 — 109.90 fps — Rendered
GPU_06 — 91.70 fps — Block Rendered
GPU_07 — 939 units Nurbs @ 5 fps in Wireframe
GPU_08 — 343 units Nurbs @ 5 fps in Shaded
GPU_09 — 64 units Nurbs @ 5 fps in RenderSpeed
GPU_10 — 204. 10 fps — RenderMesh Render
GPU_11 — 588.20 fps — RenderMesh RenderSpeed
GPU_12 — 500.00 fps — JoinedMesh Render
GPU_13 — 909.10 fps — JoinedMesh RenderSpeed
GPU_14 — 138 units mesh @ 15 fps in Shaded
GPU_15 — 402 units mesh @ 15 fps in Render
GPU_16 — 978 units mesh @ 15 fps in RenderSpeed
GPU_17 — 238.10 fps — mesh in Rendered Studio
GPU_18 — 30.60 fps — Nurbs in Rendered Studio
GPU_19 — 588.20 fps — Block Illustration
GPU_20 — 156.00 fps — 2D single
GPU_21 — 94.30 fps — 2D massive (20x)
CPU scores: 15096
CPU_01 — 8.89 sec — Booleans and Contours
CPU_02 — 2.77 sec — Twist and Taper (UDT)
CPU_03 — 4.96 sec — Meshing Mini
CPU_04 — 0.03 sec — Extract Render Mesh
CPU_05 — 0.03 sec — Join Render Mesh
CPU_06 — 12.03 sec — Reduce Mesh
CPU_07 — 0.58 sec — Calculating Technical display
CPU_08 — 3.
83 sec — Making Silhouettes
System manufacturer
System Product Name
NVIDIA Quadro RTX 4000 — 4095.0 MB
DriverVersion: 26.21.14.4292
Intel® Core™ i7-3930K CPU @ 3.20GHz
NumberOfCores: 6 NumberOfLogicalProcessors: 12
MaxClockSpeed: 3.2 GHz
TotalPhysicalMemory: 32.0 GB
Microsoft Windows 10 Pro
- None — 64-bit
Rhino 6 sr 25 64 bit
AA level = 8
2080 Ti:
Holomark 2 R6 v2,61
Total Score: 268237
Total Runtime: 1427.1 sec
GPU scores: 255980
GPU_01 — 625.40 fps — Cube 4 tests
GPU_02 — 58.10 fps — UDT Shape
GPU_03 — 909.10 fps — Wireframe
GPU_04 — 625.00 fps — Shaded
GPU_05 — 119.00 fps — Rendered
GPU_06 — 99.00 fps — Block Rendered
GPU_07 — 1106 units Nurbs @ 5 fps in Wireframe
GPU_08 — 336 units Nurbs @ 5 fps in Shaded
GPU_09 — 56 units Nurbs @ 5 fps in RenderSpeed
GPU_10 — 238.10 fps — RenderMesh Render
GPU_11 — 588.
20 fps — RenderMesh RenderSpeed
GPU_12 — 588.20 fps — JoinedMesh Render
GPU_13 — 1111.10 fps — JoinedMesh RenderSpeed
GPU_14 — 197 units mesh @ 15 fps in Shaded
GPU_15 — 519 units mesh @ 15 fps in Render
GPU_16 — 2079 units mesh @ 15 fps in RenderSpeed
GPU_17 — 263.20 fps — mesh in Rendered Studio
GPU_18 — 28.40 fps — Nurbs in Rendered Studio
GPU_19 — 35.20 fps — Block Illustration
GPU_20 — 158.50 fps — 2D single
GPU_21 — 77.50 fps — 2D massive (20x)
CPU scores: 12257
CPU_01 — 8.70 sec — Booleans and Contours
CPU_02 — 2.16 sec — Twist and Taper (UDT)
CPU_03 — 13.14 sec — Meshing Mini
CPU_04 — 0.03 sec — Extract Render Mesh
CPU_05 — 0.03 sec — Join Render Mesh
CPU_06 — 11.92 sec — Reduce Mesh
CPU_07 — 0.98 sec — Calculating Technical display
CPU_08 — 3.83 sec — Making Silhouettes
System manufacturer
System Product Name
NVIDIA GeForce RTX 2080 Ti — 4095.
0 MB
DriverVersion: 26.21.14.4292
Intel® Core™ i7-3930K CPU @ 3.20GHz
NumberOfCores: 6 NumberOfLogicalProcessors: 12
MaxClockSpeed: 3.2 GHz
TotalPhysicalMemory: 32.0 GB
Microsoft Windows 10 Pro
- None — 64-bit
Rhino 6 sr 26 64 bit
AA level = 8
According to Holomark, the RTX 2080 Ti is better by some way, and even double up in some areas. What was strange is that the Quadro RTX 4000 performed slightly better with a Studio Driver — over a Quadro driver.
Anyway, I saw and read a lot about these two cards on here and thought Id chip in as I had a good benchmark platform.
Best
F
4 Likes
Stratosfear
#2
I have no idea why this is surprising? The 2080 ti has almost double the Cuda cores and Vram.
Why do people keep buying these massively overpriced and under speced Quadros?
3 Likes
felixrothermel0
(Felixrothermel0)
#3
It’s not, it’s just that people keep asking about it and I found myself in a position to weigh the two separately on the same system.
Personally I think it would be interesting to test the quadro 5000 against the 2080 ti.
I agree though, the quadros are stupidly over-priced. With the latest Nvidia Studio Drivers, the GeForce Cards are far superior in price for performance.
1 Like
MattE
#4
Two quick questions:
Are the two sets of test results you’ve posted supposed to be identical?
How does the size and power consumption of the two cards compare? I’m looking to upgrade and the Quadro RTX 4000 is top of my list because my PC case is small and a single slot, relatively low power GPU fits the bill nicely.
I grew tired of graphics cards that wail like a banshee when they are under load several years ago. I’m not going back there
JimCarruthers
#5
Unless you’re running some other software that “needs” a Quadro, don’t bother with it unless you get the absolute top-of-the-line. Paying an insane amount of money for a minuscule performance benefit over the top GTX is…well at least something, instead of paying more than a top-shelf GTX for less performance.
1 Like
felixrothermel0
(Felixrothermel0)
#6
hi,
Sorry about that, dumb mistake, its been editted now.
The Quadro is 160W and the 2080 Ti is 260W.
I think the quadro is a decent card and I’ve enjoyed it, but the 2080 Ti blows it out of the water. That goes for Lumion, Twinmotion and Enscape as well, where the bechmarks of the Ti beat out even the Quadro 5000 by quite some margin.
I use Twinmotion a lot and I can tell you that performance difference is very noticealbe. It is louder than the than the Quadro, but i dont mind it at all.
MattE
#7
I spend almost all of my time on 2D and 3D CAD in Rhino, with infrequent sessions of ‘rendering’ or visualisation. That is probably why I’m still using a Quadro K4000, which has served me (very) well over the years. However, the promise that Cycles is showing within Rhino has made me start to look at render-capable GPU.
The past 5 years of hardware development has seen my needs not only met, but probably surpassed. I no longer require bleeding-edge technology. That is why the RTX 4000 seems a good fit. Using the same Turing chip, what would be the equivalent mainstream graphics card?
Holo
#8
It has 2304 cuda cores, the same as a RTX 2070, but a slim design, so probably at the same speed as an RTX 2060.
Theoretically a big upgrade from the k4000:
https://gpu.userbenchmark.com/Compare/Nvidia-Quadro-RTX-4000-vs-Nvidia-Quadro-K4000/m716215vsm7730
1 Like
Stratosfear
#9
Any graphics card with a blower cooler is a hard pass for me.
They don’t cool anywhere near as well as a dual or triple fan cooler. They’re incredibly load by comparison also. I’d recommend the RTX 2070 super or a used 1080 ti. The RTX 3000 series cards are out in Sept. I’d keep that in mind as well.
2 Likes
felixrothermel0
(Felixrothermel0)
#10
If you have a small system, a blower is your best bet. The fan ones work better in a bigger system with lots of air flow. The quadro RTX 4000 is an amazing card and the Turing chips are cherry picked for performance; it’ll be like coming out of the dark from the K4000! It’s the same swap I made. I just prefer the 2080 ti for complex rendering in twinmotion.
If your based in the UK let me know and we can make a deal for mine? It’s two months old.
TomTom
(Tom)
#11
To be honest with you, I never understood these performance comparison threads. The thing with performance is, that
a.) the card doesn‘t matter at all, because the situations requires much less performance.
Or b.) The card doesn‘t really matter, because the performance lack is too big anyway.
To be within the performance range, where it matters is a very rare case. For high performance rendering, nowadays you can make use of cloud or local cloud computing, which outperforms any card by far.
What rather should be discussed is the advantage of Quadros compared to Geforce cards regarding anything else then performance, such as warranty,(hardware) reliability or official CAD support. Many CAD software, as already mentioned, optimize for a specific card and driver version, assuring that it reliable works.
felixrothermel0
(Felixrothermel0)
#12
The card performance matters a lot, especially if you’re doing anything that requires GPU rendering. I.e. rhino raytracing, vray, maxwell, twinmotion, lumion, enscape, etc…
Yes cloud rendering can be faster, but it also costs money and some of them base the price off your GPU/CPU speed anyway.
TomTom
(Tom)
#13
You know people say this for a decade now, but renderings did not become better by any means. Still people believe to have the latest stuff to save 10 minutes for their rendering.
But the funny thing is, then they add another set of polygons to their szene and still require the same time for rendering it. Its super realistic, but still images lack quality. This may becomes philosophical, but I personally rather disagree.
Edit: Of course I‘m not saying take an Onboard card. But its about these 5 to 15% deltas, which also depend on so many other factors. Driver, Application, Szene Characteristics, Degree of (szene) optimisation. Amount of post processing, Type of Shaders, Amount of Light Sources, Type of Rendering, Resolution …
felixrothermel0
(Felixrothermel0)
#14
i can see the argument you’re making when it comes to creating ever more complex geometries and rendering them. However, if you’re just trying to render a piece of wood in maxwell render (for example) with a Quadro 4000 to SL 17 itll take 5 hours as opposed to 20 mins with the RTX 4000 on GPU render.
MattE
#15
As it happens, I replaced the stock cooler on the K4000 with an after-market one by Scythe, which has two very low profile 100mm fans. It works very well and got rid of the whine of the stock cooler and the constant spooling up and down. I’d definitely consider doing something similar to the new card, whichever one I end up with. There’s just about enough room in my itx case, which has a lot of perforations next the to the GPU slot.
I didn’t know about an upcoming RTX 3000. Thanks for the tip-off. I want to get a card with four monitor outputs, which the RTX 4000 has.
MattE
#16
btw — what’s with the ‘Meshing Mini’ times in those stats? Seems a bit odd.
Does the GPU help out in some way, or is it likely just a glitch?
Stratosfear
#17
I put a morpheus cooler on my Titan xp with noctua nfa fans. I use msi afterburner to control the fans. I keep an eye on loads and temps with rainmeter desktop apps. It was absolutely worth the cost, time and effort.
felixrothermel0
(Felixrothermel0)
#18
Haha… Must be a glitch… my system is a decade old now!
MattE
#19
It seems strange that for the CPU stats, the RTX 4000 soundly beats the 2080Ti in both the Meshing Mini and Calculating Technical Display scores, while for the others the reutls are all but identical.
Irrespective of whether or not your system is getting old (mine is too, as indeed am I ), it would be nice to know if the difference can be attributed to the GPU.
felixrothermel0
(Felixrothermel0)
#20
Hi Matt,
Not sure what you mean old bean? Theres a 20,000 point difference in GPU scores. I think the CPU scores should be read independently of the GPU scores as they only test the i7 6 core processor and RAM. The glitches there are likely to do with the fact that my old CPU and RAM can be a bit tempermental.
Holomark can correct me if i am wrong, but I think the first test is on soley on the GPU and the second is solely on the CPU.
So, either there my CPU is glitchy, or there is roughly a 3000 point margin of error in holomark’s benchmark.
Best,
F
next page →
GeForce RTX 2080 Ti vs Quadro RTX 4000 mobile Graphics cards Comparison
Find out if it is worth upgrading your current GPU setup by comparing GeForce RTX 2080 Ti and Quadro RTX 4000 mobile. Here you can take a closer look at graphics cards specs, such as core clock speed, memory type and size, display connectors, etc. The price, overall benchmark and gaming performances are usually defining factors when it comes to choosing between GeForce RTX 2080 Ti and Quadro RTX 4000 mobile. Make sure that the graphics card has compatible dimensions and will properly fit in your new or current computer case. Also these graphics cards may have different system power recommendations, so take that into consideration and upgrade your PSU if necessary.
GeForce RTX 2080 Ti
Check Price
Quadro RTX 4000 mobile
Check Price
Quadro RTX 4000 mobile is a Laptop Graphics Card
Note: Quadro RTX 4000 mobile is only used in laptop graphics.
It has lower GPU clock speed compared to the desktop variant, which results in lower power consumption, but also 10-30% lower gaming performance. Check available laptop models with Quadro RTX 4000 mobile here:
Quadro RTX 4000 mobile Laptops
Main Specs
| GeForce RTX 2080 Ti | Quadro RTX 4000 mobile | |
| Power consumption (TDP) | 250 Watt | 110 Watt |
| Interface | PCIe 3.0 x16 | PCIe 3.0 x16 |
| Supplementary power connectors | 2x 8-pin | |
| Memory type | GDDR6 | GDDR6 |
| Maximum RAM amount | 11 GB | 8 GB |
| Display Connectors | 1x HDMI, 3x DisplayPort, 1x USB Type-C | No outputs |
|
Check Price |
Check Price |
- GeForce RTX 2080 Ti has 127% more power consumption, than Quadro RTX 4000 mobile.
- Both video cards are using PCIe 3.0 x16 interface connection to a motherboard.
- GeForce RTX 2080 Ti has 3 GB more memory, than Quadro RTX 4000 mobile.
- GeForce RTX 2080 Ti is used in Desktops, and Quadro RTX 4000 mobile — in Mobile workstations.
- GeForce RTX 2080 Ti and Quadro RTX 4000 mobile are build with Turing architecture.
- Core clock speed of GeForce RTX 2080 Ti is 240 MHz higher, than Quadro RTX 4000 mobile.
- GeForce RTX 2080 Ti and Quadro RTX 4000 mobile are manufactured by 12 nm process technology.
- Memory clock speed of GeForce RTX 2080 Ti and Quadro RTX 4000 mobile is 14000 MHz.
Game benchmarks
| Assassin’s Creed OdysseyBattlefield 5Call of Duty: WarzoneCounter-Strike: Global OffensiveCyberpunk 2077Dota 2Far Cry 5FortniteForza Horizon 4Grand Theft Auto VMetro ExodusMinecraftPLAYERUNKNOWN’S BATTLEGROUNDSRed Dead Redemption 2The Witcher 3: Wild HuntWorld of Tanks | ||
| high / 1080p | 90−95 | 60−65 |
| ultra / 1080p | 70−75 | 45−50 |
| QHD / 1440p | 55−60 | 35−40 |
| 4K / 2160p | 40−45 | 21−24 |
| low / 720p | 100−110 | 90−95 |
| medium / 1080p | 100−110 | 75−80 |
The average gaming FPS of GeForce RTX 2080 Ti in Assassin’s Creed Odyssey is 41% more, than Quadro RTX 4000 mobile. |
||
| high / 1080p | 140−150 | 100−105 |
| ultra / 1080p | 130−140 | 90−95 |
| QHD / 1440p | 100−110 | 70−75 |
| 4K / 2160p | 70−75 | 35−40 |
| low / 720p | 160−170 | 150−160 |
| medium / 1080p | 150−160 | 110−120 |
| The average gaming FPS of GeForce RTX 2080 Ti in Battlefield 5 is 35% more, than Quadro RTX 4000 mobile. | ||
| low / 768p | 45−50 | 45−50 |
GeForce RTX 2080 Ti and Quadro RTX 4000 mobile have the same average FPS in Call of Duty: Warzone. |
||
| low / 768p | 250−260 | 250−260 |
| medium / 768p | 230−240 | 230−240 |
| QHD / 1440p | 150−160 | 150−160 |
| 4K / 2160p | 100−110 | 100−110 |
| high / 768p | 220−230 | 220−230 |
| GeForce RTX 2080 Ti and Quadro RTX 4000 mobile have the same average FPS in Counter-Strike: Global Offensive. | ||
| low / 768p | 70−75 | 70−75 |
| medium / 1080p | 50−55 | 50−55 |
| GeForce RTX 2080 Ti and Quadro RTX 4000 mobile have the same average FPS in Cyberpunk 2077. |
||
| low / 768p | 120−130 | 120−130 |
| medium / 768p | 110−120 | 110−120 |
| ultra / 1080p | − | 110−120 |
| GeForce RTX 2080 Ti and Quadro RTX 4000 mobile have the same average FPS in Dota 2. | ||
| high / 1080p | 110−120 | 80−85 |
| ultra / 1080p | 100−110 | 75−80 |
| QHD / 1440p | 100−105 | 55−60 |
| 4K / 2160p | 55−60 | 30−35 |
| low / 720p | 130−140 | 110−120 |
| medium / 1080p | 120−130 | 85−90 |
The average gaming FPS of GeForce RTX 2080 Ti in Far Cry 5 is 41% more, than Quadro RTX 4000 mobile. |
||
| high / 1080p | 170−180 | 120−130 |
| ultra / 1080p | 150−160 | 95−100 |
| QHD / 1440p | 110−120 | 65−70 |
| 4K / 2160p | 21−24 | 21−24 |
| low / 720p | 270−280 | 250−260 |
| medium / 1080p | 210−220 | 170−180 |
| The average gaming FPS of GeForce RTX 2080 Ti in Fortnite is 29% more, than Quadro RTX 4000 mobile. | ||
| high / 1080p | 150−160 | 110−120 |
| ultra / 1080p | 130−140 | 85−90 |
| QHD / 1440p | 110−120 | 65−70 |
| 4K / 2160p | 80−85 | 45−50 |
| low / 720p | 170−180 | 150−160 |
| medium / 1080p | 150−160 | 110−120 |
| The average gaming FPS of GeForce RTX 2080 Ti in Forza Horizon 4 is 40% more, than Quadro RTX 4000 mobile. |
||
| low / 768p | 170−180 | 170−180 |
| medium / 768p | 160−170 | 160−170 |
| high / 1080p | 150−160 | 120−130 |
| ultra / 1080p | 100−105 | 65−70 |
| QHD / 1440p | 90−95 | 55−60 |
| The average gaming FPS of GeForce RTX 2080 Ti in Grand Theft Auto V is 16% more, than Quadro RTX 4000 mobile. | ||
| high / 1080p | 90−95 | 50−55 |
| ultra / 1080p | 75−80 | 40−45 |
| QHD / 1440p | 60−65 | 30−35 |
| 4K / 2160p | 40−45 | 21−24 |
| low / 720p | 150−160 | 110−120 |
| medium / 1080p | 110−120 | 70−75 |
| The average gaming FPS of GeForce RTX 2080 Ti in Metro Exodus is 60% more, than Quadro RTX 4000 mobile. |
||
| low / 768p | 120−130 | 120−130 |
| GeForce RTX 2080 Ti and Quadro RTX 4000 mobile have the same average FPS in Minecraft. | ||
| high / 1080p | 160−170 | 110−120 |
| ultra / 1080p | 140−150 | 80−85 |
| 4K / 2160p | 18−20 | 18−20 |
| low / 720p | 190−200 | 140−150 |
| medium / 1080p | 180−190 | 120−130 |
| The average gaming FPS of GeForce RTX 2080 Ti in PLAYERUNKNOWN’S BATTLEGROUNDS is 45% more, than Quadro RTX 4000 mobile. | ||
| high / 1080p | 90−95 | 50−55 |
| ultra / 1080p | 55−60 | 30−35 |
| QHD / 1440p | 45−50 | 24−27 |
| 4K / 2160p | 30−35 | 16−18 |
| low / 720p | 150−160 | 110−120 |
| medium / 1080p | 120−130 | 75−80 |
The average gaming FPS of GeForce RTX 2080 Ti in Red Dead Redemption 2 is 60% more, than Quadro RTX 4000 mobile. |
||
| low / 768p | 300−350 | 240−250 |
| medium / 768p | 260−270 | 160−170 |
| high / 1080p | 180−190 | 100−105 |
| ultra / 1080p | 100−110 | 55−60 |
| 4K / 2160p | 70−75 | 35−40 |
| The average gaming FPS of GeForce RTX 2080 Ti in The Witcher 3: Wild Hunt is 57% more, than Quadro RTX 4000 mobile. | ||
| low / 768p | 650−700 | 170−180 |
| ultra / 1080p | 300−350 | 85−90 |
The average gaming FPS of GeForce RTX 2080 Ti in World of Tanks is 281% more, than Quadro RTX 4000 mobile. |
||
Full Specs
| GeForce RTX 2080 Ti | Quadro RTX 4000 mobile | |
| Architecture | Turing | Turing |
| Code name | Turing TU102 | N19E-Q3 |
| Type | Desktop | Mobile workstation |
| Release date | 27 August 2018 | 27 May 2019 |
| Pipelines | 4352 | 2560 |
| Core clock speed | 1350 MHz | 1110 MHz |
| Boost Clock | 1545 MHz | 1560 MHz |
| Transistor count | 18,600 million | 13,600 million |
| Manufacturing process technology | 12 nm | 12 nm |
| Texture fill rate | 420. 2 |
249.6 |
| Length | 267 mm | |
| Memory bus width | 352 Bit | 256 Bit |
| Memory clock speed | 14000 MHz | 14000 MHz |
| Memory bandwidth | 616.0 GB/s | 448.0 GB/s |
| Shared memory | — | — |
| G-SYNC support | + | + |
| VR Ready | + | + |
| DirectX | 12 Ultimate (12_1) | 12 Ultimate (12_1) |
| Shader Model | 6.5 | 6.5 |
| OpenGL | 4.6 | 4.6 |
| OpenCL | 2.0 | 1.2 |
| Vulkan | 1.2.131 | 1. 2.131 |
| CUDA | 7.5 | 7.5 |
| Laptop size | large | |
|
Check Price |
Check Price |
Similar compares
- GeForce RTX 2080 Ti vs GeForce RTX 3080
- GeForce RTX 2080 Ti vs GeForce RTX 3070
- Quadro RTX 4000 mobile vs GeForce RTX 3080
- Quadro RTX 4000 mobile vs GeForce RTX 3070
GeForce RTX 2080 vs Quadro RTX 4000 Graphics cards Comparison
Find out if it is worth upgrading your current GPU setup by comparing GeForce RTX 2080 and Quadro RTX 4000.
Here you can take a closer look at graphics cards specs, such as core clock speed, memory type and size, display connectors, etc. The price, overall benchmark and gaming performances are usually defining factors when it comes to choosing between GeForce RTX 2080 and Quadro RTX 4000. Make sure that the graphics card has compatible dimensions and will properly fit in your new or current computer case. Also these graphics cards may have different system power recommendations, so take that into consideration and upgrade your PSU if necessary.
GeForce RTX 2080
Check Price
Quadro RTX 4000
Check Price
Main Specs
| GeForce RTX 2080 | Quadro RTX 4000 | |
| Power consumption (TDP) | 215 Watt | 160 Watt |
| Interface | PCIe 3. 0 x16 |
PCIe 3.0 x16 |
| Supplementary power connectors | 1x 6-pin + 1x 8-pin | 1x 8-pin |
| Memory type | GDDR6 | GDDR6 |
| Maximum RAM amount | 8 GB | 8 GB |
| Display Connectors | 1x HDMI, 3x DisplayPort, 1x USB Type-C | 3x DisplayPort, 1x USB Type-C |
|
Check Price |
Check Price |
- GeForce RTX 2080 has 34% more power consumption, than Quadro RTX 4000.
- Both video cards are using PCIe 3.0 x16 interface connection to a motherboard.
- GeForce RTX 2080 and Quadro RTX 4000 have maximum RAM of 8 GB.
- Both cards are used in Desktops.
- GeForce RTX 2080 and Quadro RTX 4000 are build with Turing architecture.
- Core clock speed of GeForce RTX 2080 is 510 MHz higher, than Quadro RTX 4000.
- GeForce RTX 2080 and Quadro RTX 4000 are manufactured by 12 nm process technology.
- GeForce RTX 2080 is 26 mm longer, than Quadro RTX 4000.
- Memory clock speed of GeForce RTX 2080 is 1000 MHz higher, than Quadro RTX 4000.
Game benchmarks
| Assassin’s Creed OdysseyBattlefield 5Call of Duty: WarzoneCounter-Strike: Global OffensiveCyberpunk 2077Dota 2Far Cry 5FortniteForza Horizon 4Grand Theft Auto VMetro ExodusMinecraftPLAYERUNKNOWN’S BATTLEGROUNDSRed Dead Redemption 2The Witcher 3: Wild HuntWorld of Tanks | ||
| high / 1080p | 80−85 | 70−75 |
| ultra / 1080p | 60−65 | 50−55 |
| QHD / 1440p | 50−55 | 40−45 |
| 4K / 2160p | 30−35 | 24−27 |
| low / 720p | 100−110 | 95−100 |
| medium / 1080p | 90−95 | 80−85 |
The average gaming FPS of GeForce RTX 2080 in Assassin’s Creed Odyssey is 14% more, than Quadro RTX 4000. |
||
| high / 1080p | 120−130 | 110−120 |
| ultra / 1080p | 110−120 | 100−110 |
| QHD / 1440p | 90−95 | 80−85 |
| 4K / 2160p | 55−60 | 45−50 |
| low / 720p | 160−170 | 150−160 |
| medium / 1080p | 130−140 | 120−130 |
| The average gaming FPS of GeForce RTX 2080 in Battlefield 5 is 9% more, than Quadro RTX 4000. | ||
| low / 768p | 45−50 | 45−50 |
GeForce RTX 2080 and Quadro RTX 4000 have the same average FPS in Call of Duty: Warzone. |
||
| low / 768p | 250−260 | 250−260 |
| medium / 768p | 230−240 | 230−240 |
| QHD / 1440p | 150−160 | 150−160 |
| 4K / 2160p | 100−110 | 100−110 |
| high / 768p | 220−230 | 220−230 |
| GeForce RTX 2080 and Quadro RTX 4000 have the same average FPS in Counter-Strike: Global Offensive. | ||
| low / 768p | 70−75 | 70−75 |
| medium / 1080p | 50−55 | 50−55 |
GeForce RTX 2080 and Quadro RTX 4000 have the same average FPS in Cyberpunk 2077. |
||
| low / 768p | 120−130 | 120−130 |
| medium / 768p | 110−120 | 110−120 |
| GeForce RTX 2080 and Quadro RTX 4000 have the same average FPS in Dota 2. | ||
| high / 1080p | 100−110 | 90−95 |
| ultra / 1080p | 100−110 | 85−90 |
| QHD / 1440p | 85−90 | 65−70 |
| 4K / 2160p | 45−50 | 35−40 |
| low / 720p | 120−130 | 120−130 |
| medium / 1080p | 110−120 | 95−100 |
The average gaming FPS of GeForce RTX 2080 in Far Cry 5 is 15% more, than Quadro RTX 4000. |
||
| high / 1080p | 160−170 | 140−150 |
| ultra / 1080p | 130−140 | 110−120 |
| QHD / 1440p | 95−100 | 75−80 |
| 4K / 2160p | 21−24 | 21−24 |
| low / 720p | 270−280 | 260−270 |
| medium / 1080p | 190−200 | 170−180 |
| The average gaming FPS of GeForce RTX 2080 in Fortnite is 11% more, than Quadro RTX 4000. | ||
| high / 1080p | 140−150 | 120−130 |
| ultra / 1080p | 110−120 | 95−100 |
| QHD / 1440p | 100−105 | 80−85 |
| 4K / 2160p | 65−70 | 50−55 |
| low / 720p | 170−180 | 160−170 |
| medium / 1080p | 140−150 | 120−130 |
The average gaming FPS of GeForce RTX 2080 in Forza Horizon 4 is 16% more, than Quadro RTX 4000. |
||
| low / 768p | 170−180 | 170−180 |
| medium / 768p | 160−170 | 160−170 |
| high / 1080p | 140−150 | 130−140 |
| ultra / 1080p | 90−95 | 75−80 |
| QHD / 1440p | 80−85 | 65−70 |
| 4K / 2160p | − | 65−70 |
| The average gaming FPS of GeForce RTX 2080 in Grand Theft Auto V is 6% more, than Quadro RTX 4000. | ||
| high / 1080p | 75−80 | 60−65 |
| ultra / 1080p | 60−65 | 50−55 |
| QHD / 1440p | 50−55 | 35−40 |
| 4K / 2160p | 30−35 | 24−27 |
| low / 720p | 140−150 | 120−130 |
| medium / 1080p | 100−110 | 80−85 |
The average gaming FPS of GeForce RTX 2080 in Metro Exodus is 23% more, than Quadro RTX 4000. |
||
| low / 768p | 120−130 | 120−130 |
| GeForce RTX 2080 and Quadro RTX 4000 have the same average FPS in Minecraft. | ||
| high / 1080p | 150−160 | 120−130 |
| ultra / 1080p | 120−130 | 95−100 |
| 4K / 2160p | 18−20 | 18−20 |
| low / 720p | 170−180 | 150−160 |
| medium / 1080p | 170−180 | 140−150 |
| The average gaming FPS of GeForce RTX 2080 in PLAYERUNKNOWN’S BATTLEGROUNDS is 19% more, than Quadro RTX 4000. | ||
| high / 1080p | 70−75 | 55−60 |
| ultra / 1080p | 45−50 | 35−40 |
| QHD / 1440p | 35−40 | 30−33 |
| 4K / 2160p | 24−27 | 20−22 |
| low / 720p | 140−150 | 120−130 |
| medium / 1080p | 100−110 | 85−90 |
The average gaming FPS of GeForce RTX 2080 in Red Dead Redemption 2 is 20% more, than Quadro RTX 4000. |
||
| low / 768p | 300−350 | 260−270 |
| medium / 768p | 230−240 | 190−200 |
| high / 1080p | 140−150 | 110−120 |
| ultra / 1080p | 80−85 | 65−70 |
| 4K / 2160p | 55−60 | 40−45 |
| The average gaming FPS of GeForce RTX 2080 in The Witcher 3: Wild Hunt is 23% more, than Quadro RTX 4000. | ||
| low / 768p | 400−450 | 230−240 |
| ultra / 1080p | 190−200 | 110−120 |
The average gaming FPS of GeForce RTX 2080 in World of Tanks is 77% more, than Quadro RTX 4000. |
||
Full Specs
| GeForce RTX 2080 | Quadro RTX 4000 | |
| Architecture | Turing | Turing |
| Code name | Turing TU104 | TU104 |
| Type | Desktop | Workstation |
| Release date | 27 August 2018 | 13 November 2018 |
| Pipelines | 2944 | 2304 |
| Core clock speed | 1515 MHz | 1005 MHz |
| Boost Clock | 1710 MHz | 1545 MHz |
| Transistor count | 13,600 million | 13,600 million |
| Manufacturing process technology | 12 nm | 12 nm |
| Texture fill rate | 314. 6 |
222.5 |
| Length | 267 mm | 241 mm |
| Memory bus width | 256 Bit | 256 Bit |
| Memory clock speed | 14000 MHz | 13000 MHz |
| Memory bandwidth | 448.0 GB/s | 416.0 GB/s |
| Shared memory | — | |
| G-SYNC support | + | |
| VR Ready | + | |
| DirectX | 12 Ultimate (12_1) | 12 Ultimate (12_1) |
| Shader Model | 6.5 | 6.5 |
| OpenGL | 4.6 | 4.6 |
| OpenCL | 1.2 | 1.2 |
| Vulkan | 1.2.131 | 1. 2.131 |
| CUDA | 7.5 | 7.5 |
|
Check Price |
Check Price |
Similar compares
- GeForce RTX 2080 vs TITAN RTX
- GeForce RTX 2080 vs GeForce GTX 1080 Ti
- Quadro RTX 4000 vs TITAN RTX
- Quadro RTX 4000 vs GeForce GTX 1080 Ti
- GeForce RTX 2080 vs Radeon Pro W5700
- GeForce RTX 2080 vs GeForce RTX 2080 mobile
- Quadro RTX 4000 vs Radeon Pro W5700
- Quadro RTX 4000 vs GeForce RTX 2080 mobile
Nvidia GeForce RTX 2080 Ti Founders Edition vs Nvidia Quadro 4000: What is the difference?
70points
Nvidia GeForce RTX 2080 Ti Founders Edition
27points
Nvidia Quadro 4000
vs
56 facts in comparison
Nvidia GeForce RTX 2080 Ti Founders Edition
Nvidia Quadro 4000
Why is Nvidia GeForce RTX 2080 Ti Founders Edition better than Nvidia Quadro 4000?
- 875MHz faster GPU clock speed?
1350MHzvs475MHz - 13.
74 TFLOPS higher floating-point performance?
14.23 TFLOPSvs0.49 TFLOPS - 136.3 GPixel/s higher pixel rate?
143.9 GPixel/svs7.6 GPixel/s - 1048MHz faster memory clock speed?
1750MHzvs702MHz - 11192MHz higher effective memory clock speed?
14000MHzvs2808MHz - 5.5x more VRAM?
11GBvs2GB - 429.5 GTexels/s higher texture rate?
444.7 GTexels/svs15.2 GTexels/s - 1.1 newer version of DirectX?
12.1vs11
Why is Nvidia Quadro 4000 better than Nvidia GeForce RTX 2080 Ti Founders Edition?
- 118W lower TDP?
142Wvs260W - 1 more DVI outputs?
1vs0 - 25.7mm narrower?
241mmvs266.7mm
Which are the most popular comparisons?
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
Nvidia GeForce GTX 1080 Ti
Nvidia Quadro 4000
vs
Nvidia Quadro K4000
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
Asus ROG Strix GeForce RTX 3090 Gaming
Nvidia Quadro 4000
vs
Nvidia Quadro P5000
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
Nvidia GeForce RTX 2080 Super
Nvidia Quadro 4000
vs
Nvidia GeForce GTX 750 Ti
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
KFA2 GeForce RTX 3070 SG 1-Click OC
Nvidia Quadro 4000
vs
Nvidia GeForce GTX 1060
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
Nvidia Tesla T4
Nvidia Quadro 4000
vs
AMD Radeon Pro W5700
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
EVGA GeForce RTX 3080 FTW3 Ultra Gaming
Nvidia Quadro 4000
vs
Nvidia Quadro K2000
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
Asus Dual GeForce RTX 3070
Nvidia Quadro 4000
vs
Nvidia Quadro M6000
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
Nvidia GeForce GTX Titan X
Nvidia Quadro 4000
vs
Nvidia Quadro 2000
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
Gigabyte GeForce RTX 3070 Ti Gaming OC
Nvidia Quadro 4000
vs
Nvidia Quadro M4000
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
MSI GeForce GTX Titan X
Nvidia Quadro 4000
vs
Nvidia Quadro 600
Price comparison
Cheap alternatives
User reviews
Performance
1.
GPU clock speed
1350MHz
475MHz
The graphics processing unit (GPU) has a higher clock speed.
2.GPU turbo
1635MHz
Unknown. Help us by suggesting a value. (Nvidia Quadro 4000)
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
143.9 GPixel/s
7.6 GPixel/s
The number of pixels that can be rendered to the screen every second.
4.floating-point performance
14.23 TFLOPS
0.49 TFLOPS
Floating-point performance is a measurement of the raw processing power of the GPU.
5.texture rate
444.7 GTexels/s
15.2 GTexels/s
The number of textured pixels that can be rendered to the screen every second.
6.GPU memory speed
1750MHz
702MHz
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
14000MHz
2808MHz
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
616GB/s
89.9GB/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
352bit
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
✖Nvidia GeForce RTX 2080 Ti Founders Edition
✖Nvidia Quadro 4000
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
✔Nvidia GeForce RTX 2080 Ti Founders Edition
✔Nvidia Quadro 4000
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. (Nvidia Quadro 4000)
A lower load temperature means that the card produces less heat and its cooling system performs better.
6.supports ray tracing
✔Nvidia GeForce RTX 2080 Ti Founders Edition
✖Nvidia Quadro 4000
Ray tracing is an advanced light rendering technique that provides more realistic lighting, shadows, and reflections in games.
7.Supports 3D
✔Nvidia GeForce RTX 2080 Ti Founders Edition
✔Nvidia Quadro 4000
Allows you to view in 3D (if you have a 3D display and glasses).
8.supports DLSS
✔Nvidia GeForce RTX 2080 Ti Founders Edition
✖Nvidia Quadro 4000
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. (Nvidia GeForce RTX 2080 Ti Founders Edition)
This benchmark measures the graphics performance of a video card. Source: PassMark.
Ports
1.has an HDMI output
✔Nvidia GeForce RTX 2080 Ti Founders Edition
✖Nvidia Quadro 4000
Devices with a HDMI or mini HDMI port can transfer high definition video and audio to a display.
2.HDMI ports
Unknown. Help us by suggesting a value. (Nvidia Quadro 4000)
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
Unknown. Help us by suggesting a value. (Nvidia Quadro 4000)
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.
Miscellaneous
1.USB ports
Unknown. Help us by suggesting a value.
With more USB ports, you are able to connect more devices.
2.Has USB Type-C
✔Nvidia GeForce RTX 2080 Ti Founders Edition
✖Nvidia Quadro 4000
The USB Type-C features reversible plug orientation and cable direction.
Price comparison
Cancel
Which are the best graphics cards?
NVIDIA Quadro RTX 4000 Max-Q vs NVIDIA GeForce RTX 2080 (Desktop)
Performance Rating — 3DMark 11 + Fire Strike + Time Spy — GeForce RTX 2080 (Desktop)
The following benchmarks stem from our benchmarks of review laptops.
The performance depends on the used graphics memory, clock rate, processor, system settings, drivers, and operating systems. So the results don’t have to be representative for all laptops with this GPU. For detailed information on the benchmark results, click on the fps number.
For more games that might be playable and a list of all games and graphics cards visit our Gaming List
log 03. 15:17:08
#0 checking url part for id 9882 +0s … 0s
#1 checking url part for id 9286 +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 Sun, 02 Oct 2022 17:27:15 +0200 +0s … 0s
#4 composed specs +0.088s … 0.088s
#5 did output specs +0s … 0.088s
#6 start showIntegratedCPUs +0s … 0.088s
#7 linkCache_getLink using $NBC_LINKCACHE +0.028s … 0.116s
#8 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.116s
#9 linkCache_getLink using $NBC_LINKCACHE +0s … 0.117s
#10 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.119s
#11 getting avg benchmarks for device 9882 +0.001s … 0.119s
#12 linkCache_getLink using $NBC_LINKCACHE +0s … 0.12s
#13 got single benchmarks 9882 +0.007s … 0.126s
#14 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.13s
#15 linkCache_getLink using $NBC_LINKCACHE +0s … 0.13s
#16 linkCache_getLink using $NBC_LINKCACHE +0s … 0.13s
#17 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.132s
#18 getting avg benchmarks for device 9286 +0s … 0.132s
#19 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#20 got single benchmarks 9286 +0.01s … 0.142s
#21 got avg benchmarks for devices +0s … 0.142s
#22 linkCache_getLink no uid found +0.001s … 0.143s
#23 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.143s
#24 linkCache_getLink using $NBC_LINKCACHE +0s … 0.143s
#25 linkCache_getLink no uid found +0s … 0.143s
#26 linkCache_getLink using $NBC_LINKCACHE +0s … 0.143s
#27 linkCache_getLink using $NBC_LINKCACHE +0s … 0.144s
#28 linkCache_getLink using $NBC_LINKCACHE +0s … 0.144s
#29 linkCache_getLink no uid found +0s … 0.144s
#30 linkCache_getLink using $NBC_LINKCACHE +0s … 0.144s
#31 linkCache_getLink using $NBC_LINKCACHE +0s … 0.145s
#32 linkCache_getLink using $NBC_LINKCACHE +0s … 0.145s
#33 linkCache_getLink no uid found +0s … 0.145s
#34 linkCache_getLink using $NBC_LINKCACHE +0s … 0.145s
#35 linkCache_getLink using $NBC_LINKCACHE +0s … 0.145s
#36 linkCache_getLink using $NBC_LINKCACHE +0s … 0.145s
#37 linkCache_getLink no uid found +0s … 0.145s
#38 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.146s
#39 linkCache_getLink using $NBC_LINKCACHE +0s … 0.146s
#40 linkCache_getLink using $NBC_LINKCACHE +0s … 0.146s
#41 linkCache_getLink no uid found +0s … 0.146s
#42 linkCache_getLink using $NBC_LINKCACHE +0s … 0.147s
#43 linkCache_getLink using $NBC_LINKCACHE +0s … 0.147s
#44 linkCache_getLink using $NBC_LINKCACHE +0s … 0.147s
#45 linkCache_getLink no uid found +0s … 0.147s
#46 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#47 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#48 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#49 linkCache_getLink no uid found +0s … 0.148s
#50 linkCache_getLink using $NBC_LINKCACHE +0s … 0.148s
#51 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#52 linkCache_getLink using $NBC_LINKCACHE +0s … 0.149s
#53 linkCache_getLink no uid found +0s .
.. 0.149s
#54 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.149s
#55 linkCache_getLink no uid found +0s … 0.149s
#56 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#57 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#58 linkCache_getLink no uid found +0s … 0.15s
#59 linkCache_getLink no uid found +0s … 0.15s
#60 linkCache_getLink no uid found +0.001s … 0.15s
#61 linkCache_getLink using $NBC_LINKCACHE +0s … 0.15s
#62 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#63 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#64 linkCache_getLink no uid found +0s … 0.151s
#65 linkCache_getLink no uid found +0s … 0.151s
#66 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.151s
#67 linkCache_getLink using $NBC_LINKCACHE +0s … 0.151s
#68 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.152s
#69 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#70 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.152s
#71 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s
#72 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.154s
#73 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#74 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.155s
#75 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#76 linkCache_getLink no uid found +0s … 0.155s
#77 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.156s
#78 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#79 linkCache_getLink no uid found +0.001s … 0.157s
#80 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#81 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#82 linkCache_getLink no uid found +0s … 0.
158s
#83 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#84 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#85 linkCache_getLink no uid found +0s … 0.158s
#86 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#87 linkCache_getLink no uid found +0s … 0.159s
#88 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#89 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#90 linkCache_getLink no uid found +0s … 0.16s
#91 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#92 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#93 linkCache_getLink no uid found +0s … 0.161s
#94 linkCache_getLink using $NBC_LINKCACHE +0s … 0.161s
#95 linkCache_getLink using $NBC_LINKCACHE +0s … 0.161s
#96 linkCache_getLink no uid found +0s … 0.161s
#97 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.162s
#98 linkCache_getLink using $NBC_LINKCACHE +0s … 0.162s
#99 linkCache_getLink using $NBC_LINKCACHE +0s … 0.162s
#100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.162s
#101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.162s
#102 linkCache_getLink using $NBC_LINKCACHE +0s … 0.162s
#103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.163s
#104 linkCache_getLink no uid found +0s … 0.163s
#105 linkCache_getLink using $NBC_LINKCACHE +0s … 0.163s
#106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.164s
#107 linkCache_getLink no uid found +0s … 0.164s
#108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.164s
#109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.164s
#110 linkCache_getLink no uid found +0s … 0.164s
#111 linkCache_getLink using $NBC_LINKCACHE +0s … 0.165s
#112 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.165s
#113 linkCache_getLink using $NBC_LINKCACHE +0s … 0.166s
#114 linkCache_getLink no uid found +0s … 0.166s
#115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.166s
#116 linkCache_getLink using $NBC_LINKCACHE +0s … 0.166s
#117 linkCache_getLink no uid found +0s … 0.166s
#118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.167s
#119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.167s
#120 linkCache_getLink no uid found +0s … 0.167s
#121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.168s
#122 linkCache_getLink no uid found +0s … 0.168s
#123 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.168s
#124 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.169s
#125 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.17s
#126 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.17s
#127 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.171s
#128 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.172s
#129 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.172s
#130 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.173s
#131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.173s
#132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#133 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#134 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s
#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 no uid found +0s … 0.176s
#141 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.177s
#142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#143 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#144 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.178s
#145 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#146 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.178s
#147 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#148 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.179s
#149 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#150 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#151 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#152 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#153 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#154 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.181s
#155 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.182s
#156 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#157 linkCache_getLink using $NBC_LINKCACHE +0s … 0.182s
#158 min, max, avg, median took s +0s … 0.183s
#159 before gaming benchmark output +0s … 0.183s
#160 Got 635 rows for game benchmarks. +0.034s … 0.216s
#161 composed SQL query for gamebenchmarks +0s … 0.216s
#162 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#163 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#164 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#165 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#166 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#167 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#168 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#169 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#170 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.217s
#171 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#172 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#173 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#174 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#175 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#176 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#179 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#180 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#181 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#182 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#183 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#184 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.217s
#185 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#186 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#187 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#188 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#189 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#191 linkCache_getLink using $NBC_LINKCACHE +0s … 0.217s
#192 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#193 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#194 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#195 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#196 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#197 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#198 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.218s
#199 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#200 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#201 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#202 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#203 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#204 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#205 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#206 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#207 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#208 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#209 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#210 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#211 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#212 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.218s
#213 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#214 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#215 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#216 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#217 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#218 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#219 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#220 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#221 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#222 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#223 linkCache_getLink using $NBC_LINKCACHE +0s … 0.218s
#224 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#225 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#226 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.219s
#227 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#228 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#229 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#230 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#231 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#232 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#233 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#234 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#235 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#236 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#237 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#238 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#239 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#240 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.219s
#241 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#242 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#243 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#244 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#245 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#246 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#247 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#248 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#249 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#250 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#251 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#252 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#253 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#254 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.219s
#255 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#256 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#257 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#258 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#259 linkCache_getLink using $NBC_LINKCACHE +0s … 0.219s
#260 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#261 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#262 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#263 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#264 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#265 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#266 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#267 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#268 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.22s
#269 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#270 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#271 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#272 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#273 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#274 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#275 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#276 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#277 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#278 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#279 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#280 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#281 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#282 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#283 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.22s
#284 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#285 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#286 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#287 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#288 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#289 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#290 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#291 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#292 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#293 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#294 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#295 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#296 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#297 linkCache_getLink using $NBC_LINKCACHE +0s … 0.22s
#298 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.221s
#299 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#300 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#301 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#302 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#303 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#304 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#305 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#306 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#307 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#308 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#309 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#310 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#311 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#312 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.221s
#313 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#314 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#315 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#316 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#317 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#318 linkCache_getLink using $NBC_LINKCACHE +0s … 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 +0s … 0.221s
#322 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#323 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#324 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#325 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#326 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.221s
#327 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#328 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#329 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#330 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#331 linkCache_getLink using $NBC_LINKCACHE +0s … 0.221s
#332 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#333 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#334 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#335 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#336 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#337 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#338 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#339 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#340 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.222s
#341 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#342 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#343 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#344 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#345 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#346 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#347 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#348 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#349 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#350 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#351 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#352 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#353 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#354 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.222s
#355 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#356 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#357 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#358 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#359 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#360 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#361 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#362 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#363 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#364 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#365 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#366 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#367 linkCache_getLink using $NBC_LINKCACHE +0s … 0.222s
#368 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.223s
#369 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#370 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#371 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#372 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#373 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#374 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#375 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#376 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#377 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#378 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#379 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#380 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#381 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#382 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.223s
#383 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#384 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#385 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#386 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#387 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#388 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#389 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#390 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#391 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#392 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#393 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#394 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#395 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#396 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.223s
#397 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#398 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#399 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#400 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#401 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#402 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#403 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#404 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#405 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#406 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#407 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#408 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#409 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#410 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.223s
#411 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#412 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#413 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#414 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#415 linkCache_getLink using $NBC_LINKCACHE +0s … 0.223s
#416 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#417 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#418 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#419 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#420 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#421 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#422 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#423 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#424 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.224s
#425 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#426 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#427 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#428 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#429 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#430 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#431 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#432 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#433 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#434 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#435 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#436 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#437 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#438 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.224s
#439 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#440 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#441 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#442 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#443 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#444 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#445 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#446 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#447 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#448 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#449 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#450 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#451 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#452 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.224s
#453 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#454 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#455 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#456 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#457 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#458 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#459 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#460 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#461 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#462 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#463 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#464 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#465 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#466 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.224s
#467 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#468 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#469 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#470 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#471 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#472 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#473 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#474 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#475 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#476 linkCache_getLink using $NBC_LINKCACHE +0s … 0.224s
#477 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#478 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#479 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#480 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.225s
#481 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#482 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#483 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#484 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#485 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#486 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#487 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#488 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#489 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#490 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#491 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#492 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#493 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#494 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.225s
#495 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#496 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#497 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#498 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#499 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#500 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#501 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#502 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#503 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#504 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#505 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#506 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#507 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#508 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.225s
#509 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#510 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#511 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#512 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#513 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#514 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#515 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#516 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#517 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#518 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#519 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#520 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#521 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#522 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.225s
#523 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#524 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#525 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#526 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#527 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#528 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#529 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#530 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#531 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#532 linkCache_getLink using $NBC_LINKCACHE +0s … 0.225s
#533 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#534 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#535 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#536 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.226s
#537 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#538 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#539 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#540 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#541 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#542 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#543 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#544 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#545 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#546 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#547 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#548 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#549 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#550 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.226s
#551 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#552 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#553 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#554 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#555 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#556 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#557 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#558 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#559 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#560 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#561 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#562 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#563 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#564 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.226s
#565 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#566 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#567 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#568 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#569 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#570 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#571 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#572 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#573 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#574 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#575 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#576 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#577 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#578 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.226s
#579 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#580 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#581 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#582 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#583 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#584 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#585 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#586 linkCache_getLink using $NBC_LINKCACHE +0s … 0.226s
#587 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#588 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#589 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#590 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#591 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#592 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.227s
#593 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#594 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#595 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#596 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#597 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#598 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#599 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#600 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#601 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#602 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#603 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#604 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#605 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#606 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.227s
#607 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#608 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#609 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#610 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#611 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#612 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#613 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#614 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#615 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#616 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#617 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#618 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#619 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#620 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.227s
#621 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#622 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#623 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#624 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#625 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#626 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#627 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#628 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#629 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#630 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#631 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#632 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#633 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#634 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.227s
#635 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#636 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#637 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#638 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#639 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#640 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#641 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#642 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#643 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#644 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#645 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#646 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#647 linkCache_getLink using $NBC_LINKCACHE +0s … 0.227s
#648 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.228s
#649 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#650 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#651 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#652 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#653 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#654 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#655 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#656 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#657 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#658 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#659 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#660 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#661 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#662 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.228s
#663 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#664 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#665 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#666 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#667 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#668 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#669 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#670 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#671 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#672 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#673 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#674 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#675 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#676 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.228s
#677 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#678 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#679 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#680 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#681 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#682 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#683 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#684 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#685 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#686 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#687 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#688 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#689 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#690 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.228s
#691 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#692 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#693 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#694 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#695 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#696 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#697 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#698 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#699 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#700 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#701 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#702 linkCache_getLink using $NBC_LINKCACHE +0s … 0.228s
#703 linkCache_getLink using $NBC_LINKCACHE +0s … 0.229s
#704 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.229s
#705 linkCache_getLink using $NBC_LINKCACHE +0s … 0.229s
#706 linkCache_getLink using $NBC_LINKCACHE +0s … 0.229s
#707 linkCache_getLink using $NBC_LINKCACHE +0s … 0.229s
#708 linkCache_getLink using $NBC_LINKCACHE +0s … 0.229s
#709 linkCache_getLink using $NBC_LINKCACHE +0s … 0.229s
#710 linkCache_getLink using $NBC_LINKCACHE +0s … 0.229s
#711 linkCache_getLink using $NBC_LINKCACHE +0s … 0.229s
#712 got data and put it in $dataArray +0.002s … 0.231s
#713 linkCache_getLink using $NBC_LINKCACHE +0.071s … 0.302s
#714 linkCache_getLink using $NBC_LINKCACHE +0s … 0.302s
#715 linkCache_getLink using $NBC_LINKCACHE +0s … 0.302s
#716 linkCache_getLink using $NBC_LINKCACHE +0s … 0.302s
#717 linkCache_getLink using $NBC_LINKCACHE +0s … 0.302s
#718 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.302s
#719 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.303s
#720 linkCache_getLink using $NBC_LINKCACHE +0s … 0.303s
#721 linkCache_getLink using $NBC_LINKCACHE +0s … 0.303s
#722 linkCache_getLink using $NBC_LINKCACHE +0s … 0.303s
#723 linkCache_getLink using $NBC_LINKCACHE +0s … 0.303s
#724 linkCache_getLink using $NBC_LINKCACHE +0s … 0.303s
#725 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.304s
#726 linkCache_getLink using $NBC_LINKCACHE +0s … 0.304s
#727 linkCache_getLink using $NBC_LINKCACHE +0s … 0.304s
#728 linkCache_getLink using $NBC_LINKCACHE +0s … 0.304s
#729 linkCache_getLink using $NBC_LINKCACHE +0s … 0.304s
#730 linkCache_getLink using $NBC_LINKCACHE +0s … 0.304s
#731 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.305s
#732 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.305s
#733 linkCache_getLink using $NBC_LINKCACHE +0s … 0.305s
#734 linkCache_getLink using $NBC_LINKCACHE +0s … 0.305s
#735 linkCache_getLink using $NBC_LINKCACHE +0s … 0.305s
#736 linkCache_getLink using $NBC_LINKCACHE +0s … 0.305s
#737 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.305s
#738 linkCache_getLink using $NBC_LINKCACHE +0s … 0.305s
#739 linkCache_getLink using $NBC_LINKCACHE +0s … 0.305s
#740 linkCache_getLink using $NBC_LINKCACHE +0s … 0.305s
#741 linkCache_getLink using $NBC_LINKCACHE +0s … 0.305s
#742 linkCache_getLink using $NBC_LINKCACHE +0s … 0.305s
#743 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.306s
#744 linkCache_getLink using $NBC_LINKCACHE +0s … 0.306s
#745 linkCache_getLink using $NBC_LINKCACHE +0s … 0.306s
#746 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.306s
#747 linkCache_getLink using $NBC_LINKCACHE +0s … 0.306s
#748 linkCache_getLink using $NBC_LINKCACHE +0s … 0.306s
#749 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.307s
#750 linkCache_getLink using $NBC_LINKCACHE +0s … 0.307s
#751 linkCache_getLink using $NBC_LINKCACHE +0s … 0.307s
#752 linkCache_getLink using $NBC_LINKCACHE +0s … 0.307s
#753 linkCache_getLink using $NBC_LINKCACHE +0s … 0.307s
#754 linkCache_getLink using $NBC_LINKCACHE +0s … 0.307s
#755 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.308s
#756 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#757 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#758 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#759 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#760 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.308s
#761 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.308s
#762 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#763 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#764 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#765 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#766 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#767 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.309s
#768 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#769 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#770 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#771 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#772 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#773 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.31s
#774 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.31s
#775 linkCache_getLink using $NBC_LINKCACHE +0s … 0.31s
#776 linkCache_getLink using $NBC_LINKCACHE +0s … 0.31s
#777 linkCache_getLink using $NBC_LINKCACHE +0s … 0.31s
#778 linkCache_getLink using $NBC_LINKCACHE +0s … 0.31s
#779 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.311s
#780 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#781 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#782 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#783 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#784 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#785 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.311s
#786 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#787 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#788 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.311s
#789 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#790 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#791 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.312s
#792 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#793 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#794 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#795 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#796 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#797 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.313s
#798 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#799 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#800 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#801 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#802 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.313s
#803 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#804 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#805 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#806 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#807 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#808 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.314s
#809 linkCache_getLink using $NBC_LINKCACHE +0s … 0.314s
#810 linkCache_getLink using $NBC_LINKCACHE +0s … 0.314s
#811 linkCache_getLink using $NBC_LINKCACHE +0s … 0.314s
#812 linkCache_getLink using $NBC_LINKCACHE +0s … 0.314s
#813 linkCache_getLink using $NBC_LINKCACHE +0s … 0.314s
#814 linkCache_getLink using $NBC_LINKCACHE +0s … 0.314s
#815 linkCache_getLink using $NBC_LINKCACHE +0s … 0.314s
#816 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.314s
#817 linkCache_getLink using $NBC_LINKCACHE +0s … 0.314s
#818 linkCache_getLink using $NBC_LINKCACHE +0s … 0.314s
#819 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.315s
#820 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#821 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#822 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#823 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#824 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#825 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#826 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#827 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#828 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#829 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#830 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.315s
#831 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#832 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#833 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#834 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#835 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#836 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#837 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#838 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#839 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#840 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#841 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.316s
#842 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#843 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#844 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.316s
#845 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#846 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#847 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#848 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#849 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#850 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#851 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#852 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.317s
#853 linkCache_getLink using $NBC_LINKCACHE +0s … 0.317s
#854 linkCache_getLink using $NBC_LINKCACHE +0s … 0.317s
#855 linkCache_getLink using $NBC_LINKCACHE +0s … 0.317s
#856 linkCache_getLink using $NBC_LINKCACHE +0s … 0.317s
#857 linkCache_getLink using $NBC_LINKCACHE +0s … 0.317s
#858 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.317s
#859 linkCache_getLink using $NBC_LINKCACHE +0s … 0.317s
#860 linkCache_getLink using $NBC_LINKCACHE +0s … 0.317s
#861 linkCache_getLink using $NBC_LINKCACHE +0s … 0.317s
#862 linkCache_getLink using $NBC_LINKCACHE +0s … 0.317s
#863 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.318s
#864 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#865 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#866 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#867 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#868 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#869 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#870 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#871 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#872 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.318s
#873 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#874 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.319s
#875 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#876 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#877 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#878 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#879 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#880 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#881 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#882 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#883 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#884 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#885 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.319s
#886 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.319s
#887 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#888 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#889 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#890 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#891 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#892 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#893 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#894 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#895 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#896 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.32s
#897 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#898 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#899 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#900 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.321s
#901 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#902 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#903 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#904 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#905 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#906 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#907 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#908 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#909 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#910 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#911 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.322s
#912 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s
#913 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s
#914 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.322s
#915 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s
#916 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s
#917 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s
#918 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s
#919 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s
#920 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s
#921 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s
#922 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s
#923 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s
#924 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.323s
#925 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#926 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#927 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#928 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.323s
#929 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#930 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#931 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#932 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#933 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#934 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#935 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.324s
#936 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#937 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#938 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#939 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#940 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#941 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#942 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.324s
#943 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#944 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#945 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#946 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.324s
#947 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#948 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#949 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#950 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#951 linkCache_getLink using $NBC_LINKCACHE +0s … 0.325s
#952 linkCache_getLink using $NBC_LINKCACHE +0s … 0.325s
#953 linkCache_getLink using $NBC_LINKCACHE +0s … 0.325s
#954 linkCache_getLink using $NBC_LINKCACHE +0s … 0.325s
#955 linkCache_getLink using $NBC_LINKCACHE +0s … 0.325s
#956 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.325s
#957 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.326s
#958 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#959 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#960 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#961 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#962 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#963 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#964 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#965 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#966 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#967 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#968 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.326s
#969 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#970 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.326s
#971 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#972 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#973 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#974 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#975 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#976 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#977 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#978 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.327s
#979 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#980 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#981 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#982 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#983 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#984 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.327s
#985 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#986 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#987 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#988 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.328s
#989 linkCache_getLink using $NBC_LINKCACHE +0s … 0.328s
#990 linkCache_getLink using $NBC_LINKCACHE +0s … 0.328s
#991 linkCache_getLink using $NBC_LINKCACHE +0s … 0.328s
#992 linkCache_getLink using $NBC_LINKCACHE +0s … 0.328s
#993 linkCache_getLink using $NBC_LINKCACHE +0s … 0.328s
#994 linkCache_getLink using $NBC_LINKCACHE +0s … 0.328s
#995 linkCache_getLink using $NBC_LINKCACHE +0s … 0.328s
#996 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.329s
#997 linkCache_getLink using $NBC_LINKCACHE +0s … 0.329s
#998 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.329s
#999 linkCache_getLink using $NBC_LINKCACHE +0s … 0.329s
#1000 linkCache_getLink using $NBC_LINKCACHE +0s … 0.329s
#1001 linkCache_getLink using $NBC_LINKCACHE +0s … 0.329s
#1002 linkCache_getLink using $NBC_LINKCACHE +0s … 0.329s
#1003 linkCache_getLink using $NBC_LINKCACHE +0s … 0.329s
#1004 linkCache_getLink using $NBC_LINKCACHE +0s … 0.329s
#1005 linkCache_getLink using $NBC_LINKCACHE +0s … 0.329s
#1006 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.33s
#1007 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1008 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1009 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1010 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1011 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1012 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.33s
#1013 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1014 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1015 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1016 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.331s
#1017 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1018 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1019 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1020 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1021 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1022 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1023 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1024 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1025 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1026 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.331s
#1027 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1028 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1029 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1030 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1031 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1032 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1033 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1034 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1035 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1036 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.332s
#1037 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1038 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1039 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1040 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.332s
#1041 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1042 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1043 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1044 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1045 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1046 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.333s
#1047 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1048 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1049 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1050 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1051 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1052 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1053 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1054 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.333s
#1055 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1056 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.334s
#1057 linkCache_getLink using $NBC_LINKCACHE +0s … 0.334s
#1058 linkCache_getLink using $NBC_LINKCACHE +0s … 0.334s
#1059 linkCache_getLink using $NBC_LINKCACHE +0s … 0.334s
#1060 linkCache_getLink using $NBC_LINKCACHE +0s … 0.334s
#1061 linkCache_getLink using $NBC_LINKCACHE +0s … 0.334s
#1062 linkCache_getLink using $NBC_LINKCACHE +0s … 0.334s
#1063 linkCache_getLink using $NBC_LINKCACHE +0s … 0.334s
#1064 linkCache_getLink using $NBC_LINKCACHE +0s … 0.334s
#1065 linkCache_getLink using $NBC_LINKCACHE +0s … 0.334s
#1066 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.335s
#1067 linkCache_getLink using $NBC_LINKCACHE +0s … 0.335s
#1068 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.335s
#1069 linkCache_getLink using $NBC_LINKCACHE +0s … 0.335s
#1070 linkCache_getLink using $NBC_LINKCACHE +0s … 0.335s
#1071 linkCache_getLink using $NBC_LINKCACHE +0s … 0.335s
#1072 linkCache_getLink using $NBC_LINKCACHE +0s … 0.335s
#1073 linkCache_getLink using $NBC_LINKCACHE +0s … 0.335s
#1074 linkCache_getLink using $NBC_LINKCACHE +0s … 0.335s
#1075 linkCache_getLink using $NBC_LINKCACHE +0s … 0.335s
#1076 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.336s
#1077 linkCache_getLink using $NBC_LINKCACHE +0s … 0.336s
#1078 linkCache_getLink using $NBC_LINKCACHE +0s … 0.336s
#1079 linkCache_getLink using $NBC_LINKCACHE +0s … 0.336s
#1080 linkCache_getLink using $NBC_LINKCACHE +0s … 0.336s
#1081 linkCache_getLink using $NBC_LINKCACHE +0s … 0.336s
#1082 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.336s
#1083 linkCache_getLink using $NBC_LINKCACHE +0s … 0.336s
#1084 linkCache_getLink using $NBC_LINKCACHE +0s … 0.336s
#1085 linkCache_getLink using $NBC_LINKCACHE +0s … 0.336s
#1086 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.336s
#1087 linkCache_getLink using $NBC_LINKCACHE +0s … 0.336s
#1088 linkCache_getLink using $NBC_LINKCACHE +0s … 0.337s
#1089 linkCache_getLink using $NBC_LINKCACHE +0s … 0.337s
#1090 linkCache_getLink using $NBC_LINKCACHE +0s … 0.337s
#1091 linkCache_getLink using $NBC_LINKCACHE +0s … 0.337s
#1092 linkCache_getLink using $NBC_LINKCACHE +0s … 0.337s
#1093 linkCache_getLink using $NBC_LINKCACHE +0s … 0.337s
#1094 linkCache_getLink using $NBC_LINKCACHE +0s … 0.337s
#1095 linkCache_getLink using $NBC_LINKCACHE +0s … 0.337s
#1096 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.337s
#1097 linkCache_getLink using $NBC_LINKCACHE +0s … 0.337s
#1098 linkCache_getLink using $NBC_LINKCACHE +0s … 0.337s
#1099 linkCache_getLink using $NBC_LINKCACHE +0s … 0.337s
#1100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.337s
#1101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.337s
#1102 linkCache_getLink using $NBC_LINKCACHE +0s … 0.337s
#1103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.337s
#1104 linkCache_getLink using $NBC_LINKCACHE +0s … 0.338s
#1105 linkCache_getLink using $NBC_LINKCACHE +0s … 0.338s
#1106 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.338s
#1107 linkCache_getLink using $NBC_LINKCACHE +0s … 0.338s
#1108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.338s
#1109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.338s
#1110 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.338s
#1111 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.339s
#1112 linkCache_getLink using $NBC_LINKCACHE +0s … 0.339s
#1113 linkCache_getLink using $NBC_LINKCACHE +0s … 0.339s
#1114 linkCache_getLink using $NBC_LINKCACHE +0s … 0.339s
#1115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.339s
#1116 linkCache_getLink using $NBC_LINKCACHE +0s … 0.339s
#1117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.339s
#1118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.339s
#1119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.339s
#1120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.339s
#1121 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.341s
#1122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.341s
#1123 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.342s
#1124 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.342s
#1125 linkCache_getLink using $NBC_LINKCACHE +0s … 0.342s
#1126 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.343s
#1127 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s
#1128 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s
#1129 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s
#1130 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s
#1131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s
#1132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s
#1133 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s
#1134 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s
#1135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s
#1136 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.344s
#1137 linkCache_getLink using $NBC_LINKCACHE +0s … 0.344s
#1138 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.344s
#1139 linkCache_getLink using $NBC_LINKCACHE +0s … 0.344s
#1140 linkCache_getLink using $NBC_LINKCACHE +0s … 0.344s
#1141 linkCache_getLink using $NBC_LINKCACHE +0s … 0.344s
#1142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.344s
#1143 linkCache_getLink using $NBC_LINKCACHE +0s … 0.344s
#1144 linkCache_getLink using $NBC_LINKCACHE +0s … 0.344s
#1145 linkCache_getLink using $NBC_LINKCACHE +0s … 0.344s
#1146 benchmarks composed for output. +0s … 0.344s
#1147 calculated avg scores. +0s … 0.344s
#1148 linkCache_getLink using $NBC_LINKCACHE +0.054s … 0.398s
#1149 return log +0.002s … 0.401s
NVIDIA Quadro RTX 4000 Review – Techgage
Chaos Group V-Ray
Since our V-Ray projects don’t cooperate with Radeon and Radeon Pro cards (more here), we’re sticking to Quadro and GeForce for this look.
NVIDIA’s Quadro RTX 4000 is seen to be a huge upgrade over last-gen’s P4000, cutting render times nearly in half.
I don’t believe RTX’s ray tracing cores are used at all in rendering, so these performance improvements owe their thanks to NVIDIA’s Turing architecture. On the topic of RTX, the RT cores can in fact be used with the AI denoiser, but currently, it is suitable only for interactive design, not final renders.
It won’t be a surprise to anyone that RTX 4000 is faster than P4000, but some might be surprised to see RTX 4000 beat out last-gen’s top (regular) Quadro, the P6000. That GPU of course has three times the VRAM, but from a pure performance standpoint, the gains are seriously impressive. The RTX 2080 Ti result gives us an idea of what to expect out of the Quadro RTX 6000.
Redshift
While V-Ray can take advantage of RTX via the built-in denoiser, Redshift is holding off its support until 3.0 arrives. Whereas V-Ray highlighted an enormous gain moving from Pascal to Turing, Redshift doesn’t exhibit the same kind of gain.
The RTX 4000 performs similarly to the RTX 2080 Ti, which we think highlights that our project might not be as demanding as we need it to be.
However, there is some clear separation between those big cards and the last-gen TITAN Xp. In the usual match up against the RTX 4000 and P4000, the new card delivers some hearty speedups.
OTOY Octane
Similar to Redshift, OTOY is saving its RTX support for a later date. To be specific, it’ll come with Octane 2019, which has a tentative release date. Whenever it does happen, OTOY will be releasing this benchmark to reflect performance for both RTX on and off. When it hits the variety of platforms it supports, Octane’s RTX enhancement should speed up render times significantly.
Even without those speedups, Turing helps RTX make a big difference, with the RTX 4000 falling not too far behind the last generation P6000, and leaping far ahead of the P4000.
Blender
We recommend checking out our Blender 2.8 performance deep-dive for additional info.
Unlike rendering, Blender’s viewport performance tends to jump around, with higher resolutions proving far more grueling for graphics hardware than lower ones.
At 1080p, the RTX 4000 handles itself well, placing just behind the 2080 Ti gaming card, which sports more CUDA cores (and not to mention more VRAM). That effort was enough to surpass the last-gen TITAN Xp.
At 4K, the pain gets real, and it takes a 2080 Ti (among these GPUs) to deliver a semi-reasonable level of performance. It’s important to note that LookDev isn’t usually constantly used, so its lower frame rate isn’t a killer. If this performance carried over to the solid shading and wireframe modes, it’d be an issue. Instead, all of these GPUs could handle those modes just fine, at 4K/60.
For rendering performance, the more powerful the GPU, the better the performance. The 2080 Ti unsurprisingly sits at the top. These results actually scale according as accurately as we’d expect them to if we simply had to guess what the results would look like.
Since it’s worth highlighting again, the RTX 4000 outperforms the older P4000 by a very wide margin here.
LuxMark
With the launch of the Radeon VII, AMD specifically called out improved LuxMark performance, which is interesting on account of the fact that it’s not one we hear about too often.
Well, the results here explain well why AMD promoted this tool, as the VII soars ahead of everything else – with an exception.
The 2080 Ti handles the more complex hotel scene better than VII, hinting that the Radeon card’s performance advantage isn’t going to be guaranteed. It’s an interesting result, since AMD also has the same kind of odd performance behavior on its Ryzen CPUs in KeyShot, where the simpler car render performs fine, but the interior scene falls well behind Intel. Something about our chosen interior scenes just don’t jive as well with AMD as the others right now.
Radeon ProRender
Much to AMD’s chagrin, NVIDIA’s graphics cards perform extremely well in its Radeon ProRender. Based on the performance shown here, rendering performance on Turing is unbeatable, with the lower spec’d RTX 4000 falling behind the technically more powerful Radeon VII.
We wouldn’t say this is a reason to avoid AMD cards for ProRender, as rendering performance isn’t everything, but, if you plan to use interactive rendering, that is still rendering, so you are going to want the most powerful GPU your wallet can handle.
Support our efforts! With ad revenue at an all-time low for written websites, we’re relying more than ever on reader support to help us continue putting so much effort into this type of content. You can support us by becoming a Patron, or by using our Amazon shopping affiliate links listed through our articles. Thanks for your support!
0022 1350MHz vs 475MHz
14.23 TFLOPS vs 0.49 TFLOPS
143.9 GPixel/s vs 7.6 GPixel/s
1750MHz vs 702MHz
14000MHz vs 2808MHz
11GB vs 2GB
444.7 GTexels/s vs 15.2 GTexels/s
12.
1 vs 11 - 118W below TDP?
142W vs 260W - 1 more DVI outputs?
1 vs 0 - 25.7mm narrower?
241mm vs 266.7mm
Which comparisons are the most popular?
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
Nvidia GeForce GTX 1080 Ti
Nvidia Quadro 4000
vs
Nvidia Quadro K4000
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
Asus ROG Strix GeForce RTX 3090 Gaming
Nvidia Quadro 4000
vs
Nvidia Quadro P5000
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
Nvidia GeForce RTX 2080 Super
Nvidia Quadro 4000
vs
Nvidia GeForce GTX 750 Ti
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
KFA2 GeForce RTX 3070 SG 1-Click OC
Nvidia Quadro 4000
vs
Nvidia GeForce GTX 1060
Nvidia GeForce RTX 2080 Edition Founders0003
vs
Nvidia Tesla T4
Nvidia Quadro 4000
vs
AMD Radeon Pro W5700
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
EVGA GeForce RTX 3080 FTW3 Ultra Gaming
Nvidia Quadro 4000
vs
Nvidia Quadro K2000
Nvidia GeForce RTX 2080 Ti Founders Edition
0004 Nvidia Quadro M6000
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
Nvidia GeForce GTX Titan X
Nvidia Quadro 4000
vs
Nvidia Quadro 2000
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
Gigabyte GeForce RTX 3070 Ti Gaming OC
Nvidia Quadro 4000
vs
Nvidia Quadro M4000
Nvidia GeForce RTX 2080 Ti Founders Edition
vs
When the GPU is running below its limits, it may jump to a higher clock speed to increase performance.
3.pixel rate
143.9 GPixel/s
7.6 GPixel/s
The number of pixels that can be displayed on the screen every second.
4.flops
14.23 TFLOPS
0.49 TFLOPS
FLOPS is a measure of GPU processing power.
5. texture size
444.7 GTexels/s
15.2 GTexels/s
The number of textured pixels that can be displayed on the screen every second.
6.GPU memory speed
1750MHz
702MHz
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
14000MHz
2808MHz
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
616GB/s
89.9GB/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
352bit
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.versions of GDDR memory
Later versions of GDDR memory offer improvements such as higher data transfer rates, which improve performance.
6. Supports memory troubleshooting code
✖Nvidia GeForce RTX 2080 Ti Founders Edition
✖Nvidia Quadro 4000
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
✔Nvidia GeForce RTX 2080 Ti Founders Edition
✔Nvidia Quadro 4000
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. (Nvidia Quadro 4000)
Lower boot temperature means the card generates less heat and the cooling system works better.
6.supports ray tracing
✔Nvidia GeForce RTX 2080 Ti Founders Edition
✖Nvidia Quadro 4000
Ray tracing is an advanced light rendering technique that provides more realistic lighting, shadows and reflections in games.
7. Supports 3D
✔Nvidia GeForce RTX 2080 Ti Founders Edition
✔Nvidia Quadro 4000
Allows you to view in 3D (if you have a 3D screen and glasses).
8.supports DLSS
✔Nvidia GeForce RTX 2080 Ti Founders Edition
✖Nvidia Quadro 4000
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. (Nvidia GeForce RTX 2080 Ti Founders Edition)
This test measures the graphics performance of a graphics card. Source: Pass Mark.
Ports
1.has HDMI output
✔Nvidia GeForce RTX 2080 Ti Founders Edition
✖Nvidia Quadro 4000
Devices with HDMI or mini HDMI ports can stream HD video and audio to the connected display.
2.HDMI connectors
Unknown. Help us offer a price. (Nvidia Quadro 4000)
More HDMI connectors allow you to connect multiple devices such as game consoles and TVs at the same time.
HDMI 3.Version
HDMI 2.0
Unknown. Help us offer a price. (Nvidia Quadro 4000)
New versions of HDMI 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.
Other
1.USB connectors
Unknown. Help us offer a price.
With more USB ports, you can connect more devices.
2. USB Type-C
✔Nvidia GeForce RTX 2080 Ti Founders Edition
✖Nvidia Quadro 4000
USB Type-C has reversible connector orientation and cable routing.
Price Match
Cancel
Which graphics cards are better?
NVIDIA Quadro RTX 4000 Max-Q vs NVIDIA GeForce RTX 2080 Ti comparison which is better?
0003
76%
DeviceList Score
vs
NVIDIA GeForce RTX 2080 Ti
86%
DeviceList Score
and comparison table. Find out which one to choose in 2022.
NVIDIA Quadro RTX 4000 Max-Q Benefits
|
Power Demand (TDP) |
|
80 W -170 W (-68%) better than vs 250 W |
Benefits NVIDIA GeForce RTX 2080 Ti
Comparison winner
|
Number of shader processors |
|
4352 1792 (70%) better than vs 2560 |
|
Core frequency |
|
1350 MHz At 570 MHz (73. vs 780 MHz |
|
Boost frequency |
|
1545 MHz 165 MHz (12%) better than vs 1380 MHz |
|
Maximum memory |
|
11 GB 3 GB (37.5%) better than vs 8 GB |
|
Memory bus width |
|
352 bit 96 bits (37.5%) better than vs 256 bit |
|
Memory frequency |
|
14000 MHz 1000 MHz (7.7%) better than vs 13000 MHz |
|
Memory bandwidth |
|
616 200 (48.1%) better than vs 416 |
1%) better than | General information | |
|
Price-quality ratio The sum of all the advantages of the device divided by its price. |
|
| n/a | 0.21521522% |
|
Architecture |
|
| Turing | Turing |
|
Codename |
|
| TU104 | TU102 |
|
Type |
|
| Mobile workstation | Desktop |
|
Release price |
|
| n/a | 999 $ |
|
Number of shaders |
|
| 2560 | 4352
1792 (70%) better than |
|
Core clock |
|
| 780MHz | 1350 MHz
At 570 MHz (73.1%) better than |
|
Boost frequency |
|
| 1380 MHz | 1545 MHz
At 165 MHz (12%) better than |
|
Number of transistors |
|
| 13. |
18.600 million |
|
Process |
|
| 12 nm | 12 nm |
|
Interface |
|
| PCIe 3.0 x16 | PCIe 3.0 x16 |
|
Power Demand (TDP) Calculated thermal power shows the average heat dissipation in load operation, |
|
| 80W
-170 W (-68%) better than |
250 W |
|
Length |
|
| n/a | 267 mm |
|
Additional power connectors |
|
| no | 2x 8-pin |
|
G-SYNC Ready NVIDIA G-SYNC technology delivers a smooth gaming experience with variable refresh rates and the elimination of visual artifacts. |
|
|
Multi Monitor |
|
| + | + |
|
VR Ready Technology from NVIDIA that gives manufacturers access to Multi res Shading, Context Priority, and GPU Direct virtual reality technologies. |
|
| + | + |
|
Vulkan NVIDIA’s Vulkan technology allows developers to gain low-level access to the GPU to optimize graphics commands (better than OpenGL and Direct3D APIs). |
|
| + | + |
|
Video connectors |
|
| No outputs | 1x HDMI, 3x DisplayPort, 1x USB Type-C |
|
DirectX |
|
| 12 Ultimate (12_1) | 12 Ultimate (12_1) |
| Benchmarks |
| Memory | |
|
Memory type |
|
| GDDR6 | GDDR6 |
|
Maximum memory Large video memory allows you to run demanding games with lots of textures, |
|
| 8 GB | 11 GB
3 GB (37.5%) 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. |
|
| 256 bit | 352 bit
96 bit (37.5%) 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. |
|
| 13000 MHz | 14000 MHz
1000 MHz (7.7%) better than |
|
Memory bandwidth The greater the data transfer bandwidth, the more effective amount of RAM the PC can use. |
|
| 416 | 616
200 (48.1%) better than |
Comparison of NVIDIA GeForce RTX 3060 Ti and NVIDIA Quadro RTX 4000
Comparative analysis of NVIDIA GeForce RTX 3060 Ti and NVIDIA Quadro RTX 4000 video cards by all known characteristics in the categories: General information, Specifications, Video outputs and ports, Compatibility, dimensions, requirements, API support, Memory.
Analysis of video card performance by benchmarks: PassMark — G3D Mark, PassMark — G2D Mark, Geekbench — OpenCL, CompuBench 1.5 Desktop — Face Detection (mPixels/s), CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s), CompuBench 1.5 Desktop — T -Rex (Frames/s), CompuBench 1.5 Desktop — Video Composition (Frames/s), CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s), GFXBench 4.0 — Car Chase Offscreen (Frames), GFXBench 4.0 — Manhattan (Frames), GFXBench 4.0 — T-Rex (Frames), GFXBench 4.0 — Car Chase Offscreen (Fps), GFXBench 4.0 — Manhattan (Fps), GFXBench 4.0 — T-Rex (Fps), 3DMark Fire Strike — Graphics Score.
NVIDIA GeForce RTX 3060 Ti
versus
NVIDIA Quadro RTX 4000
Benefits
Reasons to choose NVIDIA GeForce RTX 3060 Ti
- Newer graphics card, release date difference 2 year(s) 0 month(s0) about 4%
more frequency : 1410 MHz vs 1005 MHz
- Boost core clock 8% faster: 1665 MHz vs 1545 MHz
- Texturing speed 14% faster: 253.
1 GTexel/s vs 222.5 GTexel/s
- Number of shader processors 2.1 times more: 4864 vs 2304
- Newer production process of the video card allows it to be more powerful, but with lower power consumption: 8 nm vs 12 nm
- Memory frequency is 8% higher: 1750 MHz (14 Gbps effective) vs 1625 MHz (13000 MHz effective)
- Approximately 50% more performance in Geekbench — OpenCL benchmark: 120183 vs 80254
- Performance in CompuBench 1.5 Desktop — Face Detection (mPixels/s) benchmark approximately 11 % over: 314.126 vs 282.628
- CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s) about 6% more performance: 3615.048 vs 3403.106
- CompuBench 1.5 Desktop — T-Rex (Frames/s) about 43% more performance: 35.311 2x more performance in CompuBench 1.5 Desktop — Video Composition (Frames/s) benchmark: 275.862 vs 136.919
- About 28% better performance in CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s) benchmark : 1297.279 vs 1010.818
- About 36% more performance in GFXBench 4.
0 — Car Chase Offscreen (Frames): 27478 vs 20206
- About 36% more performance in GFXBench 4.0 — Car Chase Offscreen (Fps) benchmark: 202027 vs 202027
- Performance in 3DMark Fire Strike — Graphics Score about 49% better: 11700 vs 7843
| Release date | 1 Dec 2020 vs 13 Nov 2018 |
| Core frequency | 1410 MHz vs 1005 MHz |
| Boost core clock | 1665 MHz vs 1545 MHz |
| Texturing speed | 253.1 GTexel/s vs 222.5 GTexel/s |
| Number of shader processors | 4864 vs 2304 |
| Process | 8nm vs 12nm |
| Memory frequency | 1750 MHz (14 Gbps effective) vs 1625 MHz (13000 MHz effective) |
| Geekbench — OpenCL | 120183 vs 80254 |
| CompuBench 1. |
314.126 vs 282.628 |
| CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s) | 3615.048 vs 3403.106 |
| CompuBench 1.5 Desktop — T-Rex (Frames/s) | 35.311 vs 24.719 |
| CompuBench 1.5 Desktop — Video Composition (Frames/s) | 275.862 vs 136.919 |
| CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s) | 1297.279 vs 1010.818 |
| GFXBench 4.0 — Car Chase Offscreen (Frames) | 27478 vs 20206 |
| GFXBench 4.0 — Manhattan (Frames) | 3717 vs 3714 |
| GFXBench 4. |
3360 vs 3359 |
| GFXBench 4.0 — Car Chase Offscreen (Fps) | 27478 vs 20206 |
| GFXBench 4.0 — Manhattan (Fps) | 3717 vs 3714 |
| GFXBench 4.0 — T-Rex (Fps) | 3360 vs 3359 |
| 3DMark Fire Strike — Graphics Score | 11700 vs 7843 |
Reasons to choose NVIDIA Quadro RTX 4000
- Approximately 25% less power consumption: 160 Watt vs 200 Watt
| Power consumption (TDP) | 160 Watt vs 200 Watt |
Benchmark comparison
GPU 1: NVIDIA GeForce RTX 3060 Ti
GPU 2: NVIDIA Quadro RTX 4000
| Geekbench — OpenCL |
|
|
||||
| CompuBench 1. |
|
|
||||
| CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s) |
|
|
||||
| CompuBench 1.5 Desktop — T-Rex (Frames/s) |
|
|
||||
| CompuBench 1.5 Desktop — Video Composition (Frames/s) |
|
|
||||
| CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s) |
|
|
||||
| GFXBench 4.0 — Car Chase Offscreen (Frames) |
|
|||||
| GFXBench 4.0 — Manhattan (Frames) |
|
|||||
| GFXBench 4.0 — T-Rex (Frames) |
|
|||||
| GFXBench 4. |
|
|||||
| GFXBench 4.0 — Manhattan (Fps) |
|
|||||
| GFXBench 4.0 — T-Rex (Fps) |
|
|||||
| 3DMark Fire Strike — Graphics Score |
|
| Name | NVIDIA GeForce RTX 3060 Ti | NVIDIA Quadro RTX 4000 |
|---|---|---|
| PassMark — G3D Mark | 20390 | |
| PassMark — G2D Mark | 981 | |
| Geekbench — OpenCL | 120183 | 80254 |
| CompuBench 1. |
314.126 | 282.628 |
| CompuBench 1.5 Desktop — Ocean Surface Simulation (Frames/s) | 3615.048 | 3403.106 |
| CompuBench 1.5 Desktop — T-Rex (Frames/s) | 35.311 | 24.719 |
| CompuBench 1.5 Desktop — Video Composition (Frames/s) | 275.862 | 136.919 |
| CompuBench 1.5 Desktop — Bitcoin Mining (mHash/s) | 1297.279 | 1010.818 |
| GFXBench 4.0 — Car Chase Offscreen (Frames) | 27478 | 20206 |
| GFXBench 4. |
3717 | 3714 |
| GFXBench 4.0 — T-Rex (Frames) | 3360 | 3359 |
| GFXBench 4.0 — Car Chase Offscreen (Fps) | 27478 | 20206 |
| GFXBench 4.0 — Manhattan (Fps) | 3717 | 3714 |
| GFXBench 4.0 — T-Rex (Fps) | 3360 | 3359 |
| 3DMark Fire Strike — Graphics Score | 11700 | 7843 |
Feature comparison
| NVIDIA GeForce RTX 3060 Ti | NVIDIA Quadro RTX 4000 | |
|---|---|---|
| Architecture | Ampere | Turing |
| Codename | GA104 | TU104 |
| Production date | 1 Dec 2020 | November 13, 2018 |
| Price at first issue date | $399 | $899 |
| Place in the rating | 24 | 89 |
| Type | Desktop | Desktop |
| Generation GCN | Quadro RTX | |
| Boost core clock | 1665 MHz | 1545 MHz |
| Core frequency | 1410MHz | 1005MHz |
| Process | 8nm | 12 nm |
| Peak Double Precision (FP64) Performance | 253. |
222.5GFLOPS |
| Peak Half Precision (FP16) Performance | 16.20 TFLOPS (1:1) | 14.24TFLOPS |
| Peak Single Precision (FP32) Performance | 16.20TFLOPS | 7.119TFLOPS |
| Number of shaders | 4864 | 2304 |
| Pixel fill rate | 133.2GPixel/s | 98.88 GPixel/s |
| Texturing speed | 253.1 GTexel/s | 222.5 GTexel/s |
| Power consumption (TDP) | 200 Watt | 160 Watt |
| Number of transistors | 17400 million | 13600 million |
| Render output units | 64 | |
| Texture Units | 144 | |
| Video connectors | 1x HDMI, 3x DisplayPort | 3x DisplayPort, 1x USB Type-C |
| Form factor | Dual slot | |
| Interface | PCIe 4. |
PCIe 3.0 x16 |
| Length | 242 mm (9.5 inches) | 9.5 inches (241 mm) |
| Recommended power supply | 350 Watt | |
| Additional power connectors | 1x 12-pin | 1x 8-pin |
| Width | 112 mm (4.4 inches) | |
| DirectX | 12.2 | 12.1 |
| OpenCL | 2.0 | 1.2 |
| OpenGL | 4. |
4.6 |
| Shader Model | 6.5 | 6.4 |
| Vulkan | ||
| Maximum memory size | 8GB | 8GB |
| Memory bandwidth | 448 GB/s | 416.0 GB/s |
| Memory bus width | 256bit | 256bit |
| Memory frequency | 1750 MHz (14 Gbps effective) | 1625 MHz (13000 MHz effective) |
| Memory type | GDDR6 | GDDR6 |
NVIDIA Introduces Quadro RTX 4000 Single Slot Design
NVIDIA has added another model to the Quadro RTX lineup. The first video cards were presented at the SIGGPRAPH conference this summer, after which the direction for the development of GeForce RTX video cards became clear. NVIDIA has put on hardware support for ray tracing. The presence of such support in the Turing architecture looks like a very logical step.
Thanks to the NVIDIA RTX and Microsoft DXR APIs, NVIDIA plans to get widespread support for ray tracing as soon as possible. At the Games Developer Conference this spring, NVIDIA, Microsoft and other partners announced software support that will bring real-time ray tracing to games. The corresponding graphics cards were announced this summer. Now GeForce RTX graphics cards have been on the market for almost two months, but so far not a single game has been released with support for RTX technologies.
With the Quadro RTX line, NVIDIA planned to solve the «chicken and egg» problem on the hardware side. The entry-level model Quadro RTX 4000 is now introduced. It relies on the same TU106 GPU as the gaming GeForce RTX 2070 (test).
| Model | Quadro RTX 8000 | Quadro RTX 6000 | Quadro RTX 5000 | Quadro RTX 4000 | |
| Price | — | 6.615 euro | 2.499 euros | 999 euro | |
| GPU | TU102 | TU102 | TU104 | TU106 | |
| Number of transistors | 18.6 billion | 18.6 billion | 13.6 billion | 10.8 billion | |
| Crystal area | 754 mm² | 754 mm² | 545 mm² | 445 mm² | |
| CUDA Cores | 4.608 | 4.608 | 3.072 | 2.304 | |
| Tensor cores | 576 | 576 | 384 | 288 | |
| RT cores | 72 | 72 | 48 | 36 | |
| Memory | 48GB GDDR6 | 24GB GDDR6 | 16 GB GDDR6 | 8GB GDDR6 | |
| Memory bus width | 384 bit | 384 bit | 256 bit | 256 bit | |
| Memory frequency | 1. |
1.750 MHz | 1.750 MHz | 1.625 MHz | |
| Memory bandwidth | 672 GB/s | 672 GB/s | 448 GB/s | 416 GB/s | |
| TDP | 295 W | 295 W | 295 W | 160 W | |
| Computing performance | |||||
|---|---|---|---|---|---|
| FP32 TFLOPS | 16.3 | 16.3 | 11.2 | 7.1 | |
| INT32 TIPS | 16.3 | 16.3 | 11.2 | 7.1 | |
| FP64 TFLOPS | 0.510 | 0.510 | 0.348 | 0.222 | |
| FP16 TFLOPS | 32.6 | 32.6 | 22.3 | 14.2 | |
| FP16 Tensor TFLOPS with FP16 multiplication | 130.5 | 130.5 | 89.2 | 60 | |
| FP16 Tensor TFLOPS with FP32 multiplication | 130. |
130.5 | 89.2 | 30 | |
| INT8 Tensor TOPS | 261 | 261 | 178.4 | 120 | |
| INT4 Tensor TOPS | 522 | 522 | 356.8 | 240 | |
Previously, NVIDIA only announced Quadro models based on TU102 and TU104 GPUs. Moreover, NVIDIA used the full versions of GPU data, while they were cut down on GeForce RTX video cards. However, the GeForce RTX 2070 uses the full TU106 GPU, just like the Quadro RTX 4000.
So here we get 2.304 CUDA blocks or stream processors. The number of Tensor cores is 288, the new RT cores are 36. Which corresponds to the GeForce RTX 2070 specifications. The same goes for the 256-bit memory interface. The GPU is connected to 8 GB of GDDR6 memory with a clock speed of 1.625 MHz and a bandwidth of 416 GB / s.
In principle, the TU106 GPU can be called a «half» of the TU102 GPU, so the computational performance is about half as much. NVIDIA is positioning the Quadro RTX 4000 as an entry-level solution for designers, artists and animators who want to get familiar with the RTX technologies and features of the new Quadro line.
The
Quadro RTX 4000 will be available directly from NVIDIA in December for around $900 or 1,000 Euros. The cards will be available to Dell, HPI and Lenovo system integrators, as well as PNY.
NVIDIA Quadro RTX 4000 Mobile Graphics Card Specifications and Benchmarks
NVIDIA started selling the Quadro RTX 4000 on May 27, 2019. This is a graphics card for mobile workstations based on the Turing architecture with a 12 nm process technology. It has 8 GB of GDDR6 memory with a frequency of 1750 MHz, a 256-bit bus, which provides a bandwidth of 14 Gb / s.
Connected via PCIe 3.0 x16 interface. The card does not require additional power supply, the declared maximum power consumption is 110 W.
Specifications
GPU
- GPU name
- TU104
- GPU option
- N19E-Q3-A1
- Architecture
- Turing
- Manufacturer
- TSMC
- Process
- 12 nm
- Number of transistors
- 13600 million
- Crystal area
- 545 mm²
Graphic card
- Issue date
- May 27, 2019
- Generation
- Quadro Mobile (Tx000)
- Data bus interface
- PCIe 3.
0 x16
Frequencies
- Base frequency
- 1110 MHz
- Boost frequency
- 1560 MHz
- Memory frequency
- 1750 MHz
Memory
- Memory capacity
- 8 GB
- Memory type
- GDDR6
- Memory bus
- 256 bit
- Memory speed
- 14 Gb/s
- Memory bandwidth
- 448 GB/s
Render configuration
- Shader units
- 2560
- Texture blocks
- 160
- Raster blocks
- 64
- Streaming multiprocessors
- 40
- Tensor cores
- 320
- RT Core
- 40
- L1 cache
- 64 KB
- L2 cache
- 4 MB
Rated output
- Pixel fill rate
- 99.
84 GP/s
- Texture Fill Rate
- 249.6 GT/s
- Performance FP16
- 15.97 Tflops
- Performance FP32
- 7.987 Tflops
- Performance FP64
- 249.6 GFlops
Graphics
- DirectX
- 12 Ultimate (12_2)
- OpenGL
- 4.6
- OpenCL
- 1.2
- Vulcan
- 1.2
- CUDA
- 7.5
- Shader Model
- 6.5
Video Card Design
- Heat Sink Requirements
- 110W
- Outlets
- None
- Power supply
- Not required
Game FPS
The Witcher 3
(2015)
Better than NVIDIA GeForce RTX 2070 Mobile, but worse than NVIDIA GeForce RTX 2070 Super Max-Q.
|
1024×768 / Low / 324 |
1366×768 / Medium / 234.5 |
1920×1080 / Tall / 142.5 |
1920×1080 / Ultra / 74.5 |
3840×2160 / Tall / 51 |
3840×2160 / Ultra / 51 |
F1 2020
(2020)
Better than NVIDIA GeForce RTX 2070, but worse than NVIDIA GeForce RTX 2060.
|
1280×720 / Low / 283 |
1920×1080 / Medium / 207 |
1920×1080 / Tall / 171 |
1920×1080 / Ultra / 121 |
2560×1440 / Ultra / 89 |
3840×2160 / Ultra / 50 |
Anno 1800
(2019)
Better than NVIDIA GeForce GTX 1660 Ti Mobile, but worse than NVIDIA GeForce RTX 2080 Ti.
|
1920×1080 / Medium / 98 |
1920×1080 / Tall / 77.5 |
1920×1080 / Ultra / 42.6 |
2560×1440 / Ultra / 37.7 |
3840×2160 / Ultra / 22.4 |
The Division 2
(2019)
Better than NVIDIA GeForce GTX 1660 SUPER, but worse than NVIDIA GeForce GTX 1070 Mobile.
|
1280×720 / Low / 180 |
1920×1080 / Medium / 122 |
1920×1080 / Tall / 96 |
1920×1080 / Ultra / 70 |
2560×1440 / Ultra / 47 |
3840×2160 / Ultra / 25 |
Dirt Rally 2. 0
(2019)
Better than AMD Radeon RX 570, but worse than NVIDIA GeForce RTX 2070 Super Max-Q.
|
1280×720 / Low / 267 |
1920×1080 / Medium / 180.7 |
1920×1080 / Tall / 151 |
1920×1080 / Ultra / 85.6 |
2560×1440 / Ultra / 63.3 |
Far Cry New Dawn
(2019)
Better than NVIDIA GeForce RTX 2060 SUPER, but worse than AMD Radeon RX 5600 XT.
|
1280×720 / Low / 121 |
1920×1080 / Medium / 103 |
1920×1080 / Tall / 101 |
1920×1080 / Ultra / 91 |
2560×1440 / Ultra / 77 |
2560×1440 / Ultra / 77 |
3840×2160 / Ultra / 43 |
3840×2160 / Ultra / 42. |
Battlefield V
(2018)
Better than NVIDIA GeForce GTX 1060 6GB, but worse than NVIDIA GeForce RTX 2070 Max-Q.
|
1280×720 / Low / 116.7 |
1920×1080 / Medium / 100.6 |
1920×1080 / Tall / 86.6 |
1920×1080 / Ultra / 81 |
2560×1440 / Ultra / 66 |
2560×1440 / Ultra / 65. |
3840×2160 / Ultra / 42 |
3840×2160 / Ultra / 41.8 |
Hitman 2
(2018)
Better than AMD Radeon RX 5700 XT, but worse than NVIDIA GeForce GTX 1660 SUPER.
|
1280×720 / Low / 95.4 |
1920×1080 / Medium / 93.6 |
1920×1080 / Tall / 85.8 |
1920×1080 / Ultra / 81. |
2560×1440 / Ultra / 72.9 |
3840×2160 / Ultra / 39.4 |
Assassin’s Creed Odyssey
(2018)
Better than NVIDIA GeForce GTX 1660 Ti, but worse than NVIDIA GeForce GTX 1070.
|
1280×720 / Low / 99 |
1920×1080 / Medium / 87 |
1920×1080 / Tall / 75 |
1920×1080 / Ultra / 54 |
2560×1440 / Ultra / 41 |
2560×1440 / Ultra / 41 |
3840×2160 / Ultra / 28 |
3840×2160 / Ultra / 28 |
Shadow of the Tomb Raider
(2018)
Better than AMD Radeon RX Vega 56, but worse than NVIDIA GeForce RTX 2080 Max-Q.
|
1280×720 / Low / 138.6 |
1920×1080 / Medium / 105.2 |
1920×1080 / Tall / 81.6 |
1920×1080 / Ultra / 85 |
2560×1440 / Tall / 57 |
2560×1440 / Ultra / 57.1 |
3840×2160 / Tall / 30 |
3840×2160 / Ultra / 29. |
Far Cry 5
(2018)
Better than NVIDIA GeForce GTX 1070, but worse than NVIDIA GeForce RTX 3060 Laptop GPU.
|
1280×720 / Low / 129 |
1920×1080 / Medium / 106 |
1920×1080 / Tall / 100 |
1920×1080 / Ultra / 96 |
2560×1440 / Ultra / 69 |
2560×1440 / Ultra / 69 |
3840×2160 / Ultra / 36 |
3840×2160 / Ultra / 36 |
X-Plane 11. 11
(2018)
Better than NVIDIA GeForce RTX 2070 Super Max-Q, but worse than NVIDIA GeForce GTX 1650.
|
1280×720 / Low / 120.5 |
1920×1080 / Medium / 108.5 |
1920×1080 / Tall / 89.1 |
3840×2160 / Ultra / 76.6 |
Rise of the Tomb Raider
(2016)
Better than NVIDIA GeForce GTX 1660 SUPER, but worse than NVIDIA GeForce RTX 2070 SUPER.
|
1366×768 / Medium / 199. |
1920×1080 / Tall / 127.8 |
1920×1080 / Ultra / 104.9 |
3840×2160 / Ultra / 45.1 |
Dota 2 Reborn
(2015)
Better than NVIDIA GeForce RTX 3070 Laptop GPU, but worse than NVIDIA Quadro T2000 Max-Q.
|
1280×720 / Low / 149 |
1366×768 / Medium / 137.5 |
1920×1080 / Tall / 131. |
1920×1080 / Ultra / 126.5 |
3840×2160 / Ultra / 105.5 |
Just Cause 4
(2018)
Better than NVIDIA GeForce GTX 1660 SUPER, but worse than NVIDIA GeForce RTX 2070 Mobile.
|
1280×720 / Low / 150 |
1920×1080 / Medium / 125 |
1920×1080 / Tall / 93 |
1920×1080 / Ultra / 86 |
2560×1440 / Ultra / 60 |
3840×2160 / Ultra / 33 |
Darksiders III
(2018)
Better than NVIDIA GeForce GTX 1080 Max-Q, but worse than NVIDIA TITAN RTX.
|
1920×1080 / Medium / 143.8 |
1920×1080 / Tall / 119.2 |
1920×1080 / Ultra / 105.2 |
2560×1440 / Ultra / 69.1 |
3840×2160 / Ultra / 34.2 |
F1 2018
(2018)
Better than NVIDIA GeForce GTX 1070, but worse than NVIDIA GeForce RTX 2080.
|
1280×720 / Low / 241 |
1920×1080 / Medium / 180 |
1920×1080 / Tall / 142 |
1920×1080 / Ultra / 95 |
2560×1440 / Ultra / 76 |
3840×2160 / Ultra / 48 |
Ghost Recon Wildlands
(2017)
Better than NVIDIA GeForce GTX 970, but worse than NVIDIA GeForce GTX 1070 Ti.
|
1280×720 / Low / 139.9 |
1920×1080 / Medium / 98 |
1920×1080 / Tall / 90.8 |
1920×1080 / Ultra / 52.9 |
3840×2160 / Ultra / 35 |
For Honor
(2017)
Better than AMD Radeon RX Vega 56, but worse than NVIDIA GeForce GTX 1070 Mobile.
|
1280×720 / Low / 289 |
1920×1080 / Medium / 148 |
1920×1080 / Tall / 141 |
1920×1080 / Ultra / 109 |
3840×2160 / Ultra / 45. |
Benchmark tests
3DMark Cloud Gate GPU: 119052 Better than NVIDIA GeForce RTX 2060 but worse than NVIDIA GeForce RTX 2060 SUPER.
3DMark Cloud Gate Standard Score: 38830 Better than NVIDIA GeForce GTX 1080 SLI (mobile), but worse than NVIDIA GeForce GTX 1650.
3DMark Fire Strike Graphics: 18849 Better than NVIDIA RTX A5000 Laptop GPU, but worse than NVIDIA Quadro RTX 5000 Mobile.
3DMark Fire Strike Score: 16903 Better than NVIDIA GeForce GTX 1080 but worse than AMD Radeon RX Vega 56.
3DMark Ice Storm GPUs: 445161 Better than NVIDIA GeForce RTX 2070 Mobile, but worse than NVIDIA GeForce GTX 1660 Ti.
3DMark Time Spy Graphics: 7284 Better than NVIDIA GeForce GTX 1080 but worse than NVIDIA GeForce RTX 2070 Super Max-Q.
3DMark Time Spy Score: 7362 Better than AMD Radeon RX Vega 64 but worse than NVIDIA GeForce RTX 2080 Max-Q.
3DMark Vantage P: 56250 Better than AMD Radeon RX Vega 64, but worse than NVIDIA GeForce GTX 1650 SUPER.
3DMark11 P: 21595 Better than NVIDIA GeForce RTX 3060 Laptop GPU, but worse than NVIDIA Quadro P5200.
3DMark11 P GPU: 25370.5 Better than NVIDIA GeForce GTX 1070, but worse than NVIDIA GeForce GTX 980 SLI (mobile).
Cinebench R10 32Bit OpenGL: 6824 Better than NVIDIA Quadro K610M, but worse than NVIDIA Quadro K3100M.
Cinebench R15 OpenGL 64Bit: 215.5 Better than NVIDIA Quadro RTX 4000 Max-Q, but worse than NVIDIA Quadro T2000 Max-Q.
ComputeMark v2.1 Normal, Score: 13576 Better than NVIDIA GeForce GTX 1070 but worse than NVIDIA RTX A2000 Mobile.
GFXBench: 1213 Better than NVIDIA Quadro P5000, but worse than NVIDIA Quadro RTX 5000 Max-Q.
GFXBench 3.0 1080p Manhattan Offscreen: 490.4 Better than NVIDIA GeForce GTX 980 Ti but worse than NVIDIA GeForce RTX 2060 Max-Q.
GFXBench 3.0 Manhattan Offscreen OGL: 490.4 Better than NVIDIA GeForce GTX 980 Ti but worse than NVIDIA GeForce RTX 2060 Max-Q.
GFXBench 3.1 Manhattan ES 3.1 Offscreen: 440.5 Better than NVIDIA GeForce GTX 1080 Max-Q, but worse than NVIDIA Quadro RTX 5000 Max-Q.
LuxMark v2.0 64Bit Sala GPUs-only: 5927 Better than NVIDIA GeForce GTX 980 SLI Mobile but worse than NVIDIA RTX A3000 Mobile.
Passmark: 13335 Better than NVIDIA Titan X Pascal, but worse than NVIDIA GeForce GTX 1070.
SPECviewperf 12 — Catia: 162 Better than AMD Radeon RX 5700 XT but worse than NVIDIA Quadro P5200.
SPECviewperf 12 — Creo: 141 Better than NVIDIA Quadro RTX 5000, but worse than NVIDIA Quadro P5200.
SPECviewperf 12 — Maya: 144 Better than NVIDIA GeForce GTX 1080, but worse than NVIDIA GeForce GTX 1080 Mobile.
SPECviewperf 12 — Medical: 62 Better than NVIDIA GeForce GTX 1080 Ti, but worse than NVIDIA Quadro RTX 5000 Max-Q.
SPECviewperf 12 — Showcase: 98 Better than NVIDIA GeForce GTX 1080, but worse than NVIDIA GeForce RTX 2060.
SPECviewperf 12 — Siemens NX: 186 Better than NVIDIA Quadro P5000 (mobile), but worse than NVIDIA Quadro P5200.
SPECviewperf 12 — Solidworks: 149 Better than NVIDIA Quadro RTX 5000 Max-Q, but worse than NVIDIA Quadro P5200.
Unigine Valley 1.0 Extreme HD DirectX: 89. 9 Better than NVIDIA GeForce GTX 1080 Max-Q, but worse than AMD Radeon RX 5600 XT.
Comparison with other graphics cards
Map 1:
Map 2:
Video reviews and tests
Error 403 The request cannot be completed because you have exceeded your quota. : quotaExceeded
If you find an error or have something to add, write in the comments. Have you had any experience with this video card? Is it worth buying such a card today?
Details revealed about the NVIDIA Ada Lovelace graphics core that will power GeForce RTX 4000 series graphics cards
©
KornEr
News
NVIDIA Ada Lovelace GPU architecture information has been leaked for a while now, specific configurations will use next generation AD10* series chips for GeForce RTX 40 series graphics cards which have also been leaked. Now we can talk exclusively about the next generation graphics chip itself.
NVIDIA GA102 Ampere Block Diagram
Network detective Kopte7kimi shared details on the next generation architecture block diagram, he compares the top AD102 GPU with various other NVIDIA GPUs.
Namely Ampere GA102 and Turing TU102, focused on games, while the Hopper Gh200 and Ampere GA100 are added to the list, focused on high performance workstations. The comparison only compares the AD102 to its gaming predecessors, as the super system-oriented chips are very different from the consumer-oriented offerings.
NVIDIA AD102 Ada Lovelace
Block Diagram The NVIDIA Ada Lovelace AD102 GPU will have up to 12 Graphics Processing Clusters (GPCs). This is an increase of 70% of compared to GA102 which only has 7 GPCs. Each chip will consist of 6 TPCs and 2 SMS, which come in the same configuration as the existing chip. Each streaming multiprocessor (SM) will contain four sub-core processors, which are also the same as the GA102 GPU.
What has changed is the FP32 and INT32 core configuration. Each sub-core will include 128 FP32 blocks, but combined FP32 + INT32 blocks increased to 192 . This is because FP32 blocks do not have the same sub-core as IN32 blocks. The 128 FP32 cores are separated from the 64 INT32 cores.
So in total each sub-core will consist of 128 FP32 units plus 64 INT32 units for a total of 192 units. Each SM will have a total of 512 FP32 units plus 256 INT32 units for a total of 768 units. And since there are a total of 24 SM units (2 per GPC), that works out to 12,288 FP32 units and 6,144 INT32 units for a total of 9 cores.1190 18432. Each SM will also include two processing circuits (32 threads / CLK) for 64 calculations per SM. This is an increase of 50% cores (FP32 + INT32) and an increase of 33% at cores/threads compared to GA102.
NVIDIA Preliminary Specs Ada Lovelace
NVIDIA has made a big leap in cache manipulation over existing Ampere GPUs. Ada Lovelace will contain 192 KB cache L1 on SM, which is 50% more than Ampere. That’s a total of 4.5MB cache L1 on the top AD102 GPU. Cache L2 will be increased to 96MB as mentioned in the leaks. This is a 16x increase over the Ampere GPU which contains a total of 6MB cache L2 and it will be shared between the GPU.
There is also data on the elements responsible for writing pixels to memory (ROPS), which are also increased to 32 on the GPC, 2 times increased compared to Ampere. The next generation flagship will have up to ,384, ROPs versus just 112 on the fastest Ampere GPU in the Geforce RTX 3090 Ti.
In addition, Ada Lovelace GPUs will feature the latest 4th Gen Tensor and 3rd Gen RT (Raytracing) cores to help push DLSS and Raytracing performance to the next level.