Nvidia RTX 2080 Super vs. RTX 2080 vs. RTX 2070 Super
Digital Trends may earn a commission when you buy through links on our site. Why trust us?
The RTX 2080 Super is more powerful, but is the RTX 2070 Super a better value?
By
Jon Martindale
Dan Baker/Digital Trends
Nvidia’s RTX graphics cards might have stiff competition from AMD’s RX 5700 cards, but at the top end it still rules the roost when it comes to performance. With Super versions of the RTX 2070 and 2080 offering better value than ever before, it’s a great time to buy a new graphics card. But which should you pick?
Contents
- Performance
- Ray tracing and DLSS
- The 2070 Super is king, unless you have deep pockets
To see which represents the best high-end GPU offering out there, we pitted the RTX 2080 Super vs. RTX 2080 vs. RTX 2070 Super.
Want a broader selection of GPUs? Here are the best graphics cards you can buy right now.
Performance
Riley Young/Digital Trends
We’ve had our hands on almost every RTX graphics card since they released, including the latest of the Nvidia Turing refresh cards, the RTX 2080 Super. Before we look at how they perform in the real world, let’s take a look at the specifications, which paint a pretty clear picture of what we can expect from these cards.
| RTX 2080 Ti | RTX 2080 Super | RTX 2080 | RTX 2070 Super | RTX 2070 | RTX 2060 Super | RTX 2060 | |
| GPU | TU102 | TU104 | TU104 | TU104 | TU106 | TU106 | TU106 |
| CUDA cores | 4,352 | 3,072 | 2,944 | 2,560 | 2,304 | 2,176 | 1,920 |
| Tensor cores | 544 | 384 | 368 | 320 | 288 | 272 | 240 |
| RT Cores | 68 | 48 | 46 | 40 | 36 | 34 | 30 |
| Base clock | 1,350MHz | 1,650MHz | 1,515MHz | 1,605MHz | 1,410MHz | 1,470MHz | 1,365Mhz |
| Boost clock | 1,545MHz | 1,815MHz | 1,710MHz | 1,770MHz | 1,620MHz | 1,650MHz | 1,680MHz |
| Memory | 11GB GDDR6 | 8GB GDDR6 | 8GB GDDR6 | 8GB GDDR6 | 8GB GDDR6 | 8GB GDDR6 | 6GB GDDR6 |
| Memory speed | 14 Gbps | 15. 5Gbps |
14Gbps | 14Gbps | 14Gbps | 14Gbps | 14Gbps |
| Bandwidth | 616 GBps | 496GBps | 448GBps | 448GBps | 448GBps | 448GBps | 336GBps |
| TDP | 250w | 250w | 215w | 215w | 175w | 175w | 160w |
| Price | $1,100 | $699 | $699 | $500 | $500 | $400 | $350 |
Like the RTX 2070 Super and RTX 2060 Super before it, the RTX 2080 Super saw a modest increase in CUDA cores, along with a bump to its boost clock speed by more than 100MHz. But it also saw a jump in its memory speed, which helped push its overall bandwidth close to 500GBps. All of that does come at the cost of thermals and power draw though, with the RTX 2080 Super now rated at the same 250w as the 2080 Ti.
The 2070 Super still falls behind the stock 2080, although its improved boost clock and CUDA core count over the stock 2070 helps narrow that gap considerably.
As with all computer hardware, though, the specifications only tell us part of the story. When we got to grips with these new Turing GPUs in the real world, the performance of the 2080 Super, 2080, and 2070 Super are much closer than we’d have liked to have seen.
The 2080 Super is undeniably the most powerful card of the three, but the margins aren’t as wide as we expected. The fact that the 2080 Super is sold at $100 cheaper than the original 2080’s launch price is the only real saving grace for it. You get more power for less money, which is always a good deal. That is, except when the 2070 Super is so close in performance to the original 2080 and a full $200 less than the new Super variant.
The 2070 Super is arguably the best bang for buck card in the entire RTX lineup. It outperforms AMD’s RX 5700 XT, quite often defeats the $650 Radeon VII, and it can handle RTX features like ray tracing and deep learning super sampling (DLSS).
Ray tracing and DLSS
Along with bumps in clock speed and CUDA core count, Nvidia’s new Super cards also increased the number of the RT and Tensor cores which enable ray tracing and DLSS respectively, on its RTX GPUs.
Although it wasn’t huge, the RTX 2070 Super saw an increase of 11% in RT cores and Tensor cores. While that won’t make it much easier to run the top-tier ray-tracing effects, it should help diminish the performance impact ray tracing can have.
On the other hand, the RTX 2080 Super’s RT and Tensor core counts only increased by just over 4%. That’s negligible enough that we didn’t see any real improvement in ray tracing or DLSS performance. More is better in this case and it’s certainly an improvement over the stock 2080, but the gap between the 2070 Super and 2080 Super is considerably narrower on this front than it was between the 2070 and 2080, making the 2070 Super, again, more of an upgrade over its non-Super variant than the 2080 Super.
The 2070 Super is king, unless you have deep pockets
Dan Baker/Digital Trends
The RTX Super cards are all an improvement over their predecessors and unanimously represent better value for money because of it. That said, there are cards that represent greater upgrades than others and the RTX 2080 Super just isn’t one of them.
While the raw performance crown in this head to head goes to the RTX 2080 Super, the 2070 Super just offers much more value for money. If you can find an RTX 2080 at a lower price as retailers clear stock, that might make it a worthwhile buy. But if you’re at all interested in bang for the buck, save yourself $200 and grab a 2070 Super.
Editors’ Recommendations
-
How to watch Nvidia’s RTX 4090 launch at GTC 2022 (and what to expect)
-
EVGA is done making GPUs, and reports say it’s because of Nvidia
-
The best VR headsets
-
Nvidia RTX 40-series will let you ramp up the power draw for more performance
-
The best OLED laptops for 2022
Nvidia RTX 2070 Super vs 2080 Super: How much faster is Nvidia’s new 4K graphics card?
Nvidia’s RTX 2080 Super card is finally here. Offering superior speeds for roughly the same price as the original RTX 2080, the RTX 2080 Super is pretty much the 4K graphics card to beat right now outside of Nvidia’s crazy expensive RTX 2080 Ti — especially as it currently has no real competition from the likes of AMD right now, either.
In fact, its closest rival is Nvidia’s own £485 / $500 RTX 2070 Super. But how much faster is the RTX 2080 Super, and is it worth spending another two hundred quid on it? Let’s find out via the medium of some lovely bar charts.
To see this content please enable targeting cookies.
RTX 2070 Super vs 2080 Super: How we test
Like my usual comparison articles, the aim here is to see how all both cards stack up across a variety of resolutions and graphics settings. This time, I’ve only included my 4K and 2560×1440 results because, let’s face it, no one should be buying either of these cards for playing games at 1920×1080. There are plenty of cards that can do that for a fraction of the cost of these high-end behemoths, such as our current champ, the Nvidia GeForce GTX 1660 Ti.
In fact, buying either of these Super cards for 1440p gaming is still a bit of an extravagance if you ask me, but I’ve included these benchmarks anyway as the RTX 2070 Super sits pretty much on the border of being a top-notch 1440p card and an entry-level 4K jobber.
To test each card, I paired them with my Intel Core i7-8700K CPU and 16GB of Corsair Vengeance 2133MHz RAM and put them through my general games benchmarking suite, taking an average frame rate from either their own built-in benchmark tools or from my own repeated manual gameplay tests. The games includes Shadow of the Tomb Raider, Total War: Three Kingdoms, Final Fantasy XV, Monster Hunter: World, The Witcher III, Assassin’s Creed Odyssey, Metro Exodus and Forza Horizon 4.
For this particular test, I’ve used the Nvidia Founders Editions of each card, as these were the ones sent to me for review. Both run at their stock reference speeds, so they should be fairly representative of their respective card categories. With all that in mind, then, let’s get down to those tasty bar charts.
RTX 2070 Super vs 2080 Super: 4K benchmarks
Starting at the deep-end, then, here’s how each card stacks up when faced with 4K Ultra settings across some of today’s toughest games.
Needless to say, neither are really fit for playing games at this kind of quality setting unless a) it’s an old game like The Witcher III or b) incredibly well optimised like Forza Horizon 4.
That said, both of them still manage an average of at least 30fps across the board here, which is still pretty impressive all things considered. Still, in the case of the RTX 2070 Super, you’re still seeing lows well below that in both Total War: Three Kingdoms (26fps) and Monster Hunter: World (28fps), which isn’t exactly ideal.
Moving down to High quality settings (and eliminating the games that could already hit 60fps on Ultra), both cards offer much more playable speeds here, with all but one of the RTX 2070 Super’s average frame rates sitting comfortably above 40fps. However, while the the RTX 2080 Super is perhaps only an average of 5-6fps faster in a lot of cases here, it’s precisely around this kind of mid-40s mark where a small boost like this can make all the difference between something that’s just about playable and something that’s actually pretty all right.
Final Fantasy XV, for example, felt noticeably smoother on the RTX 2080 Super here, as did Monster Hunter: World and Metro Exodus. Plus, once you enable each game’s DLSS support (which all three games now have, by the way), you’re able to get much closer to a perfect 60fps with the RTX 2080 Super than you are with the RTX 2070 Super. Take Final Fantasy XV, for example. Whereas the RTX 2070 Super was only able to reach an average of 53fps with DLSS enabled on High with all of its fancy Nvidia effects turned off, the RTX 2080 Super pushed that all the way up to 62fps.
As for Medium settings at 4K, the RTX 2070 Super is just about able to reach average frame rates between 50-60fps here, but it’s the RTX 2080 Super that’s able to hit 60fps much more consistently. Admittedly, most 4K screens max out at 60Hz these days, so the benefit you’re going to get from an average of, say, 69fps in Total War: Three Kingdoms, is almost certainly going to be lost on you due to the limitations of your gaming monitor.
The same goes for Assassin’s Creed Odyssey.
However, while you may not feel the benefit of these particular games right now, the RTX 2080 Super will almost certainly stand you in better stead further down the line when games start getting even tougher to play at 4K. If I were buying a 4K graphics card right now, I think I’d probably almost certainly go with the 2080. I wouldn’t enjoy it, because come on, no one really wants to spend almost 700 quid on a graphics card, but when the only other alternative is buying a card that only just about do Medium settings now doesn’t exactly fill me with a lot of confidence.
RTX 2070 Super vs 2080 Super: 1440p benchmarks
If you’re mainly buying a card for flawless 2560×1440 gaming, however, then the RTX 2070 Super is definitely more than enough right now. Able to hit a consistent 60fps in practically ever game going (or damn well near it), the only possible reason why you might want to upgrade to an RTX 280 Super here is if you have a high refresh rate gaming monitor — but even then I’m not sure the boost you gain here is really worth it.
As for that rather low-looking Final Fantasy XV result, this is with all of Nvidia’s fancy pants effects like HairWorks, TurfEffects, VXAO and ShadowLibs switched on, because this is the kind of calibre card you need in order to do it properly at this resolution. With everything switched off, you’re looking at an average of 71fps for the RTX 2070 Super and 82fps for the 2080 Super.
RTX 2070 Super vs 2080 Super: Conclusion
Ultimately, then, it all comes down to what resolution you’re trying to hit. If you’ve only got a 2560×1440 gaming monitor, then there’s absolutely no need to spend £669 / $699 on the RTX 2080 Super. Instead, go with the significantly cheaper £485 / $499 RTX 2070 Super.
However, if you’ve got your sights set on 4K, then you’ll probably thank yourself later for spending that extra cash, however much it’s going to bruise your wallet in the short term. I know it’s a big ask over the RTX 2070 Super, but as I mentioned above, I’m just not sure it’s particularly wise to buy a 4K graphics card that can only just about handle Medium settings at the moment, as that kind of quality level is only going to deteriorate further as the years roll on — especially if the current crop of confirmed ray tracing games all end up requiring the same kind of intense PC requirements as Remedy’s upcoming Control, too.
The only real question is whether the RTX 2080 Super will eventually face any competition from AMD’s new Navi GPUs. At time of writing, we’ve only seen the RX 5700 and RX 5700 XT come out so far, and both of them are more 1440p cards than proper 4K jobbers — as you can see from my big RTX 2060 vs RX 5700 vs RTX 2060 Super vs RX 5700 XT comparison piece — so it’s entirely possible there might be another high-end card waiting in the wings somewhere that offers more or less comparable performance to the RTX 2080 Super for less money (just like the RX 5700 XT does with the RTX 2070 Super in my RTX 2070 vs 2070 Super vs RX 5700 XT comparison). It’s just too early to say.
There is, of course, still AMD’s Radeon 7 to take into account, although considering that could barely keep up with the original RTX 2080 (as you can see from my Radeon 7 vs RTX 2080 article), it can’t really hold a candle to Nvidia’s similarly-priced Super-charged successor.
As a result, if you’re buying a 4K graphics card right now, then the RTX 2080 Super is pretty much the only way to go in my eyes, making it my new ‘what you should actually buy’ recommendation over in our graphics cards rankings.
NVIDIA GeForce RTX 2080 Super Mobile vs NVIDIA GeForce RTX 2070 Super Mobile
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 18. 04:05:38
#0 checking url part for id 10231 +0s … 0s
#1 checking url part for id 10229 +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 Sat, 17 Sep 2022 17:27:01 +0200 +0s … 0s
#4 linkCache_getLink using $NBC_LINKCACHE +0.051s … 0.052s
#5 linkCache_getLink using $NBC_LINKCACHE +0.
002s … 0.054s
#6 linkCache_getLink using $NBC_LINKCACHE +0s … 0.054s
#7 linkCache_getLink using $NBC_LINKCACHE +0s … 0.054s
#8 linkCache_getLink using $NBC_LINKCACHE +0s … 0.054s
#9 linkCache_getLink using $NBC_LINKCACHE +0s … 0.054s
#10 linkCache_getLink using $NBC_LINKCACHE +0s … 0.054s
#11 linkCache_getLink using $NBC_LINKCACHE +0s … 0.054s
#12 linkCache_getLink using $NBC_LINKCACHE +0s … 0.054s
#13 linkCache_getLink using $NBC_LINKCACHE +0s … 0.054s
#14 linkCache_getLink using $NBC_LINKCACHE +0s … 0.054s
#15 linkCache_getLink using $NBC_LINKCACHE +0s … 0.054s
#16 linkCache_getLink using $NBC_LINKCACHE +0s … 0.054s
#17 linkCache_getLink using $NBC_LINKCACHE +0s … 0.054s
#18 linkCache_getLink using $NBC_LINKCACHE +0s … 0.054s
#19 linkCache_getLink using $NBC_LINKCACHE +0s … 0.
054s
#20 linkCache_getLink using $NBC_LINKCACHE +0s … 0.054s
#21 linkCache_getLink using $NBC_LINKCACHE +0s … 0.054s
#22 linkCache_getLink using $NBC_LINKCACHE +0s … 0.054s
#23 composed specs +0s … 0.054s
#24 did output specs +0s … 0.054s
#25 start showIntegratedCPUs +0s … 0.054s
#26 getting avg benchmarks for device 10231 +0.025s … 0.079s
#27 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.079s
#28 got single benchmarks 10231 +0.015s … 0.094s
#29 getting avg benchmarks for device 10229 +0s … 0.095s
#30 linkCache_getLink using $NBC_LINKCACHE +0s … 0.095s
#31 linkCache_getLink no uid found +0.004s … 0.1s
#32 got single benchmarks 10229 +0.015s … 0.115s
#33 got avg benchmarks for devices +0s … 0.115s
#34 linkCache_getLink no uid found +0.001s … 0.116s
#35 linkCache_getLink no uid found +0s .
.. 0.116s
#36 linkCache_getLink no uid found +0s … 0.116s
#37 linkCache_getLink no uid found +0s … 0.117s
#38 linkCache_getLink no uid found +0s … 0.117s
#39 linkCache_getLink using $NBC_LINKCACHE +0s … 0.117s
#40 linkCache_getLink using $NBC_LINKCACHE +0s … 0.117s
#41 linkCache_getLink using $NBC_LINKCACHE +0s … 0.117s
#42 linkCache_getLink using $NBC_LINKCACHE +0s … 0.117s
#43 linkCache_getLink using $NBC_LINKCACHE +0s … 0.117s
#44 linkCache_getLink using $NBC_LINKCACHE +0s … 0.117s
#45 linkCache_getLink no uid found +0s … 0.117s
#46 linkCache_getLink using $NBC_LINKCACHE +0s … 0.117s
#47 linkCache_getLink using $NBC_LINKCACHE +0s … 0.117s
#48 linkCache_getLink using $NBC_LINKCACHE +0s … 0.117s
#49 linkCache_getLink no uid found +0s … 0.117s
#50 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.117s
#51 linkCache_getLink no uid found +0s … 0.117s
#52 linkCache_getLink using $NBC_LINKCACHE +0s … 0.117s
#53 linkCache_getLink no uid found +0s … 0.117s
#54 linkCache_getLink no uid found +0s … 0.117s
#55 linkCache_getLink using $NBC_LINKCACHE +0s … 0.118s
#56 linkCache_getLink using $NBC_LINKCACHE +0s … 0.118s
#57 linkCache_getLink using $NBC_LINKCACHE +0s … 0.118s
#58 linkCache_getLink using $NBC_LINKCACHE +0s … 0.118s
#59 linkCache_getLink using $NBC_LINKCACHE +0s … 0.118s
#60 linkCache_getLink using $NBC_LINKCACHE +0s … 0.118s
#61 linkCache_getLink using $NBC_LINKCACHE +0s … 0.118s
#62 linkCache_getLink no uid found +0s … 0.118s
#63 linkCache_getLink using $NBC_LINKCACHE +0s … 0.119s
#64 linkCache_getLink using $NBC_LINKCACHE +0s … 0.119s
#65 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.119s
#66 linkCache_getLink using $NBC_LINKCACHE +0s … 0.119s
#67 linkCache_getLink using $NBC_LINKCACHE +0s … 0.119s
#68 linkCache_getLink using $NBC_LINKCACHE +0s … 0.119s
#69 linkCache_getLink using $NBC_LINKCACHE +0s … 0.119s
#70 linkCache_getLink using $NBC_LINKCACHE +0s … 0.119s
#71 linkCache_getLink using $NBC_LINKCACHE +0s … 0.119s
#72 linkCache_getLink using $NBC_LINKCACHE +0s … 0.119s
#73 linkCache_getLink no uid found +0s … 0.119s
#74 linkCache_getLink using $NBC_LINKCACHE +0s … 0.119s
#75 linkCache_getLink using $NBC_LINKCACHE +0s … 0.119s
#76 linkCache_getLink using $NBC_LINKCACHE +0s … 0.119s
#77 linkCache_getLink using $NBC_LINKCACHE +0s … 0.119s
#78 linkCache_getLink using $NBC_LINKCACHE +0s … 0.12s
#79 linkCache_getLink using $NBC_LINKCACHE +0s … 0.12s
#80 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.12s
#81 linkCache_getLink using $NBC_LINKCACHE +0s … 0.12s
#82 linkCache_getLink no uid found +0s … 0.12s
#83 linkCache_getLink using $NBC_LINKCACHE +0s … 0.12s
#84 linkCache_getLink using $NBC_LINKCACHE +0s … 0.12s
#85 linkCache_getLink no uid found +0s … 0.12s
#86 linkCache_getLink using $NBC_LINKCACHE +0s … 0.12s
#87 linkCache_getLink no uid found +0s … 0.12s
#88 linkCache_getLink no uid found +0s … 0.12s
#89 linkCache_getLink using $NBC_LINKCACHE +0s … 0.12s
#90 linkCache_getLink no uid found +0s … 0.12s
#91 linkCache_getLink using $NBC_LINKCACHE +0s … 0.12s
#92 linkCache_getLink using $NBC_LINKCACHE +0s … 0.12s
#93 linkCache_getLink using $NBC_LINKCACHE +0s … 0.12s
#94 linkCache_getLink using $NBC_LINKCACHE +0s … 0.12s
#95 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.12s
#96 linkCache_getLink using $NBC_LINKCACHE +0s … 0.12s
#97 linkCache_getLink using $NBC_LINKCACHE +0s … 0.12s
#98 linkCache_getLink no uid found +0s … 0.121s
#99 linkCache_getLink using $NBC_LINKCACHE +0s … 0.121s
#100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.121s
#101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.121s
#102 linkCache_getLink using $NBC_LINKCACHE +0s … 0.121s
#103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.121s
#104 linkCache_getLink no uid found +0s … 0.121s
#105 linkCache_getLink using $NBC_LINKCACHE +0s … 0.121s
#106 linkCache_getLink no uid found +0s … 0.121s
#107 linkCache_getLink no uid found +0s … 0.121s
#108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.121s
#109 linkCache_getLink no uid found +0s … 0.121s
#110 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.121s
#111 linkCache_getLink using $NBC_LINKCACHE +0s … 0.122s
#112 linkCache_getLink using $NBC_LINKCACHE +0s … 0.122s
#113 linkCache_getLink using $NBC_LINKCACHE +0s … 0.122s
#114 linkCache_getLink using $NBC_LINKCACHE +0s … 0.122s
#115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.122s
#116 linkCache_getLink no uid found +0s … 0.122s
#117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.122s
#118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.122s
#119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.122s
#120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.122s
#121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.122s
#122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.122s
#123 linkCache_getLink using $NBC_LINKCACHE +0s … 0.122s
#124 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.122s
#125 linkCache_getLink using $NBC_LINKCACHE +0s … 0.122s
#126 linkCache_getLink using $NBC_LINKCACHE +0s … 0.122s
#127 linkCache_getLink using $NBC_LINKCACHE +0s … 0.123s
#128 linkCache_getLink using $NBC_LINKCACHE +0s … 0.123s
#129 linkCache_getLink using $NBC_LINKCACHE +0s … 0.123s
#130 linkCache_getLink using $NBC_LINKCACHE +0s … 0.123s
#131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.123s
#132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.123s
#133 linkCache_getLink using $NBC_LINKCACHE +0s … 0.123s
#134 linkCache_getLink no uid found +0s … 0.123s
#135 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.125s
#136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.126s
#137 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.128s
#138 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.128s
#139 linkCache_getLink using $NBC_LINKCACHE +0.046s … 0.174s
#140 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#141 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.175s
#142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.176s
#143 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.177s
#144 linkCache_getLink using $NBC_LINKCACHE +0s … 0.177s
#145 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.178s
#146 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#147 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.179s
#148 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#149 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.18s
#150 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s
#151 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.181s
#152 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.182s
#153 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.183s
#154 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#155 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.184s
#156 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s
#157 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.185s
#158 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.187s
#159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.187s
#160 linkCache_getLink using $NBC_LINKCACHE +0s … 0.187s
#161 linkCache_getLink using $NBC_LINKCACHE +0s … 0.187s
#162 linkCache_getLink using $NBC_LINKCACHE +0s … 0.187s
#163 linkCache_getLink using $NBC_LINKCACHE +0s … 0.187s
#164 linkCache_getLink no uid found +0s … 0.187s
#165 linkCache_getLink using $NBC_LINKCACHE +0s … 0.187s
#166 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.187s
#167 linkCache_getLink no uid found +0s … 0.187s
#168 linkCache_getLink using $NBC_LINKCACHE +0s … 0.187s
#169 linkCache_getLink using $NBC_LINKCACHE +0s … 0.187s
#170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.187s
#171 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.189s
#172 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s
#173 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s
#174 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s
#175 linkCache_getLink no uid found +0s … 0.189s
#176 linkCache_getLink no uid found +0s … 0.189s
#177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s
#178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s
#179 linkCache_getLink using $NBC_LINKCACHE +0s … 0.19s
#180 linkCache_getLink using $NBC_LINKCACHE +0s … 0.19s
#181 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.19s
#182 linkCache_getLink using $NBC_LINKCACHE +0s … 0.19s
#183 linkCache_getLink using $NBC_LINKCACHE +0s … 0.19s
#184 linkCache_getLink using $NBC_LINKCACHE +0s … 0.19s
#185 linkCache_getLink using $NBC_LINKCACHE +0s … 0.19s
#186 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.191s
#187 linkCache_getLink using $NBC_LINKCACHE +0s … 0.191s
#188 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.193s
#189 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.195s
#190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.195s
#191 linkCache_getLink using $NBC_LINKCACHE +0s … 0.195s
#192 linkCache_getLink using $NBC_LINKCACHE +0s … 0.196s
#193 linkCache_getLink using $NBC_LINKCACHE +0.007s … 0.203s
#194 linkCache_getLink using $NBC_LINKCACHE +0s … 0.203s
#195 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.203s
#196 linkCache_getLink using $NBC_LINKCACHE +0s … 0.203s
#197 linkCache_getLink using $NBC_LINKCACHE +0s … 0.203s
#198 linkCache_getLink using $NBC_LINKCACHE +0s … 0.203s
#199 linkCache_getLink using $NBC_LINKCACHE +0s … 0.203s
#200 linkCache_getLink using $NBC_LINKCACHE +0s … 0.203s
#201 linkCache_getLink using $NBC_LINKCACHE +0s … 0.203s
#202 linkCache_getLink using $NBC_LINKCACHE +0s … 0.203s
#203 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.204s
#204 linkCache_getLink using $NBC_LINKCACHE +0s … 0.204s
#205 linkCache_getLink using $NBC_LINKCACHE +0s … 0.204s
#206 linkCache_getLink using $NBC_LINKCACHE +0s … 0.204s
#207 linkCache_getLink using $NBC_LINKCACHE +0s … 0.205s
#208 linkCache_getLink using $NBC_LINKCACHE +0s … 0.205s
#209 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.205s
#210 linkCache_getLink using $NBC_LINKCACHE +0s … 0.205s
#211 linkCache_getLink using $NBC_LINKCACHE +0s … 0.205s
#212 linkCache_getLink using $NBC_LINKCACHE +0s … 0.205s
#213 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.206s
#214 linkCache_getLink using $NBC_LINKCACHE +0s … 0.206s
#215 linkCache_getLink using $NBC_LINKCACHE +0s … 0.206s
#216 linkCache_getLink using $NBC_LINKCACHE +0s … 0.206s
#217 linkCache_getLink using $NBC_LINKCACHE +0s … 0.206s
#218 linkCache_getLink using $NBC_LINKCACHE +0s … 0.206s
#219 linkCache_getLink using $NBC_LINKCACHE +0s … 0.206s
#220 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.207s
#221 min, max, avg, median took s +0.001s … 0.208s
#222 before gaming benchmark output +0s … 0.208s
#223 Got 622 rows for game benchmarks. +0.079s .
.. 0.286s
#224 composed SQL query for gamebenchmarks +0s … 0.286s
#225 linkCache_getLink using $NBC_LINKCACHE +0s … 0.286s
#226 linkCache_getLink using $NBC_LINKCACHE +0s … 0.286s
#227 linkCache_getLink using $NBC_LINKCACHE +0s … 0.286s
#228 linkCache_getLink using $NBC_LINKCACHE +0s … 0.286s
#229 linkCache_getLink using $NBC_LINKCACHE +0s … 0.286s
#230 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#231 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#232 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#233 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#234 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#235 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#236 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#237 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.287s
#238 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#239 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#240 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#241 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#242 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#243 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#244 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#245 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#246 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#247 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#248 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#249 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#250 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#251 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.287s
#252 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#253 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#254 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#255 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#256 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#257 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#258 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#259 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#260 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#261 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#262 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#263 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#264 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#265 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.287s
#266 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#267 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#268 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#269 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#270 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#271 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#272 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#273 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#274 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#275 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#276 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#277 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#278 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#279 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.287s
#280 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#281 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#282 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#283 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#284 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#285 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#286 linkCache_getLink using $NBC_LINKCACHE +0s … 0.287s
#287 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#288 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#289 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#290 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#291 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#292 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#293 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.288s
#294 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#295 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#296 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#297 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#298 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#299 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#300 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#301 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#302 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#303 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#304 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#305 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#306 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#307 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.288s
#308 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#309 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#310 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#311 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#312 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#313 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#314 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#315 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#316 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#317 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#318 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#319 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#320 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#321 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.288s
#322 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#323 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#324 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#325 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#326 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#327 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#328 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#329 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#330 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#331 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#332 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#333 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#334 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#335 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.288s
#336 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#337 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#338 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#339 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#340 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#341 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#342 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#343 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#344 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#345 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#346 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#347 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#348 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#349 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.288s
#350 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#351 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#352 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#353 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#354 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#355 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#356 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#357 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#358 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#359 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#360 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#361 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#362 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#363 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.288s
#364 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#365 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#366 linkCache_getLink using $NBC_LINKCACHE +0s … 0.288s
#367 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#368 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#369 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#370 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#371 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#372 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#373 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#374 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#375 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#376 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#377 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.289s
#378 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#379 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#380 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#381 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#382 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#383 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#384 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#385 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#386 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#387 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#388 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#389 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#390 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#391 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.289s
#392 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#393 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#394 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#395 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#396 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#397 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#398 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#399 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#400 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#401 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#402 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#403 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#404 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#405 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.289s
#406 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#407 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#408 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#409 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#410 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#411 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#412 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#413 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#414 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#415 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#416 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#417 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#418 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#419 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.289s
#420 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#421 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#422 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#423 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#424 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#425 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#426 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#427 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#428 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#429 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#430 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#431 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#432 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#433 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.289s
#434 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#435 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#436 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#437 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#438 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#439 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#440 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#441 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#442 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#443 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#444 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#445 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#446 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#447 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.289s
#448 linkCache_getLink using $NBC_LINKCACHE +0s … 0.289s
#449 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#450 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#451 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#452 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#453 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#454 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#455 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#456 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#457 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#458 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#459 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#460 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#461 linkCache_getLink using $NBC_LINKCACHE +0s … 0.
29s
#462 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#463 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#464 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#465 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#466 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#467 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#468 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#469 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#470 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#471 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#472 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#473 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#474 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#475 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#476 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.29s
#477 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#478 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#479 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#480 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#481 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#482 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#483 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#484 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#485 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#486 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#487 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#488 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#489 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#490 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#491 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.29s
#492 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#493 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#494 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#495 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#496 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#497 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#498 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#499 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#500 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#501 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#502 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#503 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#504 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#505 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#506 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.29s
#507 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#508 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#509 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#510 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#511 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#512 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#513 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#514 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#515 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#516 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#517 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#518 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#519 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#520 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#521 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.29s
#522 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#523 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#524 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#525 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#526 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#527 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#528 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#529 linkCache_getLink using $NBC_LINKCACHE +0s … 0.29s
#530 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#531 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#532 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#533 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#534 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#535 linkCache_getLink using $NBC_LINKCACHE +0s …
0.291s
#536 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#537 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#538 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#539 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#540 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#541 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#542 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#543 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#544 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#545 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#546 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#547 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#548 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#549 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.291s
#550 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#551 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#552 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#553 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#554 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#555 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#556 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#557 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#558 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#559 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#560 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#561 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#562 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#563 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.291s
#564 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#565 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#566 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#567 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#568 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#569 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#570 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#571 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#572 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#573 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#574 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#575 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#576 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#577 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.291s
#578 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#579 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#580 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#581 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#582 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#583 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#584 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#585 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#586 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#587 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#588 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#589 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#590 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#591 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.291s
#592 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#593 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#594 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#595 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#596 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#597 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#598 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#599 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#600 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#601 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#602 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#603 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#604 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#605 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.291s
#606 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#607 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#608 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#609 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#610 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#611 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#612 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#613 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#614 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#615 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#616 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#617 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#618 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#619 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.291s
#620 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#621 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#622 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#623 linkCache_getLink using $NBC_LINKCACHE +0s … 0.291s
#624 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#625 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#626 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#627 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#628 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#629 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#630 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#631 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#632 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#633 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.292s
#634 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#635 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#636 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#637 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#638 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#639 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#640 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#641 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#642 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#643 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#644 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#645 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#646 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#647 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.292s
#648 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#649 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#650 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#651 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#652 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#653 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#654 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#655 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#656 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#657 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#658 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#659 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#660 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#661 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.292s
#662 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#663 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#664 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#665 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#666 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#667 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#668 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#669 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#670 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#671 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#672 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#673 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#674 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#675 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.292s
#676 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#677 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#678 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#679 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#680 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#681 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#682 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#683 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#684 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#685 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#686 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#687 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#688 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#689 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.292s
#690 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#691 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#692 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#693 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#694 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#695 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#696 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#697 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#698 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#699 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#700 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#701 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#702 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#703 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.292s
#704 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#705 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#706 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#707 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#708 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#709 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#710 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#711 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#712 linkCache_getLink using $NBC_LINKCACHE +0s … 0.292s
#713 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#714 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#715 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#716 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#717 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.293s
#718 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#719 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#720 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#721 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#722 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#723 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#724 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#725 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#726 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#727 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#728 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#729 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#730 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#731 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.293s
#732 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#733 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#734 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#735 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#736 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#737 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#738 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#739 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#740 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#741 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#742 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#743 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#744 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#745 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.293s
#746 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#747 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#748 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#749 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#750 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#751 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#752 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#753 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#754 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#755 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#756 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#757 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#758 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#759 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.293s
#760 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#761 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#762 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#763 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#764 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#765 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#766 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#767 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#768 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#769 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#770 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#771 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#772 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#773 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.293s
#774 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#775 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#776 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#777 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#778 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#779 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#780 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#781 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#782 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#783 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#784 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#785 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#786 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#787 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.293s
#788 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#789 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#790 linkCache_getLink using $NBC_LINKCACHE +0s … 0.293s
#791 got data and put it in $dataArray +0.005s … 0.298s
#792 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.299s
#793 linkCache_getLink using $NBC_LINKCACHE +0s … 0.299s
#794 linkCache_getLink using $NBC_LINKCACHE +0s … 0.299s
#795 linkCache_getLink using $NBC_LINKCACHE +0s … 0.299s
#796 linkCache_getLink using $NBC_LINKCACHE +0s … 0.299s
#797 linkCache_getLink using $NBC_LINKCACHE +0s … 0.299s
#798 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.299s
#799 linkCache_getLink using $NBC_LINKCACHE +0s … 0.299s
#800 linkCache_getLink using $NBC_LINKCACHE +0s … 0.299s
#801 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.299s
#802 linkCache_getLink using $NBC_LINKCACHE +0s … 0.299s
#803 linkCache_getLink using $NBC_LINKCACHE +0s … 0.299s
#804 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.3s
#805 linkCache_getLink using $NBC_LINKCACHE +0s … 0.3s
#806 linkCache_getLink using $NBC_LINKCACHE +0s … 0.3s
#807 linkCache_getLink using $NBC_LINKCACHE +0s … 0.3s
#808 linkCache_getLink no uid found +0s … 0.3s
#809 linkCache_getLink no uid found +0s … 0.3s
#810 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.301s
#811 linkCache_getLink using $NBC_LINKCACHE +0s … 0.301s
#812 linkCache_getLink using $NBC_LINKCACHE +0s … 0.301s
#813 linkCache_getLink using $NBC_LINKCACHE +0s … 0.301s
#814 linkCache_getLink using $NBC_LINKCACHE +0s … 0.301s
#815 linkCache_getLink using $NBC_LINKCACHE +0s … 0.301s
#816 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.301s
#817 linkCache_getLink using $NBC_LINKCACHE +0s … 0.301s
#818 linkCache_getLink using $NBC_LINKCACHE +0s … 0.301s
#819 linkCache_getLink no uid found +0s … 0.301s
#820 linkCache_getLink using $NBC_LINKCACHE +0s … 0.301s
#821 linkCache_getLink using $NBC_LINKCACHE +0s … 0.301s
#822 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.301s
#823 linkCache_getLink using $NBC_LINKCACHE +0s … 0.302s
#824 linkCache_getLink using $NBC_LINKCACHE +0s … 0.302s
#825 linkCache_getLink using $NBC_LINKCACHE +0s … 0.302s
#826 linkCache_getLink using $NBC_LINKCACHE +0s … 0.302s
#827 linkCache_getLink using $NBC_LINKCACHE +0s … 0.302s
#828 linkCache_getLink using $NBC_LINKCACHE +0s … 0.302s
#829 linkCache_getLink no uid found +0s … 0.302s
#830 linkCache_getLink using $NBC_LINKCACHE +0s … 0.
302s
#831 linkCache_getLink no uid found +0s … 0.302s
#832 linkCache_getLink using $NBC_LINKCACHE +0s … 0.302s
#833 linkCache_getLink using $NBC_LINKCACHE +0s … 0.302s
#834 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.302s
#835 linkCache_getLink using $NBC_LINKCACHE +0s … 0.302s
#836 linkCache_getLink using $NBC_LINKCACHE +0s … 0.303s
#837 linkCache_getLink using $NBC_LINKCACHE +0s … 0.303s
#838 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.303s
#839 linkCache_getLink using $NBC_LINKCACHE +0s … 0.303s
#840 linkCache_getLink using $NBC_LINKCACHE +0s … 0.303s
#841 linkCache_getLink using $NBC_LINKCACHE +0s … 0.303s
#842 linkCache_getLink using $NBC_LINKCACHE +0s … 0.303s
#843 linkCache_getLink using $NBC_LINKCACHE +0s … 0.303s
#844 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.304s
#845 linkCache_getLink using $NBC_LINKCACHE +0s … 0.304s
#846 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.304s
#847 linkCache_getLink using $NBC_LINKCACHE +0s … 0.304s
#848 linkCache_getLink using $NBC_LINKCACHE +0s … 0.304s
#849 linkCache_getLink using $NBC_LINKCACHE +0s … 0.304s
#850 linkCache_getLink using $NBC_LINKCACHE +0s … 0.304s
#851 linkCache_getLink using $NBC_LINKCACHE +0s … 0.304s
#852 linkCache_getLink using $NBC_LINKCACHE +0s … 0.304s
#853 linkCache_getLink using $NBC_LINKCACHE +0s … 0.304s
#854 linkCache_getLink using $NBC_LINKCACHE +0s … 0.304s
#855 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.305s
#856 linkCache_getLink using $NBC_LINKCACHE +0s … 0.305s
#857 linkCache_getLink using $NBC_LINKCACHE +0s … 0.305s
#858 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.305s
#859 linkCache_getLink using $NBC_LINKCACHE +0s … 0.305s
#860 linkCache_getLink using $NBC_LINKCACHE +0s … 0.306s
#861 linkCache_getLink using $NBC_LINKCACHE +0s … 0.306s
#862 linkCache_getLink using $NBC_LINKCACHE +0s … 0.306s
#863 linkCache_getLink using $NBC_LINKCACHE +0s … 0.306s
#864 linkCache_getLink using $NBC_LINKCACHE +0s … 0.306s
#865 linkCache_getLink using $NBC_LINKCACHE +0s … 0.306s
#866 linkCache_getLink using $NBC_LINKCACHE +0s … 0.306s
#867 linkCache_getLink using $NBC_LINKCACHE +0s … 0.306s
#868 linkCache_getLink using $NBC_LINKCACHE +0s … 0.306s
#869 linkCache_getLink no uid found +0s … 0.306s
#870 linkCache_getLink using $NBC_LINKCACHE +0s … 0.306s
#871 linkCache_getLink using $NBC_LINKCACHE +0s … 0.307s
#872 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.307s
#873 linkCache_getLink using $NBC_LINKCACHE +0s … 0.307s
#874 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.307s
#875 linkCache_getLink using $NBC_LINKCACHE +0s … 0.307s
#876 linkCache_getLink using $NBC_LINKCACHE +0s … 0.307s
#877 linkCache_getLink using $NBC_LINKCACHE +0s … 0.307s
#878 linkCache_getLink using $NBC_LINKCACHE +0s … 0.307s
#879 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#880 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#881 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#882 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#883 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#884 linkCache_getLink no uid found +0s … 0.308s
#885 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#886 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.308s
#887 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.308s
#888 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#889 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#890 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#891 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#892 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#893 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#894 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#895 linkCache_getLink using $NBC_LINKCACHE +0s … 0.308s
#896 linkCache_getLink no uid found +0s … 0.309s
#897 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#898 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#899 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#900 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.309s
#901 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#902 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#903 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#904 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#905 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#906 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#907 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#908 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#909 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#910 linkCache_getLink no uid found +0s … 0.309s
#911 linkCache_getLink no uid found +0s … 0.309s
#912 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#913 linkCache_getLink using $NBC_LINKCACHE +0s … 0.309s
#914 linkCache_getLink using $NBC_LINKCACHE +0s … 0.
309s
#915 linkCache_getLink using $NBC_LINKCACHE +0s … 0.31s
#916 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.31s
#917 linkCache_getLink using $NBC_LINKCACHE +0s … 0.31s
#918 linkCache_getLink using $NBC_LINKCACHE +0s … 0.31s
#919 linkCache_getLink using $NBC_LINKCACHE +0s … 0.31s
#920 linkCache_getLink using $NBC_LINKCACHE +0s … 0.31s
#921 linkCache_getLink using $NBC_LINKCACHE +0s … 0.31s
#922 linkCache_getLink using $NBC_LINKCACHE +0s … 0.31s
#923 linkCache_getLink using $NBC_LINKCACHE +0s … 0.31s
#924 linkCache_getLink using $NBC_LINKCACHE +0s … 0.31s
#925 linkCache_getLink no uid found +0s … 0.31s
#926 linkCache_getLink using $NBC_LINKCACHE +0s … 0.31s
#927 linkCache_getLink using $NBC_LINKCACHE +0s … 0.31s
#928 linkCache_getLink using $NBC_LINKCACHE +0s … 0.31s
#929 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.31s
#930 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.311s
#931 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#932 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#933 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#934 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#935 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#936 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#937 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#938 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#939 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#940 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#941 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#942 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#943 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.311s
#944 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#945 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#946 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#947 linkCache_getLink using $NBC_LINKCACHE +0s … 0.311s
#948 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.312s
#949 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#950 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#951 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#952 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#953 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#954 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#955 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#956 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#957 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.312s
#958 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#959 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#960 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#961 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#962 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#963 linkCache_getLink no uid found +0s … 0.312s
#964 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#965 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#966 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#967 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#968 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#969 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#970 linkCache_getLink using $NBC_LINKCACHE +0s … 0.312s
#971 linkCache_getLink using $NBC_LINKCACHE +0s ..
. 0.313s
#972 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.313s
#973 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#974 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#975 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#976 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#977 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#978 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#979 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#980 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#981 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#982 linkCache_getLink using $NBC_LINKCACHE +0s … 0.313s
#983 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.314s
#984 linkCache_getLink using $NBC_LINKCACHE +0s … 0.314s
#985 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.314s
#986 linkCache_getLink using $NBC_LINKCACHE +0s … 0.314s
#987 linkCache_getLink using $NBC_LINKCACHE +0s … 0.314s
#988 linkCache_getLink using $NBC_LINKCACHE +0s … 0.314s
#989 linkCache_getLink using $NBC_LINKCACHE +0s … 0.314s
#990 linkCache_getLink using $NBC_LINKCACHE +0s … 0.314s
#991 linkCache_getLink using $NBC_LINKCACHE +0s … 0.314s
#992 linkCache_getLink using $NBC_LINKCACHE +0s … 0.314s
#993 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.315s
#994 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#995 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#996 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#997 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#998 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#999 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.315s
#1000 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#1001 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#1002 linkCache_getLink using $NBC_LINKCACHE +0s … 0.315s
#1003 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.316s
#1004 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1005 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1006 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1007 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1008 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1009 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1010 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1011 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1012 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1013 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.316s
#1014 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1015 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1016 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1017 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1018 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1019 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1020 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1021 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1022 linkCache_getLink using $NBC_LINKCACHE +0s … 0.316s
#1023 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.318s
#1024 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#1025 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#1026 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#1027 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.318s
#1028 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#1029 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#1030 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#1031 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#1032 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#1033 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.318s
#1034 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#1035 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#1036 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#1037 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#1038 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#1039 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#1040 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#1041 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.318s
#1042 linkCache_getLink using $NBC_LINKCACHE +0s … 0.318s
#1043 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.319s
#1044 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#1045 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#1046 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#1047 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#1048 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#1049 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#1050 linkCache_getLink using $NBC_LINKCACHE +0s … 0.319s
#1051 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#1052 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#1053 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.32s
#1054 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#1055 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.32s
#1056 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#1057 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#1058 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#1059 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#1060 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#1061 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#1062 linkCache_getLink using $NBC_LINKCACHE +0s … 0.32s
#1063 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.321s
#1064 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#1065 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#1066 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#1067 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#1068 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#1069 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.321s
#1070 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#1071 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#1072 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#1073 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#1074 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#1075 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#1076 linkCache_getLink using $NBC_LINKCACHE +0s … 0.321s
#1077 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.322s
#1078 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s
#1079 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s
#1080 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s
#1081 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s
#1082 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s
#1083 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.322s
#1084 linkCache_getLink using $NBC_LINKCACHE +0s … 0.322s
#1085 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.323s
#1086 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#1087 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#1088 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#1089 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#1090 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#1091 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#1092 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#1093 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#1094 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#1095 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.323s
#1096 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#1097 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.323s
#1098 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#1099 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#1100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#1101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.323s
#1102 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#1103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#1104 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#1105 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.324s
#1106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#1107 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#1108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#1109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#1110 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#1111 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.324s
#1112 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#1113 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#1114 linkCache_getLink using $NBC_LINKCACHE +0s … 0.324s
#1115 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.325s
#1116 linkCache_getLink using $NBC_LINKCACHE +0s … 0.325s
#1117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.325s
#1118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.325s
#1119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.325s
#1120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.325s
#1121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.325s
#1122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.325s
#1123 linkCache_getLink using $NBC_LINKCACHE +0s … 0.325s
#1124 linkCache_getLink using $NBC_LINKCACHE +0s … 0.325s
#1125 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.326s
#1126 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#1127 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#1128 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#1129 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#1130 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#1131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#1132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.326s
#1133 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.326s
#1134 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#1135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#1136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#1137 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#1138 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#1139 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.327s
#1140 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#1141 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#1142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#1143 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.327s
#1144 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#1145 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#1146 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#1147 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#1148 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#1149 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#1150 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#1151 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#1152 linkCache_getLink using $NBC_LINKCACHE +0s … 0.327s
#1153 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.328s
#1154 linkCache_getLink using $NBC_LINKCACHE +0s … 0.328s
#1155 linkCache_getLink using $NBC_LINKCACHE +0s … 0.328s
#1156 linkCache_getLink using $NBC_LINKCACHE +0s … 0.328s
#1157 linkCache_getLink using $NBC_LINKCACHE +0s … 0.328s
#1158 linkCache_getLink using $NBC_LINKCACHE +0s … 0.328s
#1159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.328s
#1160 linkCache_getLink using $NBC_LINKCACHE +0s … 0.328s
#1161 linkCache_getLink using $NBC_LINKCACHE +0s … 0.328s
#1162 linkCache_getLink using $NBC_LINKCACHE +0s … 0.328s
#1163 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.329s
#1164 linkCache_getLink using $NBC_LINKCACHE +0s … 0.329s
#1165 linkCache_getLink using $NBC_LINKCACHE +0s … 0.329s
#1166 linkCache_getLink using $NBC_LINKCACHE +0s … 0.329s
#1167 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.329s
#1168 linkCache_getLink using $NBC_LINKCACHE +0s … 0.329s
#1169 linkCache_getLink using $NBC_LINKCACHE +0s … 0.329s
#1170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.329s
#1171 linkCache_getLink using $NBC_LINKCACHE +0s … 0.329s
#1172 linkCache_getLink using $NBC_LINKCACHE +0s … 0.329s
#1173 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.329s
#1174 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1175 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1176 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1179 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1180 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1181 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.33s
#1182 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1183 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.33s
#1184 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1185 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1186 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1187 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1188 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1189 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1191 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1192 linkCache_getLink using $NBC_LINKCACHE +0s … 0.33s
#1193 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1194 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1195 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.331s
#1196 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1197 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.331s
#1198 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1199 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1200 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1201 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1202 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1203 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1204 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1205 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1206 linkCache_getLink using $NBC_LINKCACHE +0s … 0.331s
#1207 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.332s
#1208 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1209 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.332s
#1210 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1211 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1212 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1213 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1214 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1215 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1216 linkCache_getLink using $NBC_LINKCACHE +0s … 0.332s
#1217 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.333s
#1218 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1219 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1220 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1221 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1222 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1223 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.333s
#1224 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1225 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1226 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1227 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1228 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1229 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1230 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1231 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1232 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1233 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1234 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1235 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1236 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1237 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.333s
#1238 linkCache_getLink using $NBC_LINKCACHE +0s … 0.333s
#1239 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.334s
#1240 linkCache_getLink using $NBC_LINKCACHE +0.025s … 0.359s
#1241 linkCache_getLink using $NBC_LINKCACHE +0.012s … 0.37s
#1242 linkCache_getLink using $NBC_LINKCACHE +0.01s … 0.38s
#1243 linkCache_getLink using $NBC_LINKCACHE +0.008s … 0.388s
#1244 linkCache_getLink using $NBC_LINKCACHE +0.006s … 0.394s
#1245 linkCache_getLink using $NBC_LINKCACHE +0.004s … 0.398s
#1246 linkCache_getLink using $NBC_LINKCACHE +0s … 0.398s
#1247 linkCache_getLink using $NBC_LINKCACHE +0s … 0.398s
#1248 linkCache_getLink using $NBC_LINKCACHE +0s … 0.398s
#1249 linkCache_getLink using $NBC_LINKCACHE +0s … 0.398s
#1250 linkCache_getLink using $NBC_LINKCACHE +0s … 0.398s
#1251 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.398s
#1252 linkCache_getLink using $NBC_LINKCACHE +0s … 0.399s
#1253 linkCache_getLink using $NBC_LINKCACHE +0s … 0.399s
#1254 linkCache_getLink using $NBC_LINKCACHE +0s … 0.399s
#1255 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.399s
#1256 linkCache_getLink using $NBC_LINKCACHE +0s … 0.399s
#1257 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.4s
#1258 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1259 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1260 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1261 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1262 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1263 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1264 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1265 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.4s
#1266 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1267 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1268 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1269 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1270 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1271 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1272 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1273 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1274 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1275 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1276 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1277 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1278 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1279 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1280 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.4s
#1281 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1282 linkCache_getLink using $NBC_LINKCACHE +0s … 0.4s
#1283 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.401s
#1284 linkCache_getLink using $NBC_LINKCACHE +0s … 0.401s
#1285 linkCache_getLink using $NBC_LINKCACHE +0s … 0.401s
#1286 linkCache_getLink using $NBC_LINKCACHE +0s … 0.401s
#1287 linkCache_getLink using $NBC_LINKCACHE +0s … 0.401s
#1288 linkCache_getLink using $NBC_LINKCACHE +0s … 0.401s
#1289 linkCache_getLink using $NBC_LINKCACHE +0s … 0.401s
#1290 linkCache_getLink using $NBC_LINKCACHE +0s … 0.401s
#1291 linkCache_getLink using $NBC_LINKCACHE +0s … 0.401s
#1292 linkCache_getLink using $NBC_LINKCACHE +0s … 0.401s
#1293 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.402s
#1294 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.402s
#1295 linkCache_getLink using $NBC_LINKCACHE +0s … 0.402s
#1296 linkCache_getLink using $NBC_LINKCACHE +0s … 0.402s
#1297 linkCache_getLink using $NBC_LINKCACHE +0s … 0.402s
#1298 linkCache_getLink using $NBC_LINKCACHE +0s … 0.402s
#1299 linkCache_getLink using $NBC_LINKCACHE +0s … 0.402s
#1300 linkCache_getLink using $NBC_LINKCACHE +0s … 0.402s
#1301 linkCache_getLink using $NBC_LINKCACHE +0s … 0.402s
#1302 linkCache_getLink using $NBC_LINKCACHE +0s … 0.402s
#1303 linkCache_getLink using $NBC_LINKCACHE +0s … 0.402s
#1304 linkCache_getLink using $NBC_LINKCACHE +0s … 0.402s
#1305 linkCache_getLink using $NBC_LINKCACHE +0s … 0.402s
#1306 linkCache_getLink using $NBC_LINKCACHE +0s … 0.402s
#1307 linkCache_getLink using $NBC_LINKCACHE +0s … 0.402s
#1308 linkCache_getLink using $NBC_LINKCACHE +0.
001s … 0.403s
#1309 linkCache_getLink using $NBC_LINKCACHE +0s … 0.403s
#1310 linkCache_getLink using $NBC_LINKCACHE +0s … 0.403s
#1311 linkCache_getLink using $NBC_LINKCACHE +0s … 0.403s
#1312 linkCache_getLink using $NBC_LINKCACHE +0s … 0.403s
#1313 linkCache_getLink using $NBC_LINKCACHE +0s … 0.403s
#1314 linkCache_getLink using $NBC_LINKCACHE +0s … 0.403s
#1315 linkCache_getLink using $NBC_LINKCACHE +0s … 0.403s
#1316 linkCache_getLink using $NBC_LINKCACHE +0s … 0.403s
#1317 linkCache_getLink using $NBC_LINKCACHE +0s … 0.403s
#1318 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.403s
#1319 linkCache_getLink using $NBC_LINKCACHE +0s … 0.403s
#1320 linkCache_getLink using $NBC_LINKCACHE +0s … 0.403s
#1321 linkCache_getLink using $NBC_LINKCACHE +0s … 0.403s
#1322 linkCache_getLink using $NBC_LINKCACHE +0s .
.. 0.403s
#1323 linkCache_getLink using $NBC_LINKCACHE +0s … 0.403s
#1324 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1325 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1326 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1327 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1328 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1329 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1330 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1331 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1332 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1333 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1334 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1335 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1336 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.404s
#1337 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1338 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1339 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1340 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1341 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1342 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1343 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1344 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1345 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1346 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1347 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1348 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1349 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1350 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.404s
#1351 linkCache_getLink using $NBC_LINKCACHE +0s … 0.404s
#1352 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.405s
#1353 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1354 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1355 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1356 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1357 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1358 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1359 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1360 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1361 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1362 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1363 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1364 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.405s
#1365 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1366 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1367 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1368 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1369 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1370 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1371 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1372 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1373 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1374 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1375 linkCache_getLink using $NBC_LINKCACHE +0s … 0.405s
#1376 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.409s
#1377 linkCache_getLink using $NBC_LINKCACHE +0.004s … 0.412s
#1378 linkCache_getLink using $NBC_LINKCACHE +0. 002s … 0.415s
#1379 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.418s
#1380 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.42s
#1381 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.423s
#1382 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.426s
#1383 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.429s
#1384 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.432s
#1385 linkCache_getLink no uid found +0.003s … 0.435s
#1386 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.437s
#1387 linkCache_getLink using $NBC_LINKCACHE +0.004s … 0.441s
#1388 linkCache_getLink using $NBC_LINKCACHE +0s … 0.441s
#1389 linkCache_getLink using $NBC_LINKCACHE +0s … 0.441s
#1390 linkCache_getLink using $NBC_LINKCACHE +0s … 0.441s
#1391 linkCache_getLink using $NBC_LINKCACHE +0s … 0.441s
#1392 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.442s
#1393 linkCache_getLink using $NBC_LINKCACHE +0s … 0.442s
#1394 linkCache_getLink using $NBC_LINKCACHE +0s … 0.442s
#1395 linkCache_getLink using $NBC_LINKCACHE +0s … 0.442s
#1396 linkCache_getLink using $NBC_LINKCACHE +0s … 0.442s
#1397 linkCache_getLink using $NBC_LINKCACHE +0s … 0.442s
#1398 linkCache_getLink using $NBC_LINKCACHE +0s … 0.442s
#1399 linkCache_getLink using $NBC_LINKCACHE +0s … 0.442s
#1400 linkCache_getLink using $NBC_LINKCACHE +0s … 0.442s
#1401 linkCache_getLink using $NBC_LINKCACHE +0s … 0.442s
#1402 linkCache_getLink using $NBC_LINKCACHE +0s … 0.442s
#1403 linkCache_getLink using $NBC_LINKCACHE +0s … 0.442s
#1404 linkCache_getLink using $NBC_LINKCACHE +0s … 0.442s
#1405 linkCache_getLink using $NBC_LINKCACHE +0s … 0.442s
#1406 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.442s
#1407 linkCache_getLink using $NBC_LINKCACHE +0s … 0.442s
#1408 linkCache_getLink using $NBC_LINKCACHE +0s … 0.442s
#1409 linkCache_getLink using $NBC_LINKCACHE +0s … 0.442s
#1410 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.443s
#1411 linkCache_getLink using $NBC_LINKCACHE +0s … 0.443s
#1412 linkCache_getLink using $NBC_LINKCACHE +0s … 0.443s
#1413 linkCache_getLink using $NBC_LINKCACHE +0s … 0.443s
#1414 benchmarks composed for output. +0s … 0.443s
#1415 calculated avg scores. +0s … 0.443s
#1416 linkCache_getLink using $NBC_LINKCACHE +0.075s … 0.518s
#1417 return log +0.003s … 0.521s
GeForce RTX 2070 SUPER vs GeForce RTX 2080 Ti Graphics cards Comparison
In this comparison between GeForce RTX 2070 SUPER and GeForce RTX 2080 Ti you will find out which graphics card performs better in today’s games. Bear in mind that third-party versions may have more efficient cooling and higher clock speeds. This will increase cards’ performance, though not by much. In addition to raw power you should also take into account the dimensions. Thicker models simply will not fit into a small mini-ITX case. The resolution of your monitor also affects the choice, since 4K gameplay requires a more powerful GPU. And don’t overspend on the graphics card. Other parts of your build may also need to be upgraded, save some money for the CPU or power supply. For some people GeForce RTX 2070 SUPER will be the best choice, for others GeForce RTX 2080 Ti will be their preference. Study the comparison tables below and make your choice.
GeForce RTX 2070 SUPER
Check Price
GeForce RTX 2080 Ti
Check Price
Main Specs
| GeForce RTX 2070 SUPER | GeForce RTX 2080 Ti | |
| Power consumption (TDP) | 215 Watt | 250 Watt |
| Interface | PCIe 3. |
PCIe 3.0 x16 |
| Supplementary power connectors | 1x 6-pin + 1x 8-pin | 2x 8-pin |
| Memory type | GDDR6 | GDDR6 |
| Maximum RAM amount | 8 GB | 11 GB |
| Display Connectors | 1x HDMI, 3x DisplayPort, 1x USB Type-C | 1x HDMI, 3x DisplayPort, 1x USB Type-C |
|
Check Price |
Check Price |
- GeForce RTX 2080 Ti has 16% more power consumption, than GeForce RTX 2070 SUPER.
- Both video cards are using PCIe 3.0 x16 interface connection to a motherboard.
- GeForce RTX 2080 Ti has 3 GB more memory, than GeForce RTX 2070 SUPER.
- Both cards are used in Desktops.
- GeForce RTX 2070 SUPER and GeForce RTX 2080 Ti are build with Turing architecture.
- Core clock speed of GeForce RTX 2070 SUPER is 255 MHz higher, than GeForce RTX 2080 Ti.
- GeForce RTX 2070 SUPER and GeForce RTX 2080 Ti are manufactured by 12 nm process technology.
- Both graphics cards are the same length of 267 mm.
- Memory clock speed of GeForce RTX 2070 SUPER and GeForce RTX 2080 Ti 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 | 80−85 | 90−95 |
| ultra / 1080p | 60−65 | 70−75 |
| QHD / 1440p | 50−55 | 55−60 |
| 4K / 2160p | 30−35 | 40−45 |
| low / 720p | 100−110 | 100−110 |
| medium / 1080p | 90−95 | 100−110 |
| The average gaming FPS of GeForce RTX 2080 Ti in Assassin’s Creed Odyssey is 11% more, than GeForce RTX 2070 SUPER. |
||
| high / 1080p | 120−130 | 140−150 |
| ultra / 1080p | 110−120 | 130−140 |
| QHD / 1440p | 90−95 | 100−110 |
| 4K / 2160p | 55−60 | 70−75 |
| low / 720p | 160−170 | 160−170 |
| medium / 1080p | 130−140 | 150−160 |
| The average gaming FPS of GeForce RTX 2080 Ti in Battlefield 5 is 12% more, than GeForce RTX 2070 SUPER. | ||
| low / 768p | 45−50 | 45−50 |
| GeForce RTX 2070 SUPER and GeForce RTX 2080 Ti 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 2070 SUPER and GeForce RTX 2080 Ti have the same average FPS in Counter-Strike: Global Offensive. | ||
| low / 768p | 70−75 | 70−75 |
| medium / 1080p | 50−55 | 50−55 |
| GeForce RTX 2070 SUPER and GeForce RTX 2080 Ti have the same average FPS in Cyberpunk 2077. |
||
| low / 768p | 120−130 | 120−130 |
| medium / 768p | 110−120 | 110−120 |
| GeForce RTX 2070 SUPER and GeForce RTX 2080 Ti have the same average FPS in Dota 2. | ||
| high / 1080p | 100−110 | 110−120 |
| ultra / 1080p | 100−105 | 100−110 |
| QHD / 1440p | 80−85 | 100−105 |
| 4K / 2160p | 45−50 | 55−60 |
| low / 720p | 120−130 | 130−140 |
| medium / 1080p | 110−120 | 120−130 |
| The average gaming FPS of GeForce RTX 2080 Ti in Far Cry 5 is 10% more, than GeForce RTX 2070 SUPER. |
||
| high / 1080p | 160−170 | 170−180 |
| ultra / 1080p | 130−140 | 150−160 |
| QHD / 1440p | 95−100 | 110−120 |
| 4K / 2160p | 21−24 | 21−24 |
| low / 720p | 270−280 | 270−280 |
| medium / 1080p | 190−200 | 210−220 |
| The average gaming FPS of GeForce RTX 2080 Ti in Fortnite is 7% more, than GeForce RTX 2070 SUPER. | ||
| high / 1080p | 130−140 | 150−160 |
| ultra / 1080p | 110−120 | 130−140 |
| QHD / 1440p | 95−100 | 110−120 |
| 4K / 2160p | 65−70 | 80−85 |
| low / 720p | 170−180 | 170−180 |
| medium / 1080p | 140−150 | 150−160 |
| The average gaming FPS of GeForce RTX 2080 Ti in Forza Horizon 4 is 11% more, than GeForce RTX 2070 SUPER. |
||
| low / 768p | 170−180 | 170−180 |
| medium / 768p | 160−170 | 160−170 |
| high / 1080p | 140−150 | 150−160 |
| ultra / 1080p | 85−90 | 100−105 |
| QHD / 1440p | 75−80 | 90−95 |
| The average gaming FPS of GeForce RTX 2080 Ti in Grand Theft Auto V is 6% more, than GeForce RTX 2070 SUPER. | ||
| high / 1080p | 75−80 | 90−95 |
| ultra / 1080p | 60−65 | 75−80 |
| QHD / 1440p | 45−50 | 60−65 |
| 4K / 2160p | 30−35 | 40−45 |
| low / 720p | 140−150 | 150−160 |
| medium / 1080p | 95−100 | 110−120 |
| The average gaming FPS of GeForce RTX 2080 Ti in Metro Exodus is 16% more, than GeForce RTX 2070 SUPER. |
||
| low / 768p | 120−130 | 120−130 |
| GeForce RTX 2070 SUPER and GeForce RTX 2080 Ti have the same average FPS in Minecraft. | ||
| high / 1080p | 140−150 | 160−170 |
| ultra / 1080p | 120−130 | 140−150 |
| 4K / 2160p | 18−20 | 18−20 |
| low / 720p | 170−180 | 190−200 |
| medium / 1080p | 160−170 | 180−190 |
| The average gaming FPS of GeForce RTX 2080 Ti in PLAYERUNKNOWN’S BATTLEGROUNDS is 12% more, than GeForce RTX 2070 SUPER. | ||
| high / 1080p | 70−75 | 90−95 |
| ultra / 1080p | 45−50 | 55−60 |
| QHD / 1440p | 35−40 | 45−50 |
| 4K / 2160p | 24−27 | 30−35 |
| low / 720p | 140−150 | 150−160 |
| medium / 1080p | 100−110 | 120−130 |
| The average gaming FPS of GeForce RTX 2080 Ti in Red Dead Redemption 2 is 18% more, than GeForce RTX 2070 SUPER. |
||
| low / 768p | 300−350 | 300−350 |
| medium / 768p | 230−240 | 260−270 |
| high / 1080p | 140−150 | 180−190 |
| ultra / 1080p | 80−85 | 100−110 |
| 4K / 2160p | 55−60 | 70−75 |
| The average gaming FPS of GeForce RTX 2080 Ti in The Witcher 3: Wild Hunt is 12% more, than GeForce RTX 2070 SUPER. | ||
| low / 768p | 350−400 | 650−700 |
| ultra / 1080p | 180−190 | 300−350 |
| The average gaming FPS of GeForce RTX 2080 Ti in World of Tanks is 78% more, than GeForce RTX 2070 SUPER. |
||
Full Specs
| GeForce RTX 2070 SUPER | GeForce RTX 2080 Ti | |
| Architecture | Turing | Turing |
| Code name | Turing TU104 | Turing TU102 |
| Type | Desktop | Desktop |
| Release date | 2 July 2019 | 27 August 2018 |
| Pipelines | 2560 | 4352 |
| Core clock speed | 1605 MHz | 1350 MHz |
| Boost Clock | 1770 MHz | 1545 MHz |
| Transistor count | 13,600 million | 18,600 million |
| Manufacturing process technology | 12 nm | 12 nm |
| Texture fill rate | 283. |
420.2 |
| Length | 267 mm | 267 mm |
| Memory bus width | 256 Bit | 352 Bit |
| Memory clock speed | 14000 MHz | 14000 MHz |
| Memory bandwidth | 448.0 GB/s | 616.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 | 2.0 |
| Vulkan | 1. |
1.2.131 |
| CUDA | 7.5 | 7.5 |
|
Check Price |
Check Price |
Similar compares
- GeForce RTX 2070 SUPER vs GeForce RTX 2080 Super mobile
- GeForce RTX 2070 SUPER vs GeForce RTX 2080 Super mobile
- GeForce RTX 2080 Ti vs GeForce RTX 2080 Super mobile
- GeForce RTX 2080 Ti vs GeForce RTX 2080 Super mobile
- GeForce RTX 2070 SUPER vs GeForce RTX 3080
- GeForce RTX 2070 SUPER vs Quadro RTX 4000 mobile
- GeForce RTX 2080 Ti vs GeForce RTX 3080
- GeForce RTX 2080 Ti vs Quadro RTX 4000 mobile
Nvidia GeForce RTX 2070 Super vs Nvidia GeForce RTX 2080 Super: What is the difference?
73points
Nvidia GeForce RTX 2070 Super
76points
Nvidia GeForce RTX 2080 Super
Comparison winner
vs
54 facts in comparison
Nvidia GeForce RTX 2070 Super
Nvidia GeForce RTX 2080 Super
Why is Nvidia GeForce RTX 2070 Super better than Nvidia GeForce RTX 2080 Super?
- 35W lower TDP?
215Wvs250W
Why is Nvidia GeForce RTX 2080 Super better than Nvidia GeForce RTX 2070 Super?
- 2.
09 TFLOPS higher floating-point performance?
11.15 TFLOPSvs9.06 TFLOPS - 187MHz faster memory clock speed?
1937MHzvs1750MHz - 1496MHz higher effective memory clock speed?
15496MHzvs14000MHz - 65.3 GTexels/s higher texture rate?
348.5 GTexels/svs283.2 GTexels/s - 47.9GB/s more memory bandwidth?
495.9GB/svs448GB/s - 512 more shading units?
3072vs2560 - 32 more texture mapping units (TMUs)?
192vs160 - 1 more DisplayPort outputs?
3vs2
Which are the most popular comparisons?
Nvidia GeForce RTX 2070 Super
vs
Nvidia GeForce RTX 3060
Nvidia GeForce RTX 2080 Super
vs
Nvidia GeForce RTX 3060
Nvidia GeForce RTX 2070 Super
vs
Nvidia GeForce RTX 3060 Ti
Nvidia GeForce RTX 2080 Super
vs
Nvidia GeForce RTX 3070 Ti
Nvidia GeForce RTX 2070 Super
vs
Nvidia GeForce RTX 3070 Ti
Nvidia GeForce RTX 2080 Super
vs
Nvidia GeForce RTX 3070
Nvidia GeForce RTX 2070 Super
vs
Nvidia GeForce RTX 3050 Laptop
Nvidia GeForce RTX 2080 Super
vs
Nvidia GeForce RTX 3080
Nvidia GeForce RTX 2070 Super
vs
Nvidia GeForce RTX 3070
Nvidia GeForce RTX 2080 Super
vs
Nvidia GeForce RTX 3080 Ti
Nvidia GeForce RTX 2070 Super
vs
Nvidia Geforce GTX 1660 Super
Nvidia GeForce RTX 2080 Super
vs
Nvidia GeForce RTX 3060 Ti
Nvidia GeForce RTX 2070 Super
vs
AMD Radeon RX 6500 XT
Nvidia GeForce RTX 2080 Super
vs
Nvidia Geforce GTX 1660 Super
Nvidia GeForce RTX 2070 Super
vs
Nvidia GeForce RTX 2060
Nvidia GeForce RTX 2080 Super
vs
Nvidia GeForce RTX 2060 Super
Nvidia GeForce RTX 2070 Super
vs
Nvidia GeForce RTX 3050 Ti Laptop
Nvidia GeForce RTX 2080 Super
vs
AMD Radeon RX 5700 XT
Nvidia GeForce RTX 2070 Super
vs
KFA2 GeForce RTX 2080 Ti
Price comparison
User reviews
Performance
1. GPU clock speed
1605MHz
1650MHz
The graphics processing unit (GPU) has a higher clock speed.
2.GPU turbo
1770MHz
1815MHz
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
113.3 GPixel/s
116.2 GPixel/s
The number of pixels that can be rendered to the screen every second.
4.floating-point performance
9.06 TFLOPS
11.15 TFLOPS
Floating-point performance is a measurement of the raw processing power of the GPU.
5.texture rate
283.2 GTexels/s
348.5 GTexels/s
The number of textured pixels that can be rendered to the screen every second.
6.GPU memory speed
1750MHz
1937MHz
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
15496MHz
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
448GB/s
495.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
256bit
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 2070 Super
✖Nvidia GeForce RTX 2080 Super
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 2070 Super
✔Nvidia GeForce RTX 2080 Super
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
A lower load temperature means that the card produces less heat and its cooling system performs better.
6.supports ray tracing
✔Nvidia GeForce RTX 2070 Super
✔Nvidia GeForce RTX 2080 Super
Ray tracing is an advanced light rendering technique that provides more realistic lighting, shadows, and reflections in games.
7.Supports 3D
✔Nvidia GeForce RTX 2070 Super
✔Nvidia GeForce RTX 2080 Super
Allows you to view in 3D (if you have a 3D display and glasses).
8.supports DLSS
✔Nvidia GeForce RTX 2070 Super
✔Nvidia GeForce RTX 2080 Super
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 2070 Super)
Unknown. Help us by suggesting a value. (Nvidia GeForce RTX 2080 Super)
This benchmark measures the graphics performance of a video card. Source: PassMark.
Ports
1.has an HDMI output
✔Nvidia GeForce RTX 2070 Super
✔Nvidia GeForce RTX 2080 Super
Devices with a HDMI or mini HDMI port can transfer high definition video and audio to a display.
2.HDMI ports
More HDMI ports mean that you can simultaneously connect numerous devices, such as video game consoles and set-top boxes.
3.HDMI version
HDMI 2.0
HDMI 2.0
Newer versions of HDMI support higher bandwidth, which allows for higher resolutions and frame rates.
4.DisplayPort outputs
Allows you to connect to a display using DisplayPort.
5.DVI outputs
Allows you to connect to a display using DVI.
6.mini DisplayPort outputs
Allows you to connect to a display using mini-DisplayPort.
Price comparison
Cancel
Which are the best graphics cards?
RTX 2070 vs 2080: The Best 4K Graphics Card in 2020
3D Insider is ad supported and earns money from clicks, commissions from sales, and other ways.
One of the biggest trends in gaming in 2020 is 4K. It used to break the bank, but it has since become more affordable. Now, 4K-ready displays are reasonable enough that anyone can get it. There are even gaming-centric monitors that come with high refresh rates and low response times to highlight your skills and maximize performance.
This trend is also translated to graphics cards where the latest generation is geared towards running games in 4K at high frame rates on the highest graphics settings. Nvidia’s RTX 20 series proves just that, since apart from the latest Turing architecture with RTX capabilities, their higher-end cards come with the raw power to run even the most demanding games in 4K smoothly.
Aiming for 4K-ready gaming rigs is still expensive. However, with graphics cards like the RTX 2070, 2080, and their Super variants, you now have a lot of options.
What RTX Brings
Nvidia’s latest Turing cards, the RTX 20 series, comes with brand new features never seen before in GPUs. Apart from the usual shader or CUDA cores, they also packed these latest generation cards with RT and Tensor cores.
The main draw of the RTX cards is ray tracing performed by the RT cores. This feature renders light differently. It allows the graphics card to produce realistic lighting effects, including reflections and shadows, giving you a more immersive gaming experience. Light effects become more striking, subtle, and crisp showing a different dimension on your favorite games.
Another essential feature of these latest Turing cards is its deep learning technology. Using the Tensor cores, this leverages the power of AI to simulate rendering at higher resolutions giving you more available processing power. The card can use fewer resources to render at lower resolutions and upscales it without using more. This gives you leftover power that translates to additional frames for a smoother overall gaming experience.
Performance Comparison
| RTX 2080 Ti | RTX 2080 Super |
RTX 2080 | RTX 2070 Super |
RTX 2070 | |
|---|---|---|---|---|---|
| GPU | TU102 | TU104 | TU104 | TU104 | TU106 |
| CUDA Cores | 4,352 | 3,072 | 2,944 | 2,560 | 2,304 |
| Tensor Cores | 544 | 384 | 368 | 320 | 288 |
| RT Cores | 68 | 48 | 46 | 40 | 36 |
| Base Clock | 1,350 MHz | 1,650 MHz | 1,515 MHz | 1,605 MHz | 1,410 MHz |
| Boost Clock | 1,545 MHz | 1,815 MHz | 1,710 MHz | 1,770 MHz | 1,620 MHz |
| Memory | 11GB GDDR6 | 8GB GDDR6 | 8GB GDDR6 | 8GB GDDR6 | 8GB GDDR6 |
RTX 2070 vs 2080
These graphics cards are two of Nvidia’s latest generation high-performance hardware. The RTX 2080 is a beast of a GPU with 2,944 CUDA cores and, most importantly, the presence of RT and Tensor cores that enables the latest RTX features. The RTX 2070 is no slouch, either. As expected with Nvidia’s product line, the 2070 comes with slightly less performance than the 2080.
Both these cards are in the high-performance category and are meant to run games in 1440p or 4K resolution at high frame rates.
Retail Price: $439
The RTX 2070 is undoubtedly an impressive graphics card that sports the latest technologies supported by Nvidia’s latest Turing architecture. It is a powerful midrange card that comes with the capability to play games in 4K. It is not as smooth as its more powerful sibling, the RTX 2080, but you will definitely be able to play some of your favorite games in 4K.
There are some games though, like Assassin’s Creed Odyssey, where it is barely just playable. Still, overall, you will be able to play at a consistent 60 frames per second. However, where this card truly shines is in 1440p gaming. A resolution step below 4K, although not as detailed, but definitely a much smoother experience.
It is definitely more powerful than its predecessor, the GTX 1070, enjoying a 20% boost in performance. However, its RTX features, especially ray tracing, needs a bit more fine-tuning and games support. The RTX 2080 definitely packs more power, and its refined ray tracing is definitely a plus.
The RTX 2070 is right on the edge of high-performance cards, and without turning on ray tracing, it can offer you a silky-smooth gaming experience on all your favorite games. It may not be the best choice for 4K gaming, but if you are on a budget and want to occasionally play titles in 4K while taking a hit in graphics quality, this is the card for you.
Retail Price: $789
The RTX 2080 is a high-end Turing graphics card that hits the sweet spot in terms of performance and price. Yes, it is on the pricier side of things, but it fully justifies it with how it handles games in 4K, especially with the RTX features turned on.
If you are looking for a card that can handle 4K gaming without spending more for the RTX 2080 Ti, this is an excellent alternative. It is undoubtedly not the most affordable out there, but looking at the specs, this GPU is a significant step up from the previous generation and its lower tiers.
The RTX 2080 is a card that is capable of delivering 60 frames per second at 4K resolutions on the latest Triple-A games. Although you will not get the silky-smooth experience on several games, especially on graphically intensive ones.
The RTX 2080 is an impressive piece of hardware that allows you to enjoy your favorite games. If you are prepared to spend a bit more, you will surely not be disappointed. Other than the RTX 2080 Ti and the latest RTX 2080 Super, no other card comes close to the 2080 in terms of performance. There are games where you really will not be able to push it with the highest settings, a little compromise should do the trick. It is still an excellent card to get, especially since it strikes a good balance between performance and price.
| RTX 2070 | RTX 2080 | |
|---|---|---|
| CUDA Cores | 2,304 | 2,944 |
| Base Clock | 1,410 Mhz | 1,515 Mhz |
| Boost Clock | 1,620 Mhz | 1,710 Mhz |
| Memory Size | 8 GB | 8 GB |
| Memory Type | GDDR6 | GDDR6 |
| Memory Speed | 14 Gbps | 14 Gbps |
| Memory Bandwidth |
448 GB/s | 448 GB/s |
| Bus Width | 256-bit | 256-bit |
| GPU Power (TDP) |
185 W | 215 W |
| Ray Tracing Rays per Second |
6 Billion | 8 Billion |
| RTX Operations per Second |
42 Trillion | 57 Trillion |
| Retail Price | $529 CHECK PRICE |
$739 CHECK PRICE |
RTX 2070 Super vs 2080 Super
Nvidia upgraded their original lineup with a Super version of each of their RTX cards. The RTX 2070 Super and the 2080 Super are two cards that need some attention because they provide significant performance improvements from their vanilla counterparts.
The most notable thing here is that the prices of these two are not drastically different than their vanilla versions. In fact, they are more or less the same with better performance ultimately, the Super cards offer far better value. So, if you are planning to get a graphics card and are choosing between a 2070 or 2080, consider the Super versions.
Retail Price: $529
Part of the Super line of graphics cards, the RTX 2070 Super is the latest mid-tier option that packs a really good punch. When it comes to pricing, it costs similar to the vanilla RTX 2070, but with a performance that comes relatively close to the RTX 2080. Comparing it to last generation cards, it is slightly faster than the GTX 1080 Ti, the most potent mainstream GPU of its generation.
The performance bump from the original RTX 2070 is due to the added computing cores with better clock speeds that come with the new chip. A definite performance upgrade at the same price means the RTX 2070 Super comes in with additional value than its vanilla version.
If the RTX 2070 is capable of running Triple-A games at 4K with slightly lower graphics settings, this takes it a step up. The card can effortlessly push more than 60 frames per second on most games at 4K resolution giving you an ultra-smooth and immersive gameplay experience. Pair it up with a high refresh rate monitor and turn the resolution down a notch. You will have an entirely different gaming experience.
At its price and the added power on top of the vanilla 2070, the Super version is an impressive piece of hardware. It surely has a spot as one of the best value graphics cards in the market that is capable of running games smoothly in 4K.
Retail Price: $769
The RTX 2080 Super may not get the crown of being the fastest mainstream graphics card in the market, but it does come at a close second. You will get top-notch performance with this card with only the RTX 2080 Ti beating it in all aspects. You also save a lot of cash if you choose to get this card rather than the more expensive 2080 Ti. There is really not much difference between the two since you still get the same ray tracing and deep learning features. However, you do sacrifice quite a bit in core count and memory.
Compared with the original RTX 2080, though, it comes with more power and better performance giving you a consistent 60 frames or more in 4K with your favorite game titles. If you are looking for superior performance without spending an insane amount of money for the 2080 Ti, this is the card for you.
There are times when you will need to tweak some settings down to get the full 60 frames per second experience with ray tracing, like Metro Exodus, but for the most part, the RTX 2080 Super should be enough for your triple-A gaming needs. Dialing your resolution down to 1440p will definitely give you the best experience with graphics settings pumped up to maximum, but 4K should not be a problem for the RTX 2080 Super.
If you are willing to spend a little bit extra so you can ensure a smooth 4K gaming experience on every game, you get your hands on for the next two or three years. Getting the RTX 2080 Super is undoubtedly a worthy investment.
| RTX 2070 Super | RTX 2080 Super | |
|---|---|---|
| CUDA Cores | 2,560 | 3,072 |
| Base Clock | 1,605 Mhz | 1,650 Mhz |
| Boost Clock | 1,770 Mhz | 1,815 Mhz |
| Memory Size | 8 GB | 8 GB |
| Memory Type | GDDR6 | GDDR6 |
| Memory Speed | 14 Gbps | 15.5 Gbps |
| Memory Bandwidth |
448 GB/s | 496 GB/s |
| Bus Width | 256-bit | 256-bit |
| GPU Power (TDP) |
215 W | 250 W |
| Ray Tracing Rays per Second |
7 Billion | 8 Billion |
| RTX Operations per Second |
52 Trillion | 63 Trillion |
| Retail Price | $549 CHECK PRICE |
$749 CHECK PRICE |
RTX 2080 Ti vs Others
The RTX 2080 Ti is the most powerful consumer-grade graphics card out there. So, there really is no comparison between this card and the rest of the RTX line, including the Super versions. Although the RTX 2080 Super closed the gap, it is still significant that if you are looking to play your favorite games at 4K at high frame rates, this is the only card that will give you that experience.
Retail Price: $1,299
The RTX 2080 Ti is the graphics card to get if the budget is not really an issue for you. It is the latest and most powerful mainstream GPU available in the market. What makes it so powerful over its previous generation counterpart is its larger chip able to cram in more CUDA, RT, and Tensor cores.
This is the card to get if you are looking to play your favorite games in 4K 144Hz with HDR and G-Sync enabled. It is the fastest out there that will be able to effortlessly handle all of these intense processes. If one is not enough, you can add a second one and use an NVLink connector to improve the insane performance and take it to even new heights.
There is a drawback with getting the RTX 2080 Ti, though, and that is support for the RTX’s ray tracing and deep learning features. However, this is going to be changing soon, and more games will definitely take advantage of these new features and include them.
So, as long as the budget is not an issue, and you are willing to spend upwards of $1,000 for the best graphics cards out there, the RTX 2080 Ti is the one for you. You will be able to easily hit 144 frames per second, allowing you to utilize your high refresh rate 4K monitor for buttery smooth gaming performance.
| RTX 2080 Ti | |
|---|---|
| CUDA Cores | 4,352 |
| Base Clock | 1,350 Mhz |
| Boost Clock | 1,545 Mhz |
| Memory Size | 11 GB |
| Memory Type | GDDR6 |
| Memory Speed | 14 Gbps |
| Memory Bandwidth |
616 GB/s |
| Bus Width | 352-bit |
| GPU Power (TDP) |
250 W |
| Ray Tracing Rays per Second |
10 Billion |
| RTX Operations per Second |
76 Trillion |
| Retail Price | $1,299 CHECK PRICE |
Game Performance Benchmarks
| RTX 2080 Ti | RTX 2080 Super |
RTX 2080 | RTX 2070 Super |
RTX 2070 | |
|---|---|---|---|---|---|
| Fortnite | |||||
| 1080p Epic | 230 FPS | 202 FPS | 170 FPS | 197 FPS | 131 FPS |
| 1440p Epic | 208 FPS | 138 FPS | 129 FPS | 123 FPS | 84 FPS |
| 4K Epic | 105 FPS | 76 FPS | 76 FPS | 72 FPS | 70 FPS |
| Battlefield V | |||||
| 1080p Ultra | 143 FPS | 128 FPS | 136 FPS | 121 FPS | 113 FPS |
| 1440p Ultra | 117 FPS | 102 FPS | 105 FPS | 95 FPS | 76 FPS |
| 4K Ultra | 74 FPS | 62 FPS | 63 FPS | 56 FPS | 60 FPS |
| Civilization VI | |||||
| 1080p Ultra | 198 FPS | 177 FPS | 174 FPS | 170 FPS | 132 FPS |
| 1440p Ultra | 175 FPS | 159 FPS | 152 FPS | 142 FPS | 112 FPS |
| 4K Ultra | 128 FPS | 109 FPS | 104 FPS | 95 FPS | 85 FPS |
| Assassin’s Creed Odyssey |
|||||
| 1080p Ultra | 82 FPS | 78 FPS | 78 FPS | 70 FPS | 65 FPS |
| 1440p Ultra | 73 FPS | 64 FPS | 64 FPS | 62 FPS | 53 FPS |
| 4K Ultra | 53 FPS | 44 FPS | 41 FPS | 40 FPS | 35 FPS |
| Call of Duty Modern Warfare |
|||||
| 1080p Ultra | 213 FPS | 184 FPS | 170 FPS | 156 FPS | 145 FPS |
| 1440p Ultra | 153 FPS | 132 FPS | 122 FPS | 112 FPS | 104 FPS |
| 4K Ultra | 91 FPS | 79 FPS | 73 FPS | 67 FPS | 62 FPS |
| Apex Legends | |||||
| 1080p Ultra | 192 FPS | 162 FPS | 153 FPS | 126 FPS | 139 FPS |
| 1440p Ultra | 143 FPS | 121 FPS | 114 FPS | 94 FPS | 104 FPS |
| 4K Ultra | 86 FPS | 72 FPS | 68 FPS | 62 FPS | 56 FPS |
The Perfect Graphics Card for Your Needs
The Best 4K Graphics Card
| GeForce RTX 2080 Ti |
|---|
| ✔ Fastest consumer-grade graphics card |
| ✔ Can effortlessly do 4K at high or ultra settings at 60 fps or more |
| ✔ Overclocked models available for added power |
If you are keen on playing your favorite Triple-A and e-sports titles at 4K at the highest graphical settings and ultra-smooth movements, then the RTX 2080 Ti is the best card for this job. Other than the RTX Titan, which is more of a professional-level GPU, this is the fastest that you can get in the market.
The card can easily handle just about any game, even the most graphically-intensive ones. Getting this card will also future-proof your system, ensuring that you will not have to buy a new one each time a new generation is released.
With prices over $1,000, it surely is not the card to pick up if you want to maximize price to performance. However, as long as the budget is not an issue for you, then this is definitely one of those luxury purchases that are worth it. If you are a big fan of gaming and do a lot of graphics-intensive productivity tasks like 3D modeling and rendering, this is the card for you.
Alternative Hardware: GeForce RTX 2080 Super
The Best 1440p Graphics Card
| GeForce RTX 2070 Super |
|---|
| ✔ Performance close to the vanilla RTX 2080 at a lower price |
| ✔ Price is similar to the vanilla RTX 2070 |
| ✔ All the Turing RTX features like ray tracing and deep learning without the excessive premium |
Even though the RTX 2070 Super can handle 4K gaming effortlessly by simply taking a tiny hit in terms of quality, it is best suited for 1440p. Lowering your resolution by just a notch will enable you to enjoy the power and RTX features of the 2070 Super.
The Super variant does come with a lot of advantages over the original RTX 2070, and it shows in the performance for 4K and 1440p gaming. One thing to note about the RTX 2070 Super is that its power levels are much improved without affecting its price. Offering you more value since it can go toe to toe with the RTX 2080.
As a graphics card at a reasonable price point with solid performance, the RTX 2070 Super is definitely an excellent choice. You also get to enjoy all the RTX features without sacrificing frame rates, especially in 1440p resolution.
Best Value High Performance Graphics Card
GEFORCE RTX 2070 SUPER
Both the RTX 2080 and the 2070 are high-performance cards, which means they are capable of providing you 4K gaming experience. However, the price of both the RTX 2080 Ti and the 2080 Super is a bit on the expensive side. The good news is that the RTX 2070 Super is on the more reasonable side and offers excellent performance for its price. This makes it a card that will provide you with the best value.
It is a graphics card that is on the edge with power similar to the vanilla RTX 2080 for optimum 4K performance. Where it excels, though, is in 1440p as it can give you insane frame rates even at the highest possible graphics settings. You can then pair it up with a high refresh rate monitor for an immersive gaming experience.
Wrap Up
With the options at your fingertips, 4K gaming is not as expensive as it was a couple of years ago. Now, you do not need to get the most powerful graphics card to satisfy your 4K gaming itch.
The RTX 2080 Ti, is an absolute beast and is a great card overall. However, you do not necessarily need to get it to enjoy a high resolution gaming experience. There are a couple of choices like the RTX 2080 Super and the 2070 Super, which can offer you a taste of 4K gaming.
The high performance RTX family is definitely an impressive line of graphics cards. They can provide you unbridled power and even value so you can enjoy your favorite games even when you have a budget to stick to or not.
0024 215W vs 250W
- 2.09 TFLOPS higher than FLOPS?
11.15 TFLOPS vs 9.06 TFLOPS - 187MHz faster memory speed?
1937MHz vs 1750MHz - 1496MHz higher effective clock speed?
15496MHz vs 14000MHz - 65.3 GTexels/s higher number of textured pixels? 9more memory bandwidth?
495.9GB/s vs 448GB/s - 512 more stream processors?
3072 vs 2560 - 32 more texture units (TMUs)?
192 vs 160 - 1 more DisplayPort outputs?
3 vs 2
Which comparisons are the most popular?
Nvidia GeForce RTX 2070 Super
vs
Nvidia GeForce RTX 3060
Nvidia GeForce RTX 2080 Super
vs
Nvidia GeForce RTX 3060
Nvidia GeForce RTX 2070 Super
vs
Nvidia GeForce RTX 3060 Ti
Nvidia GeForce RTX 2080 Super
vs
Nvidia GeForce RTX 3070 Ti
Nvidia GeForce RTX 2070 Super
vs
Nvidia GeForce RTX 3070 Ti
GeForce RTX 20003
vs
Nvidia GeForce RTX 3070
Nvidia GeForce RTX 2070 Super
vs
Nvidia GeForce RTX 3050 Laptop
Nvidia GeForce RTX 2080 Super
vs
Nvidia GeForce RTX 3080
Nvidia GeForce RTX 2070 Super
vs
Nvidia GeForce RTX 3070
Nvidia GeForce RTX 2080 Super
vs
Nvidia GeForce RTX 3080 Ti
Nvidia GeForce RTX 2070 Super
vs
0003
Nvidia Geforce GTX 1660 Super
Nvidia GeForce RTX 2080 Super
vs
Nvidia GeForce RTX 3060 Ti
Nvidia GeForce RTX 2070 Super
vs
AMD Radeon RX 6500 XT
Nvidia GeForce RTX 2080 Super
VS
NVIDIA GeForce GTX 1660 Super
NVIDIA GeForce RTX 2070 Super
VS
NVIDIA GEFORCE RTX 2060
NVIDIA GEFORCE SUPER
9000 NVIDIA
000 NVIDI0003
Nvidia GeForce RTX 2070 Super
vs
Nvidia GeForce RTX 3050 Ti Laptop
Nvidia GeForce RTX 2080 Super
vs
AMD Radeon RX 5700 XT
Nvidia GeForce RTX 2070 Super
vs
KFA2 GeForce RTX 2080 Ti
Price Match
User Reviews
Performance
1. GPU Clock Speed
1605MHz
1650MHz
The graphics processing unit (GPU) has a higher clock speed.
2.turbo GPU
1770MHz
1815MHz
When the GPU is running below its limits, it can jump to a higher clock speed to increase performance.
3.pixel rate
113.3 GPixel/s
116.2 GPixel/s
The number of pixels that can be displayed on the screen every second.
4.flops
9.06 TFLOPS
11.15 TFLOPS
FLOPS is a measure of GPU processing power.
5.texture size
283.2 GTexels/s
348.5 GTexels/s
Number of textured pixels that can be displayed on the screen every second.
6.GPU memory speed
1750MHz
1937MHz
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
15496MHz
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
448GB/s
495.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
256bit
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 2070 Super
✖Nvidia GeForce RTX 2080 Super
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 2070 Super
✔Nvidia GeForce RTX 2080 Super
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
Lower boot temperature means that the card generates less heat and the cooling system works better.
6.supports ray tracing
✔Nvidia GeForce RTX 2070 Super
✔Nvidia GeForce RTX 2080 Super
Ray tracing is an advanced light rendering technique that provides more realistic lighting, shadows and reflections in games.
7. Supports 3D
✔Nvidia GeForce RTX 2070 Super
✔Nvidia GeForce RTX 2080 Super
Allows you to view in 3D (if you have a 3D screen and glasses).
8.supports DLSS
✔Nvidia GeForce RTX 2070 Super
✔Nvidia GeForce RTX 2080 Super
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 2070 Super)
Unknown. Help us offer a price. (Nvidia GeForce RTX 2080 Super)
This test measures the graphics performance of a graphics card. Source: Pass Mark.
Ports
1.has HDMI output
✔Nvidia GeForce RTX 2070 Super
✔Nvidia GeForce RTX 2080 Super
Devices with HDMI or mini HDMI ports can stream HD video and audio to the connected display.
2.HDMI connectors
More HDMI connectors allow you to connect multiple devices at the same time, such as game consoles and TVs.
HDMI 3.Version
HDMI 2.0
HDMI 2.0
New HDMI versions support higher bandwidth for higher resolutions and frame rates.
4. DisplayPort outputs
Allows connection to a display using DisplayPort.
5.DVI outputs
Allows connection to a display using DVI.
Mini DisplayPort 6.outs
Allows connection to a display using Mini DisplayPort.
Price match
Cancel
Which graphics cards are better?
is the obvious choice for GECID.com. Page 1
::>Video cards
>2019
> NVIDIA GeForce RTX 2070 SUPER versus RTX 2080, RTX 2070 and Radeon VII: the obvious choice
08-08-2019
Page 1
Page 2
One page
In early July, NVIDIA decided to update its GeForce RTX 20 line of graphics cards and released the RTX 20 SUPER series. It includes three models: GeForce RTX 2060 SUPER, RTX 2070 SUPER and RTX 2080 SUPER. All of them are based on a combination of 12nm Turing microarchitecture and GDDR6 memory. The performance bonus is achieved by increasing the structural blocks in the GPU and raising its clock frequencies. The RTX 2080 SUPER has also increased the memory frequency.
The GeForce RTX 2070 SUPER was the first to come to us for testing. It retains the recommended price tag of the regular RTX 2070, but boasts 4 additional SM blocks with proportional growth of CUDA cores, texture modules, RT cores and Tensor cores. Reference clock speeds increased by 9-fourteen%. The video memory subsystem has not changed, but the power consumption has increased from 175 to 215 watts.
We have already got acquainted with this video card using the Palit GeForce RTX 2070 SUPER JetStream as an example. Therefore, we will only briefly recall that it is distinguished by a reinforced 12-phase power subsystem, LED backlighting and a massive, almost 3-slot cooler with two 96mm fans and a stiffening plate on the back.
The card also received two BIOS chips. The highlight of the first is the factory overclocking of the dynamic frequency by 2.5%. And the second is the hybrid cooler mode: at low GPU temperatures, the fans stop spinning. Here the choice is yours: overclocking with the cooler running all the time or acoustic comfort at reference frequencies.
But not everything is going smoothly with the opponents. We have only GeForce RTX 2080 in the hands of the same Palit. It pleases with DrMOS chips in power circuits and a 2-slot cooling system with two 9 cm fans. There is also a 6% overclocking of the dynamic frequency of the GPU.
We didn’t have other opponents. For several weeks they asked partners for GeForce RTX 2070 , but this time it was not possible to get it. Radeon RX 5700 XT is promised to us, but has not yet been delivered, and it is very difficult to catch the Radeon VII , since the copy for the press constantly wanders from one edition to another.
Therefore, we had to interpolate the results of the RTX 2070 and Radeon VII based on the two previous comparisons with the RTX 2080. Where possible, we did not use the average difference between them, but focused on each benchmark in order to get the results more accurate. If we manage to get our hands on an RTX 2070 and one of the competing Radeon RX 5700s, we’ll be sure to retest.
The following stand was used for testing:
- Intel Core i9-9900K
- Vinga CL3008B
- ASRock Z390 Phantom Gaming SLI
- 4x 8GB DDR4-3600 CORSAIR Dominator Platinum RGB
- Apacer AS2280P2 M.2 NVMe 480 GB
- Apacer Panther AS340 960GB
- Seagate Barracuda Pro 4TB ST4000DM006
- Vinga VPS-1200Pl
- Vinga Ark
- AOC U2879VF
Gameplays recorded by an external system with AVerMedia Live Gamer 4K, i.e. without performance loss. The program FPS Monitor was used for monitoring.
We will compare sequentially in three resolutions. We display only the video of two video cards that we really managed to test, and the calculated data for the RTX 2070 and Radeon VII will also appear on the charts.
Let’s start with Far Cry New Dawn . In Full HD at the maximum preset with HD textures, it requires a little more than 5 GB of video memory, so the buffer size is not a problem for all the presented video cards. The RTX 2080 was able to maintain the lead, but only by a narrow margin over the 2070 SUPER.
With the transition to Quad HD, the requirements for the amount of video memory increase slightly, but the difference in the performance of graphic processors is already better felt. Therefore, the advantage of the RTX 2080 over the new product rises to 4-8%.
Ultra HD eats up about 7 GB of video memory — a lot, but not critical for these video cards. Overall figures are falling, but in general, the difference between the RTX 2080 and the new product is at the level of 5-7%.
In Full HD at the maximum preset, the benchmark The Division 2 turned out to be not too gluttonous, requiring only 5 GB of video memory for its needs. Nothing threatens the leadership of the GeForce RTX 2080, and the second place according to calculations will be contested by the Radeon VII and 2070 SUPER.
In Quad HD, Radeon VII can only win on very rare events. Otherwise, this confrontation will remain a novelty. But the GeForce RTX 2080 is ahead of it by 8-9%.
In 4K, the benchmark modestly requires about 7 GB of video memory for its needs, although the game will definitely gobble up more than 10. The advantage of the GeForce RTX 2080 over the 2070 SUPER reaches 20%. In turn, the novelty is only ahead of its predecessor by a maximum of 7%.
Benchmark World War Z in Vulkan mode impressed with its modesty — it needs a little more than 3 GB of video memory in Full HD at ultra settings. In addition, it does not fully load the GPUs, so the difference between 2080 and 2070 SUPER is in the range of 3-4%.
With the transition to Quad HD, video memory consumption increases by 200-300 MB, but the GPU load is approximately the same as the difference in results between two real video cards.
You can safely run the benchmark in Ultra HD as well – it requires only 4.5 GB of video memory. But the loading of GPUs has not changed at all: either the monitoring is lying, or the game is poorly optimized for Vulkan. In any case, the RTX 2070 SUPER confidently takes the second place. No more than 6% separates it from the leader.
But we decided to test Strange Brigade in DirectX 12 mode in order to get a consistently high load on video cards. In Full HD, you can count on very comfortable results for all participants. The palm in terms of average frame rate should be taken by Radeon VII. According to the rest of the statistics, it remains for the GeForce RTX 2080.
In Quad HD, the order of video cards does not change, as does the gap between the GeForce RTX 2080 and the test novelty — it is still within 6-8%.
Even at 4K, the GeForce RTX 2070 SUPER promises a comfortable 60+ FPS. In general, its performance is a maximum of 22% higher than its predecessor. But if this is not enough for you, then an overpayment for the GeForce RTX 2080 promises only a 5-7% bonus.
GeForce RTX 2070 vs GeForce RTX 2080 SUPER
GeForce RTX 2070 vs GeForce RTX 2080 SUPER — Th200
Contents
- Introduction
- Features
- Tests
- Games
- Key differences
- Conclusion
- Comments
Video card
Video card
Introduction
We compared two graphics cards: NVIDIA GeForce RTX 2070 vs NVIDIA GeForce RTX 2080 SUPER. On this page, you will learn about the key differences between them, as well as which one is the best in terms of features and performance.
The NVIDIA GeForce RTX 2070 is a Turing-based GeForce 20 generation graphics card released Oct 17th, 2018. It comes with 8GB of GDDR6 memory running at 1750MHz, has a 1x 8-pin power connector, and consumes up to 165W.
NVIDIA GeForce RTX 2080 SUPER is a Turing-based GeForce 20 generation graphics card released on Jul 23rd, 2019. It comes with 8GB GDDR6 memory running at 1937MHz, has 1x 6-pin + 1x 8-pin power connector and consumes up to 165 watts.
348.5 GFLOPS (1:32)
Clock Speeds
Basic frequency
1410 MHZ
1650 MHZ
Maximum frequency
MHZ
1815 MHZ 9000
Render Config
Shading Units
2304
3072
Texture Units
192
Raster UNITS
64
64
SM CUUNT
36
48
Tensor Cores
288
384
RT Cores
36
48
Graphics Features
DirectX
12 Ultimate (12_2)
12 Ultimate (12_2)
OpenGL
4. 6
4.6
OpenCl
3.0
3.0
CUDA
7.5
VULKAN
1.2
1.2
Board Design
Heating
175W
250W
Power connectors
1x 8-pin
1x 6-Pin + 1x 8-Pin
9000 Graphics
3DMark is a benchmarking tool designed and developed by UL to measure the performance of computer hardware. Upon completion, the program gives a score, where a higher value indicates better performance.
NVIDIA GeForce RTX 2070
NVIDIA GeForce RTX 2080 SUPER
+28%
Blender bmw27
Blender is the most popular program for creating 3D content. It has its own test, which is widely used to determine the rendering speed of processors and video cards. We chose the bmw27 scene. The result of the test is the time taken to render the given scene.
NVIDIA GeForce RTX 2070
NVIDIA GeForce RTX 2080 SUPER
+23%
Th200 RP
Th200 RP is a test created by Th200. It measures the raw power of the components and gives a score, with a higher value indicating better performance.
NVIDIA GeForce RTX 2070
NVIDIA GeForce RTX 2080 SUPER
+26%
Games
1920×1080, Ultra
| Game | GeForce RTX 2070 | GeForce RTX 2080 SUPER |
|---|---|---|
| Anno 1800 | ||
| Assassin’s Creed Odyssey | ||
| Battlefield 5 | ||
| Battlefield V | ||
| Cyberpunk 2077 | ||
| DOOM Eternal | ||
| Far Cry 5 | ||
| Grand Theft Auto V | ||
| Hitman 2 | ||
| Hitman 3 | ||
| Metro Exodus | ||
| Monster Hunter World | ||
| Red Dead Redemption 2 | ||
| Shadow of the Tomb Raider | ||
| The Witcher 3 | ||
| Average | 106. |
124.60 fps |
2560×1440, Ultra
| Game | GeForce RTX 2070 | GeForce RTX 2080 SUPER |
|---|---|---|
| Anno 1800 | ||
| Assassin’s Creed Odyssey | ||
| Assassin’s Creed Valhalla | ||
| Battlefield 5 | ||
| Battlefield V | ||
| Cyberpunk 2077 | ||
| DOOM Eternal | ||
| Far Cry 5 | ||
| Grand Theft Auto V | ||
| Hitman 2 | ||
| Hitman 3 | ||
| Metro Exodus | ||
| Monster Hunter World | ||
| Red Dead Redemption 2 | ||
| Shadow of the Tomb Raider | ||
| The Witcher 3 | ||
| Average | 78. |
93.69 fps |
3840×2160, Ultra
| Game | GeForce RTX 2070 | GeForce RTX 2080 SUPER |
|---|---|---|
| Anno 1800 | ||
| Assassin’s Creed Odyssey | ||
| Assassin’s Creed Valhalla | ||
| Battlefield 5 | ||
| Battlefield V | ||
| Cyberpunk 2077 | ||
| DOOM Eternal | ||
| Far Cry 5 | ||
| Grand Theft Auto V | ||
| Hitman 2 | ||
| Hitman 3 | ||
| Metro Exodus | ||
| Monster Hunter World | ||
| Red Dead Redemption 2 | ||
| Shadow of the Tomb Raider | ||
| Average | 44. |
54.58 fps |
Key differences
Why is NVIDIA GeForce RTX 2070 better than NVIDIA GeForce RTX 2080 SUPER?
Uses 31% less power — 175W vs 250W
Why is NVIDIA GeForce RTX 2080 SUPER better than NVIDIA GeForce RTX 2070?
Newer — released 9 months later
Has 26% higher average FPS in games at 1080p — 124.60 FPS versus 106.55 FPS
Has 26% higher average FPS in games at 1440p — 93.69 FPS versus 78.39 FPS
Has 24% higher average FPS in games at 2160p — 54.58 FPS versus 44.14 FPS
Has 11% higher throughput — 495.9 GB/s vs 448.0 GB/s
Has 13% more bandwidth high pixel fill rate — 116.2 GPixel/s vs 103.7 GPixel/s
Has 50% higher texture fill rate — 348.5 GTexel/s vs 233.3 GTexel/s
Has more texture units +48
Has 768 more shading units
Has 96 more tensor cores
Has 12 more RT cores
Conclusion
Which is better GeForce RTX 2080 SUPER or GeForce RTX 2070?
The GeForce RTX 2080 SUPER delivers 26% better performance, consumes up to 43% more energy and holds the same amount of memory. According to our research, GeForce RTX 2080 SUPER 3990X is more powerful than GeForce RTX 2070.
Is GeForce RTX 2080 SUPER good today?
GeForce RTX 2080 SUPER has 8 GB memory and shows an average of 93.69 FPS in 13 games at 1440p, making it an excellent choice for games in 2022.
This graphics card will give you a good experience in every game on reasonable graphics settings.
What AMD graphics cards is equivalent to GeForce RTX 2080 SUPER?
The Radeon RX Vega 64 Liquid Cooling is AMD’s closest competitor to the GeForce RTX 2080 SUPER. It is 7% more powerful, uses 38% more energy, and holds the same amount of memory.
What NVIDIA graphics cards is equivalent to GeForce RTX 2080 SUPER?
The GeForce GTX 1080 Ti 10 GB is NVIDIA’s closest competitor to the GeForce RTX 2080 SUPER. It is 2% more powerful, uses the same amount of energy, and holds 2 GB less memory.
How does GeForce RTX 2070 perform compared to GeForce RTX 2080 SUPER and other graphics cards?
Relative performance
Total performance
Bench performance
GeForce RTX 2070 Mobile vs GeForce RTX 2080 SUPER
GeForce RTX 2070 Mobile vs GeForce RTX 2080 SUPER — Th200
Contents
- Introduction
- Features
- Tests
- Games
- Key differences
- Conclusion
- Comments
Video card
Video card
Introduction
We compared two graphics cards: NVIDIA GeForce RTX 2070 Mobile vs. NVIDIA GeForce RTX 2080 SUPER. On this page, you will learn about the key differences between them, as well as which one is the best in terms of features and performance.
The NVIDIA GeForce RTX 2070 Mobile is a Turing-based GeForce 20 Mobile generation graphics card released Jan 29th, 2019. It comes with 8GB of GDDR6 memory running at 1750MHz and consumes up to 115W.
NVIDIA GeForce RTX 2080 SUPER is a Turing-based GeForce 20 generation graphics card released on Jul 23rd, 2019. It comes with 8GB GDDR6 memory running at 1937MHz, has 1x 6-pin + 1x 8-pin power connector and consumes up to 165 watts.
495.9 GB/S
Theoretical Performance
Pixel filling speed
92.16 GPIXEL/S
116.2 GPIXEL/S 9000 performance
13.27 TFLOPS (2:1)
22.30 TFLOPS (2:1)
FP32 (float) performance
6.636 TFLOPS
11.15 TFLOPS
FP64 (double) performance
207.4 GFLOPS (1:32)
348. 5 GFLOPS (1:32)
Clock Speeds
Basic frequency
1215 MHZ
1650 MHZ
Maximum frequency
1440 MHZ 9000
Render Config
Shading Units
2304
3072
Texture Units
192
Raster UNITS
64
64
SM CUUNT
36
48
Tensor Cores
288
384
RT Cores
36
48
Graphics Features
DirectX
12 Ultimate (12_2)
12 Ultimate (12_2)
OpenGL
4.6
4.6
OpenCl
3.0
3.0
CUDA
7.5
VULKAN
1.2
1.2
Board Design
Heating
115W
250W
Power connectors
None
1x 6-Pin + 1x 8-pin
MXM MODULE
DUAL-SLOT
Tonses 9000 RP 9000 RP 9000 RP RP is a test created by Th200. It measures the raw power of the components and gives a score, with a higher value indicating better performance.
NVIDIA GeForce RTX 2070 Mobile
NVIDIA GeForce RTX 2080 SUPER
+37%
3DMark Graphics
3DMark is a test tool designed and developed by UL to measure the performance of computer hardware. Upon completion, the program gives a score, where a higher value indicates better performance.
NVIDIA GeForce RTX 2070 Mobile
NVIDIA GeForce RTX 2080 SUPER
Blender bmw27
Blender is the most popular 3D content creation software. It has its own test, which is widely used to determine the rendering speed of processors and video cards. We chose the bmw27 scene. The result of the test is the time taken to render the given scene.
NVIDIA GeForce RTX 2070 Mobile
NVIDIA GeForce RTX 2080 SUPER
Games
1920×1080, Ultra
| Game | GeForce RTX 2070 Mobile | GeForce RTX 2080 SUPER |
|---|---|---|
| Anno 1800 | ||
| Assassin’s Creed Odyssey | ||
| Battlefield V | ||
| Cyberpunk 2077 | ||
| DOOM Eternal | ||
| Far Cry 5 | ||
| Hitman 2 | ||
| Hitman 3 | ||
| Metro Exodus | ||
| Red Dead Redemption 2 | ||
| Shadow of the Tomb Raider | ||
| The Witcher 3 | ||
| Average | 0. |
124.60 fps |
2560×1440, Ultra
| Game | GeForce RTX 2070 Mobile | GeForce RTX 2080 SUPER |
|---|---|---|
| Anno 1800 | ||
| Assassin’s Creed Odyssey | ||
| Assassin’s Creed Valhalla | ||
| Battlefield V | ||
| Cyberpunk 2077 | ||
| DOOM Eternal | ||
| Far Cry 5 | ||
| Hitman 2 | ||
| Hitman 3 | ||
| Metro Exodus | ||
| Red Dead Redemption 2 | ||
| Shadow of the Tomb Raider | ||
| The Witcher 3 | ||
| Average | 0. |
93.69 fps |
3840×2160, Ultra
| Game | GeForce RTX 2070 Mobile | GeForce RTX 2080 SUPER |
|---|---|---|
| Anno 1800 | ||
| Assassin’s Creed Odyssey | ||
| Assassin’s Creed Valhalla | ||
| Battlefield V | ||
| Cyberpunk 2077 | ||
| DOOM Eternal | ||
| Far Cry 5 | ||
| Hitman 2 | ||
| Hitman 3 | ||
| Metro Exodus | ||
| Red Dead Redemption 2 | ||
| Shadow of the Tomb Raider | ||
| Average | 0. |
54.58 fps |
Key differences
Why is NVIDIA GeForce RTX 2070 Mobile better than NVIDIA GeForce RTX 2080 SUPER?
Uses 54% less power — 115W vs 250W
Why is NVIDIA GeForce RTX 2080 SUPER better than NVIDIA GeForce RTX 2070 Mobile?
Newer — released 5 months later
Has 37% faster performance
Has 11% higher throughput — 495.9 GB/s vs 448.0 GB/s
Has 27% faster pixel fill rate — 116.2 GPixel/s vs 92.16 GPixel/s
Has 69% higher texture fill rate — 348.5 GTexel/s vs 207.4 GTexel/s
Has more texture units +48
Has 768 more shading units
Has 96 more tensor cores
12 more RT cores
Conclusion
Which is better GeForce RTX 2080 SUPER or GeForce RTX 2070 Mobile?
The GeForce RTX 2080 SUPER delivers 37% better performance, consumes up to 118% more energy and holds the same amount of memory. According to our research, the GeForce RTX 2080 SUPER 3990X is more powerful than the GeForce RTX 2070 Mobile.
Is GeForce RTX 2080 SUPER good today?
GeForce RTX 2080 SUPER has 8 GB memory and shows an average of 93.69 FPS in 13 games at 1440p, making it an excellent choice for games in 2022.
This graphics card will give you a good experience in every game on reasonable graphics settings.
What AMD graphics cards is equivalent to GeForce RTX 2080 SUPER?
The Radeon RX Vega 64 Liquid Cooling is AMD’s closest competitor to the GeForce RTX 2080 SUPER. It is 7% more powerful, uses 38% more energy, and holds the same amount of memory.
What NVIDIA graphics cards is equivalent to GeForce RTX 2080 SUPER?
The GeForce GTX 1080 Ti 10 GB is NVIDIA’s closest competitor to the GeForce RTX 2080 SUPER. It is 2% more powerful, uses the same amount of energy, and holds 2 GB less memory.
How does GeForce RTX 2070 Mobile perform compared to GeForce RTX 2080 SUPER and other graphics cards?
Relative performance
Total performance
Bench performance
Mobile productivity
NVIDIA GeForce RTX 2070 Super vs NVIDIA GeForce RTX 2080.
Comparative specifications and benchmarks of video cards
VS
General information
The general information section of the video card comparison list contains information about the release date, type, overall rating and other useful data to determine the winner between NVIDIA GeForce RTX 2070 Super and NVIDIA GeForce RTX 2080. Please note that the comparison takes place across all indicators, and below are ratings from synthetic benchmarks that define different criteria in games and work applications.
$ 699
$ 1436 (2.9x MSRP)
Actual price
$ 1591 (2.3x msrp)
18.25
16.000 9000 Desktop
Market segment
Desktop
Specifications
Which graphics card is better in comparison NVIDIA GeForce RTX 2070 Super vs NVIDIA GeForce RTX 2080 in manufacturing process, power consumption, and GPU base and turbo frequency is the most important part contained in the rating of video cards.
PCIE 3. 0 X16
Interface
PCIE 3.0 X16
267 MM
length
267 MM
1x 6-Pin + 1x 8-Pin 9000
Memory (frequency and overclocking)
Graphics card memory plays an important role in both gaming and graphics applications. The higher the standard ( GDDR ), the better. It directly affects the speed and efficiency of data processing. What is the difference in type, base and turbo frequency, GDDR bandwidth between NVIDIA GeForce RTX 2070 Super and NVIDIA GeForce RTX 2080:
GDDR6
Type of memory
GDDR6
8 GB
Maximum RAM AMOUNT
8 GB
256 BIT
DISTRUCTION of memory
256 BIT
14000 14000 MHZ
9000 Memory Memory Memory Memory Memory Memory Memory Memory Memory Memory Memory Memory 448.0 Gb/s
memory capacity
448.0 gb/s
—
Demeded memory
—
Support for ports and displays
Let’s find out the difference in ports that are equipped with NVIDIA GEFORCE RTX 2070 SUPER and NVIDIA GEFOR RTX 2080. Pay attention to the number of ports and the maximum resolution of supported monitors.
1x HDMI, 3X DisplayPort, 1x USB Type-C
Connections to
1x HDMI, 3x DisplayPort, 1x USB Type-C
+
Support G-SYNC
+
9000 + 9000 + 9000.
+
Technology
Let’s see what the difference is. It is worth noting that NVIDIA and AMD use different technologies.
+
VR support
+
+
Multiple monitors
+
7.5
CUDA
7.5
API support
The confrontation between the two rivals NVIDIA GeForce RTX 2070 Super and NVIDIA GeForce RTX 2080 is almost over. Hardware support (API) does not greatly affect the overall performance, it is not taken into account in synthetic benchmarks and other performance tests.
12 Ultimate (12_1)
DirectX
12 Ultimate (12_1)
4.6
OpenGL
4.6
1.2.0003
NVIDIA GeForce RTX 2080
3DMark Ice Storm GPU
The Ice Storm multi-platform test shows the performance of a graphics card using the screen rendering method. Standard test conditions — 1280*720 (720p).
NVIDIA GeForce RTX 2070 Super
486649 (100%)
NVIDIA GeForce RTX 2080
436117 (89%)
3DMark Cloud Gate GPU
Unlike Ice Storm, 3DMark’s Cloud Gate test uses more resource intensive scenes. The better the final score, the faster your graphics card. Processing is done with DirectX 10.
NVIDIA GeForce RTX 2070 Super
127163 (88%)
NVIDIA GeForce RTX 2080
143576 (100%)
3DMark Fire Strike Score
This is an advanced graphics card benchmark. When using DirectX 11 for processing, typical testing time is 15 minutes. The higher the score, the faster the graphics card.
NVIDIA GeForce RTX 2070 Super
20245 (98%)
NVIDIA GeForce RTX 2080
20492 (100%)
3DMark Fire Strike Graphics
Complex graphic scenes require all the graphics card resources. They use the entire RAM and computing power. The test’s results can be viewed below.
NVIDIA GeForce RTX 2070 Super
24394 (88%)
NVIDIA GeForce RTX 2080
27620 (100%)
3DMark 11 Performance GPU
This benchmark analyzes the gaming performance of a video card using Direct X 11 (multithreading, tessellation, shader calculations).
NVIDIA GeForce RTX 2070 Super
33460 (83%)
NVIDIA GeForce RTX 2080
40278 (100%)
3DMark Vantage Performance
This Direct X10 based benchmark contains tests for artificial intelligence, physics and 6 computational tests.
NVIDIA GeForce RTX 2070 Super
69049 (100%)
NVIDIA GeForce RTX 2080
66631 (96%)
SPECviewperf 12 — Solidworks
This is a world famous benchmark for determining the performance of a graphics card in applications. In testing, graphic models and real program scenes are used.
NVIDIA GeForce RTX 2070 Super
72 (100%)
NVIDIA GeForce RTX 2080
70 (97%)
SPECviewperf 12 — Siemens NX
Siemens NX (snx-02) is a dedicated SPECviewperf 12 suite for graphical load tracing. It includes many rendering modes.
NVIDIA GeForce RTX 2070 Super
12 (100%)
NVIDIA GeForce RTX 2080
12 (100%)
SPECviewperf 12 — Showcase
This test is based on Autodesk Showcase 2013. It introduces shading and shadow projection modes.
NVIDIA GeForce RTX 2070 Super
128 (100%)
NVIDIA GeForce RTX 2080
SPECviewperf 12 — Medical
This is a special set of benchmarks designed as a 3D rendering application. It uses all the resources of the video card.
NVIDIA GeForce RTX 2070 Super
42 (93%)
NVIDIA GeForce RTX 2080
45 (100%)
SPECviewperf 12 — Maya
Maya-04, developed by SPECviewperf 12, contains many rendering modes, including fill, anti-alias, and transparency.
NVIDIA GeForce RTX 2070 Super
150 (100%)
NVIDIA GeForce RTX 2080
150 (100%)
SPECviewperf 12 — Energy
This is a pre-installed SPECviewperf 12 set called Energy-01, which is used to determine the power of the video card. It performs volumetric rendering.
NVIDIA GeForce RTX 2070 Super
12 (100%)
NVIDIA GeForce RTX 2080
12 (100%)
SPECviewperf 12 — Creo
This benchmark offers a test of the video card’s power in various rendering modes (anti-aliasing, reflection fill and edge fill).
NVIDIA GeForce RTX 2070 Super
50 (96%)
NVIDIA GeForce RTX 2080
52 (100%)
SPECviewperf 12 — Catia
This video card power and speed test includes rendering aircraft and car models. The better the score, the more powerful your graphics card.
NVIDIA GeForce RTX 2070 Super
98 (89%)
NVIDIA GeForce RTX 2080
109 (100%)
SPECviewperf 12 — 3ds Max
NVIDIA GeForce RTX 2070 Super
212 (100%)
NVIDIA GeForce RTX 2080
205 (96%)
Passmark
Passmark is an excellent benchmark that is updated regularly and shows relevant graphics card performance information.
NVIDIA GeForce RTX 2070 Super
18126 (96%)
NVIDIA GeForce RTX 2080
18746 (100%)
Popular comparisons with selected graphics cards
| one. | NVIDIA GeForce RTX 2070 Super vs. NVIDIA GeForce GTX 1660 Ti | |
|
2. |
NVIDIA GeForce RTX 2080 vs. AMD Radeon VII | |
| 3. | Intel HD Graphics 620 vs. NVIDIA GeForce RTX 2080 | |
| four. |
AMD Radeon RX Vega 11 vs. |
|
| 5. | NVIDIA GeForce RTX 2070 Super vs. AMD Radeon VII | |
| 6. | NVIDIA GeForce GTX 660 vs. NVIDIA GeForce RTX 2080 | |
| 7. |
NVIDIA GeForce RTX 2070 Super vs. |
|
| eight. | AMD Radeon RX 5700XT vs. NVIDIA GeForce RTX 2080 | |
| 9. | NVIDIA GeForce RTX 2070 Super vs. NVIDIA GeForce RTX 2080 | |
| ten. |
NVIDIA GeForce RTX 3070 Ti vs. |
|
| eleven. | NVIDIA GeForce GTX 1650 vs. NVIDIA GeForce RTX 2070 Super | |
| 12. | AMD Radeon Pro Vega 20 vs. NVIDIA GeForce RTX 2070 Super | |
| 13. |
NVIDIA GeForce RTX 3070 Max-Q vs. |
|
| fourteen. | NVIDIA GeForce RTX 2070 Super vs. NVIDIA GeForce GTX 980 Ti | |
| fifteen. | NVIDIA GeForce RTX 2080 vs. NVIDIA GEFORCE RTX 3060 |
RTX 2070 SUPER vs RTX 2080 SUPER comparison charts
April 23, 2020
Matt Mills
Hardware, Tips and Tricks
0
You’ve decided you’re going to buy the high-end video card, but as usual you’ll have doubts about which model to invest your money in. For this reason, in this article we are going to make a technical comparison of two of NVIDIA’s high-end graphics cards: RTX 2070 SUPER vs. RTX 2080 SUPER . Is the premium RTX 2080 SUPER worth it compared to the RTX 2070 SUPER?
In this comparison, we are not going to evaluate which of the two graphics cards is better, since by definition the RTX 2080 SUPER is superior to the RTX 2070 SUPER. What we’re going to do is put them head to head and evaluate if it’s worth the price premium that the RTX 2080 SUPER has. Currently these are the prices they have in stores, choosing the Gigabyte model which is the cheapest in this case in both models.
As you can see, there is a price difference of around 215 euros between these graphics cards (roughly equivalent to a $200 difference in their starting prices according to NVIDIA), so now we have to evaluate if it deserves it? Is it worth paying more for what the RTX 2080 SUPER will give you in return? Let’s look at it in a technical comparison.
Contents [show]
- Technical comparison: RTX 2070 SUPER vs. RTX 2080 SUPER
- How superior is the RTX 2080 SUPER? 9
Release date July 2019 July 2019 Based on the technical specifications, it is clear that the RTX 2080 SUPER3 will give us the best performance in games. Not only is it faster, but it has more shaders, VRAM bandwidth, and more RT and Tensor Cores for ray tracing. There is no doubt about this.
As for the heatsink, both use the same in the case of reference models as well as custom models such as the one we gave Gigabyte as an example. Here the TDP of the graphics is taken into account since 9The 0438 RTX 2070 SUPER has a theoretical power draw 35W less than , so it will use less power, run cooler and therefore the heatsink fans will make less noise.
How superior is the RTX 2080 SUPER?
In terms of relative efficiency, the RTX 2080 SUPER is 13% higher than the RTX 2070 SUPER on average.
According to our own empirical tests (you can check out the RTX 2080 SUPER and RTX 2070 SUPER review on our website), here example in 3DMark Fire Strike Ultra:
12.08% above shown here. Another example, this time in the game (Shadow of the Tomb Raider) in Full HD resolution with maximum graphics.
The performance difference between these RTX 2070 SUPER and RTX 2080 SUPER is 7.56% here and nothing more, but the situation changes when we increase the resolution, increasing to 15% at best.
So which graphics card should you buy?
As we stated at the beginning, the price difference between the two graphics cards is just over 200 euros, and the performance difference averages 13% in favor of the RTX 2080 SUPER. We’re talking about graphics that already belong to the high range, so it’s really not that much of a difference in money to pay.
If we had to choose between these two graphics cards, we think the RTX 2070 is the better option as the performance difference between the two doesn’t justify the price increase of except you’re going to be playing in 4K resolution with everything at a maximum of , it would make more sense to invest in an RTX 2080 SUPER in this case, as we will need every FPS we can compress for that resolution.