1070 ti sli: 50-game GTX 1070 Ti SLI Review : nvidia

Which is better: 2 GTX 1070 SLI or 1 RTX 2070?

Not too long ago, if you wanted to drastically increase your PC’s graphics power, a great way to do so was to add a second graphics card, sharing the load between them using AMD’s Crossfire or Nvidia’s SLI technologies. It was a good way to save money by throwing a second hand card in when a new generation debuted, meaning you could get most of the performance of new-gen cards, with old-gen hardware.

So, surely that applies today too, right? Would a pair of GTX 1070s in SLI be as fast or even faster than a newer RTX 2070? In benchmarks, absolutely. Throw a pair of GTX 1070s at 3DMark Time Spy, and they will easily outstrip an RTX 2070. But in most games, that’s not the case.

SLI and indeed Crossfire, are practically dead technologies at this point. If you want reliable, high-speed gaming, an RTX 2070 is going to offer you better performance than a pair of GTX 1070s in SLI. This is simply because most games offer better support for faster single cards, than they do for a pair of slower cards.

Which is better: 2 GTX 1070 SLI, or 1 RTX 2070? While the 1070s will be faster in some games, for almost everything else, you should pick the RTX 2070.

SLI, a quick history

SLI, or Scalable Link Interface technology, was originally created as the scan-line interleave technology by 3dfx, well before it was bought out by Nvidia. Introduced with its Voodoo2 line of graphics cards in 1998, it allowed two or more GPUs to work side by side on the same graphical problems. This enabled impressive scaling of graphics power, leading to better benchmark and in-game performance.

Nvidia later reintroduced SLI in a different manner in 2004. Cards were paired in a master-slave configuration, where all cards performed the same amount of work, but sent the completed visuals to the master card for transmission to the display. They typically worked by rendering a portion of each frame individually, a technique known as split frame rendering. It later introduced alternate frame rendering, where each GPU renders a subsequent frame entirely by themselves, and SLI antialiasing, where anti-aliasing rendering was specifically split between two GPUs to reduce the overhead it had on system resources.

The Evolution

Over the years the technology evolved to offer better support for a wider array of games and for larger numbers of GPUs, with the highest-end systems managing to run four top-tier graphics cards at once for ridiculous levels of performance. But scalability was always a problem, with even the best implementations not getting close to 100 percent performance scaling with additional GPUs.

Nvidia then slowly began to walk back SLI’s significance. With 10-series GPUs, like the GTX 1070, it introduced a new high-speed SLI bridge, that, while faster, only supported two GPUs at once.

That continued with the RTX 2000-series of Turing graphics cards, where Nvidia again introduced a new bridge known as NVLink, and limited it to just two cards once again.

Making matters worse in 2020, is that game support for SLI with realistically useful scaling, is incredibly limited. There are perhaps tens of games that can truly benefit from it, and even then, bugs and unimpressive scaling continue to plague these titles.

SLI is possible, and if the games you play can benefit from SLI, then it might be worth it. But for more reliable performance, less bugs, and a longer warranty (finding a new 1070 right now is very difficult), you’re better off with the 2070.

But wait… there’s more

You don’t have to buy an RTX 2070. Indeed, if you want improved performance over a single GTX 1070, or RTX 2070-like performance but want to save some money, there are some alternatives.

For starters, the RTX 2070 has largely been replaced by the RTX 2070 Super. Although the former is still available at some retailers at a reasonable price, with dwindled stock, they tend to be overpriced for what you get. The RTX 2070 Super is available around a similar price and with vastly improved performance. In some games it’s more like 15 percent, but in others it can be close to 30 percent quicker. At the same sort of price!

Chillblast no longer ships any custom gaming PCs with RTX 2070s, preferring instead to offer our customers what we consider a better deal in the RTX 2070 Super.

Other options you could try

But if that’s too expensive for you, or you don’t like the value proposition from the RTX 2070 Super, there are other options too. The RTX 2060 Super is much closer in performance to the original RTX 2070, often just a few percent points behind. And yet there are some RTX 2060 Supers that can be bought for under £400, making it a great card for mid-range gaming with even entry-level ray tracing an option, as well as deep learning super sampling. Check out this blog for an insight into games that take advantage of Nvidia’s ray-tracing abilities.

We pack an RTX 2060 Super into one of our most high-value and popular custom gaming PCs, the Chillblast Fusion Super Custom. It combines the high-power Nvidia GPU with an Intel Core i5 9600K, 16GB of fast DDR4 memory and a combination of NVMe SSD and large storage HDD, all packed inside an attractive, tempered glass chassis.

Priced at just £1,300, it’s a fantastic option for anyone looking to upgrade their gaming experience with some serious hardware, without breaking the bank.

Don’t forget AMD

But if you don’t like any of the Nvidia options available as an alternative to SLI GTX 1070s, then there’s always AMD. The RX 5700 XT is an impressively capable card that only falls just behind the RTX 2070 Super (it’s arguably the reason that card exists in the first place) and is significantly cheaper too.

The most affordable 5700 XTs tend to cost just south of £350, though there are some with abysmal cooling solutions, so make sure to check reviews if you’re considering one of them. Around the £400 mark you get a lot more quality of cooling and higher clock speeds for added performance.

There’s also other options further down the performance spectrum. The RX 5700 falls behind a standard RTX 2070, but gives the 2060 Super a good run for its money and can be had for much closer to £300 than any of the other cards we’ve suggested.

Need more help deciding? Give us a call

If you’re still unsure about SLI or single new-generation cards, Nvidia or AMD, you can always give Chillblast a call. We have a team of dedicated hardware experts who not only build the PCs our customers buy, but help design them too. If you’re unsure about what graphics card (or even multiple GPUs if you’re feeling brave) are right for your new gaming system, then we can help.

We’ll walk you through hardware choice based on your particular needs and budget, as well as any options that might improve your gaming performance beyond what even you may have been expecting.

If you like, we can even overclock your new PC for you too, giving you a performance edge entirely for free and completely covered by our five year warranty, so you have complete peace of mind.

More Resources:

For another GPU comparison, check out this blog if you are deciding between a GTX 1080Ti or a 2080!

NVIDIA GeForce GTX 1070 SLI (Desktop) vs NVIDIA GeForce RTX 2080 Mobile vs NVIDIA GeForce GTX 1070 Ti (Desktop)

Performance Rating — 3DMark 11 + Fire Strike + Time Spy — GeForce RTX 2080 Mobile

Die folgenden Benchmarks basieren auf unseren Spieletests mit Testnotebooks. Die Performance dieser Grafikkarte bei den gelisteten Spielen ist abhängig von der verwendeten CPU, Speicherausstattung, Treiber und auch Betriebssystem. Dadurch müssen die untenstehenden Werte nicht repräsentativ sein. Detaillierte Informationen über das verwendete System sehen Sie nach einem Klick auf den fps-Wert.

log 28. 21:49:28

#0 checking url part for id 8092 +0s … 0s

#1 checking url part for id 9541 +0s … 0s

#2 checking url part for id 8258 +0s … 0s

#3 not redirecting to Ajax server +0s … 0s

#4 did not recreate cache, as it is less than 5 days old! Created at Tue, 27 Sep 2022 17:27:11 +0200 +0s … 0s

#5 linkCache_getLink using $NBC_LINKCACHE +0.051s … 0.052s

#6 linkCache_getLink using $NBC_LINKCACHE +0s … 0.052s

#7 linkCache_getLink using $NBC_LINKCACHE +0s … 0.052s

#8 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.052s

#9 linkCache_getLink using $NBC_LINKCACHE +0s … 0.052s

#10 linkCache_getLink using $NBC_LINKCACHE +0s … 0.052s

#11 linkCache_getLink using $NBC_LINKCACHE +0s … 0.052s

#12 linkCache_getLink using $NBC_LINKCACHE +0s … 0.052s

#13 linkCache_getLink using $NBC_LINKCACHE +0s … 0.052s

#14 linkCache_getLink using $NBC_LINKCACHE +0s … 0.052s

#15 linkCache_getLink using $NBC_LINKCACHE +0s … 0.052s

#16 linkCache_getLink using $NBC_LINKCACHE +0s … 0.052s

#17 linkCache_getLink using $NBC_LINKCACHE +0s … 0.052s

#18 linkCache_getLink using $NBC_LINKCACHE +0s … 0.052s

#19 linkCache_getLink using $NBC_LINKCACHE +0s … 0.052s

#20 linkCache_getLink using $NBC_LINKCACHE +0s … 0.052s

#21 linkCache_getLink using $NBC_LINKCACHE +0s … 0.052s

#22 linkCache_getLink using $NBC_LINKCACHE +0s … 0.052s

#23 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.052s

#24 composed specs +0s … 0.052s

#25 did output specs +0s … 0.052s

#26 start showIntegratedCPUs +0s … 0.052s

#27 linkCache_getLink using $NBC_LINKCACHE +0.04s … 0.092s

#28 linkCache_getLink using $NBC_LINKCACHE +0s … 0.092s

#29 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.095s

#30 linkCache_getLink using $NBC_LINKCACHE +0s … 0.095s

#31 linkCache_getLink using $NBC_LINKCACHE +0s … 0.095s

#32 getting avg benchmarks for device 8092 +0s … 0.095s

#33 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.096s

#34 got single benchmarks 8092 +0.006s … 0.101s

#35 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.104s

#36 linkCache_getLink using $NBC_LINKCACHE +0s … 0.105s

#37 linkCache_getLink using $NBC_LINKCACHE +0s … 0.105s

#38 linkCache_getLink using $NBC_LINKCACHE +0. 002s … 0.107s

#39 linkCache_getLink using $NBC_LINKCACHE +0s … 0.107s

#40 linkCache_getLink using $NBC_LINKCACHE +0s … 0.107s

#41 linkCache_getLink using $NBC_LINKCACHE +0s … 0.107s

#42 linkCache_getLink using $NBC_LINKCACHE +0s … 0.107s

#43 linkCache_getLink using $NBC_LINKCACHE +0s … 0.107s

#44 linkCache_getLink using $NBC_LINKCACHE +0s … 0.107s

#45 linkCache_getLink using $NBC_LINKCACHE +0s … 0.107s

#46 linkCache_getLink using $NBC_LINKCACHE +0s … 0.107s

#47 linkCache_getLink using $NBC_LINKCACHE +0s … 0.107s

#48 getting avg benchmarks for device 9541 +0s … 0.107s

#49 got single benchmarks 9541 +0.036s … 0.142s

#50 getting avg benchmarks for device 8258 +0s … 0.143s

#51 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.143s

#52 got single benchmarks 8258 +0.006s … 0.149s

#53 got avg benchmarks for devices +0s . .. 0.149s

#54 linkCache_getLink no uid found +0.001s … 0.15s

#55 linkCache_getLink no uid found +0.001s … 0.151s

#56 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.152s

#57 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s

#58 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s

#59 linkCache_getLink no uid found +0s … 0.152s

#60 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s

#61 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s

#62 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s

#63 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s

#64 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s

#65 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s

#66 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s

#67 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s

#68 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.152s

#69 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s

#70 linkCache_getLink using $NBC_LINKCACHE +0s … 0.152s

#71 linkCache_getLink no uid found +0s … 0.152s

#72 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s

#73 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s

#74 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s

#75 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s

#76 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s

#77 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s

#78 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s

#79 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s

#80 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s

#81 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s

#82 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s

#83 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.155s

#84 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s

#85 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s

#86 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s

#87 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s

#88 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s

#89 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s

#90 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s

#91 linkCache_getLink no uid found +0s … 0.155s

#92 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s

#93 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s

#94 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s

#95 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s

#96 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s

#97 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s

#98 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.156s

#99 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s

#100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s

#101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s

#102 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s

#103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s

#104 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s

#105 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s

#106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s

#107 linkCache_getLink no uid found +0s … 0.156s

#108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s

#109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s

#110 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s

#111 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s

#112 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s

#113 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s

#114 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s

#115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s

#116 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s

#117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s

#118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s

#119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s

#120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s

#121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s

#122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s

#123 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s

#124 linkCache_getLink no uid found +0s … 0.158s

#125 linkCache_getLink no uid found +0s … 0.158s

#126 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s

#127 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.158s

#128 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s

#129 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s

#130 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s

#131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s

#132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s

#133 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s

#134 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s

#135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s

#136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s

#137 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s

#138 linkCache_getLink no uid found +0s … 0.159s

#139 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s

#140 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s

#141 linkCache_getLink using $NBC_LINKCACHE +0s .. . 0.159s

#142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s

#143 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s

#144 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s

#145 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s

#146 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s

#147 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s

#148 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s

#149 linkCache_getLink no uid found +0s … 0.159s

#150 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s

#151 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s

#152 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s

#153 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s

#154 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s

#155 linkCache_getLink no uid found +0s … 0.16s

#156 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.161s

#157 linkCache_getLink using $NBC_LINKCACHE +0s … 0.161s

#158 linkCache_getLink using $NBC_LINKCACHE +0s … 0.161s

#159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.161s

#160 linkCache_getLink using $NBC_LINKCACHE +0s … 0.161s

#161 linkCache_getLink using $NBC_LINKCACHE +0s … 0.161s

#162 linkCache_getLink using $NBC_LINKCACHE +0s … 0.161s

#163 linkCache_getLink no uid found +0s … 0.161s

#164 linkCache_getLink no uid found +0s … 0.161s

#165 linkCache_getLink no uid found +0s … 0.161s

#166 linkCache_getLink no uid found +0s … 0.161s

#167 linkCache_getLink using $NBC_LINKCACHE +0s … 0.161s

#168 linkCache_getLink using $NBC_LINKCACHE +0s … 0.161s

#169 linkCache_getLink using $NBC_LINKCACHE +0s … 0.161s

#170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.161s

#171 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.161s

#172 linkCache_getLink no uid found +0s … 0.161s

#173 linkCache_getLink using $NBC_LINKCACHE +0s … 0.161s

#174 linkCache_getLink no uid found +0s … 0.161s

#175 linkCache_getLink using $NBC_LINKCACHE +0s … 0.161s

#176 linkCache_getLink using $NBC_LINKCACHE +0s … 0.162s

#177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.162s

#178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.163s

#179 linkCache_getLink using $NBC_LINKCACHE +0s … 0.163s

#180 linkCache_getLink using $NBC_LINKCACHE +0s … 0.163s

#181 linkCache_getLink no uid found +0s … 0.163s

#182 linkCache_getLink using $NBC_LINKCACHE +0s … 0.163s

#183 linkCache_getLink using $NBC_LINKCACHE +0s … 0.163s

#184 linkCache_getLink no uid found +0s … 0.163s

#185 linkCache_getLink using $NBC_LINKCACHE +0s … 0.163s

#186 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.163s

#187 linkCache_getLink using $NBC_LINKCACHE +0s … 0.163s

#188 linkCache_getLink using $NBC_LINKCACHE +0s … 0.163s

#189 linkCache_getLink using $NBC_LINKCACHE +0s … 0.163s

#190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.163s

#191 linkCache_getLink using $NBC_LINKCACHE +0s … 0.163s

#192 linkCache_getLink no uid found +0s … 0.163s

#193 linkCache_getLink using $NBC_LINKCACHE +0s … 0.163s

#194 linkCache_getLink no uid found +0s … 0.163s

#195 linkCache_getLink using $NBC_LINKCACHE +0s … 0.163s

#196 linkCache_getLink no uid found +0s … 0.163s

#197 linkCache_getLink no uid found +0.001s … 0.164s

#198 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.165s

#199 linkCache_getLink using $NBC_LINKCACHE +0s … 0.165s

#200 linkCache_getLink using $NBC_LINKCACHE +0s … 0.165s

#201 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.166s

#202 linkCache_getLink using $NBC_LINKCACHE +0s … 0.166s

#203 linkCache_getLink no uid found +0s … 0.166s

#204 linkCache_getLink using $NBC_LINKCACHE +0s … 0.166s

#205 linkCache_getLink using $NBC_LINKCACHE +0s … 0.166s

#206 linkCache_getLink using $NBC_LINKCACHE +0s … 0.167s

#207 linkCache_getLink using $NBC_LINKCACHE +0s … 0.167s

#208 linkCache_getLink using $NBC_LINKCACHE +0s … 0.167s

#209 linkCache_getLink using $NBC_LINKCACHE +0s … 0.168s

#210 linkCache_getLink using $NBC_LINKCACHE +0s … 0.168s

#211 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.169s

#212 linkCache_getLink using $NBC_LINKCACHE +0s … 0.169s

#213 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.169s

#214 linkCache_getLink using $NBC_LINKCACHE +0s … 0.17s

#215 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.17s

#216 linkCache_getLink using $NBC_LINKCACHE +0s … 0.171s

#217 linkCache_getLink using $NBC_LINKCACHE +0s … 0.171s

#218 linkCache_getLink using $NBC_LINKCACHE +0s … 0.171s

#219 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.172s

#220 linkCache_getLink using $NBC_LINKCACHE +0s … 0.172s

#221 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.173s

#222 linkCache_getLink using $NBC_LINKCACHE +0s … 0.173s

#223 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.173s

#224 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s

#225 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s

#226 linkCache_getLink no uid found +0s … 0.174s

#227 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.175s

#228 linkCache_getLink no uid found +0s … 0.175s

#229 linkCache_getLink no uid found +0s . .. 0.175s

#230 linkCache_getLink using $NBC_LINKCACHE +0s … 0.175s

#231 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.176s

#232 linkCache_getLink no uid found +0s … 0.176s

#233 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.176s

#234 linkCache_getLink no uid found +0s … 0.176s

#235 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.177s

#236 linkCache_getLink no uid found +0s … 0.177s

#237 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.177s

#238 linkCache_getLink no uid found +0s … 0.177s

#239 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.178s

#240 linkCache_getLink no uid found +0s … 0.178s

#241 linkCache_getLink no uid found +0.001s … 0.178s

#242 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s

#243 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.179s

#244 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.179s

#245 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s

#246 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s

#247 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.18s

#248 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s

#249 linkCache_getLink no uid found +0s … 0.18s

#250 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s

#251 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s

#252 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.18s

#253 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s

#254 linkCache_getLink no uid found +0s … 0.18s

#255 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s

#256 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s

#257 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s

#258 linkCache_getLink no uid found +0s … 0.18s

#259 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.18s

#260 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s

#261 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s

#262 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s

#263 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s

#264 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.181s

#265 linkCache_getLink no uid found +0s … 0.181s

#266 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s

#267 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s

#268 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s

#269 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s

#270 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s

#271 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s

#272 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s

#273 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s

#274 linkCache_getLink using $NBC_LINKCACHE +0s … 0.181s

#275 linkCache_getLink no uid found +0.001s … 0.182s

#276 linkCache_getLink no uid found +0.001s … 0.182s

#277 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.183s

#278 linkCache_getLink no uid found +0s … 0.183s

#279 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s

#280 linkCache_getLink using $NBC_LINKCACHE +0s … 0.184s

#281 linkCache_getLink no uid found +0s … 0.184s

#282 linkCache_getLink using $NBC_LINKCACHE +0s … 0.185s

#283 linkCache_getLink using $NBC_LINKCACHE +0s … 0.185s

#284 linkCache_getLink no uid found +0s … 0.186s

#285 linkCache_getLink using $NBC_LINKCACHE +0s … 0.186s

#286 linkCache_getLink using $NBC_LINKCACHE +0s … 0.186s

#287 linkCache_getLink using $NBC_LINKCACHE +0s … 0.187s

#288 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.187s

#289 linkCache_getLink using $NBC_LINKCACHE +0s … 0.188s

#290 linkCache_getLink using $NBC_LINKCACHE +0s … 0.188s

#291 linkCache_getLink using $NBC_LINKCACHE +0s … 0.188s

#292 linkCache_getLink using $NBC_LINKCACHE +0s … 0.188s

#293 linkCache_getLink using $NBC_LINKCACHE +0s … 0.188s

#294 linkCache_getLink using $NBC_LINKCACHE +0s … 0.188s

#295 linkCache_getLink using $NBC_LINKCACHE +0s … 0.188s

#296 linkCache_getLink using $NBC_LINKCACHE +0s … 0.188s

#297 linkCache_getLink using $NBC_LINKCACHE +0s … 0.188s

#298 linkCache_getLink using $NBC_LINKCACHE +0s … 0.188s

#299 linkCache_getLink using $NBC_LINKCACHE +0s … 0.188s

#300 linkCache_getLink using $NBC_LINKCACHE +0s … 0.188s

#301 linkCache_getLink using $NBC_LINKCACHE +0s … 0.188s

#302 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.188s

#303 linkCache_getLink using $NBC_LINKCACHE +0s … 0.188s

#304 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.189s

#305 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s

#306 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s

#307 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s

#308 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s

#309 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s

#310 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s

#311 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s

#312 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s

#313 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s

#314 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s

#315 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s

#316 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.189s

#317 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s

#318 linkCache_getLink using $NBC_LINKCACHE +0s … 0.189s

#319 linkCache_getLink using $NBC_LINKCACHE +0s … 0.19s

#320 linkCache_getLink using $NBC_LINKCACHE +0s … 0.19s

#321 linkCache_getLink using $NBC_LINKCACHE +0s … 0.19s

#322 linkCache_getLink using $NBC_LINKCACHE +0s … 0.19s

#323 linkCache_getLink using $NBC_LINKCACHE +0s … 0.19s

#324 linkCache_getLink using $NBC_LINKCACHE +0s … 0.19s

#325 linkCache_getLink using $NBC_LINKCACHE +0s … 0.19s

#326 linkCache_getLink using $NBC_LINKCACHE +0s … 0.19s

#327 linkCache_getLink using $NBC_LINKCACHE +0s … 0.19s

#328 linkCache_getLink using $NBC_LINKCACHE +0s … 0.19s

#329 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.191s

#330 linkCache_getLink using $NBC_LINKCACHE +0.001s . .. 0.191s

#331 min, max, avg, median took s +0s … 0.192s

#332 before gaming benchmark output +0s … 0.192s

#333 Got 992 rows for game benchmarks. +0.065s … 0.256s

#334 composed SQL query for gamebenchmarks +0s … 0.256s

#335 linkCache_getLink using $NBC_LINKCACHE +0s … 0.256s

#336 linkCache_getLink using $NBC_LINKCACHE +0s … 0.256s

#337 linkCache_getLink using $NBC_LINKCACHE +0s … 0.256s

#338 linkCache_getLink using $NBC_LINKCACHE +0s … 0.256s

#339 linkCache_getLink using $NBC_LINKCACHE +0s … 0.256s

#340 linkCache_getLink using $NBC_LINKCACHE +0s … 0.256s

#341 linkCache_getLink using $NBC_LINKCACHE +0s … 0.256s

#342 linkCache_getLink using $NBC_LINKCACHE +0s … 0.256s

#343 linkCache_getLink using $NBC_LINKCACHE +0s … 0.256s

#344 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#345 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.257s

#346 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#347 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#348 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#349 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#350 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#351 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#352 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#353 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#354 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#355 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#356 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#357 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#358 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#359 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.257s

#360 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#361 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#362 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#363 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#364 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#365 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#366 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#367 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#368 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#369 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#370 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#371 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#372 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#373 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.257s

#374 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#375 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#376 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#377 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#378 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#379 linkCache_getLink using $NBC_LINKCACHE +0s … 0.257s

#380 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#381 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#382 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#383 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#384 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#385 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#386 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#387 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.258s

#388 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#389 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#390 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#391 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#392 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#393 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#394 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#395 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#396 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#397 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#398 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#399 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#400 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#401 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.258s

#402 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#403 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#404 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#405 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#406 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#407 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#408 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#409 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#410 linkCache_getLink using $NBC_LINKCACHE +0s … 0.258s

#411 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#412 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#413 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#414 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#415 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.259s

#416 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#417 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#418 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#419 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#420 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#421 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#422 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#423 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#424 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#425 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#426 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#427 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#428 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#429 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.259s

#430 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#431 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#432 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#433 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#434 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#435 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#436 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#437 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#438 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#439 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#440 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#441 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#442 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#443 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.259s

#444 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#445 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#446 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#447 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#448 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#449 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#450 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#451 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#452 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#453 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#454 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#455 linkCache_getLink using $NBC_LINKCACHE +0s … 0.259s

#456 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#457 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.26s

#458 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#459 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#460 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#461 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#462 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#463 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#464 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#465 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#466 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#467 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#468 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#469 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#470 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#471 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#472 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.26s

#473 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#474 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#475 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#476 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#477 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#478 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#479 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#480 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#481 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#482 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#483 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#484 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#485 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#486 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#487 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.26s

#488 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#489 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#490 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#491 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#492 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#493 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#494 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#495 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#496 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#497 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#498 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#499 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#500 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#501 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#502 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.26s

#503 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#504 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#505 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#506 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#507 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#508 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#509 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#510 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#511 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#512 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#513 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#514 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#515 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#516 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#517 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.26s

#518 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#519 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#520 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#521 linkCache_getLink using $NBC_LINKCACHE +0s … 0.26s

#522 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#523 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#524 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#525 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#526 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#527 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#528 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#529 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#530 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#531 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.261s

#532 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#533 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#534 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#535 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#536 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#537 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#538 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#539 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#540 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#541 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#542 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#543 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#544 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#545 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.261s

#546 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#547 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#548 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#549 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#550 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#551 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#552 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#553 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#554 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#555 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#556 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#557 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#558 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#559 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.261s

#560 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#561 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#562 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#563 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#564 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#565 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#566 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#567 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#568 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#569 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#570 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#571 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#572 linkCache_getLink using $NBC_LINKCACHE +0s … 0.261s

#573 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.261s

#574 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#575 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#576 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#577 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#578 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#579 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#580 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#581 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#582 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#583 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#584 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#585 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#586 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#587 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.262s

#588 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#589 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#590 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#591 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#592 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#593 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#594 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#595 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#596 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#597 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#598 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#599 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#600 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#601 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.262s

#602 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#603 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#604 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#605 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#606 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#607 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#608 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#609 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#610 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#611 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#612 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#613 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#614 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#615 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.262s

#616 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#617 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#618 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#619 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#620 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#621 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#622 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#623 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#624 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#625 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#626 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#627 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#628 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#629 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.262s

#630 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#631 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#632 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#633 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#634 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#635 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#636 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#637 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#638 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#639 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#640 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#641 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#642 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#643 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.262s

#644 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#645 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#646 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#647 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#648 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#649 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#650 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#651 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#652 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#653 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#654 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#655 linkCache_getLink using $NBC_LINKCACHE +0s … 0.262s

#656 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#657 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.263s

#658 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#659 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#660 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#661 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#662 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#663 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#664 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#665 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#666 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#667 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#668 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#669 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#670 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#671 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.263s

#672 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#673 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#674 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#675 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#676 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#677 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#678 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#679 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#680 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#681 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#682 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#683 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#684 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#685 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.263s

#686 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#687 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#688 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#689 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#690 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#691 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#692 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#693 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#694 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#695 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#696 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#697 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#698 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#699 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.263s

#700 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#701 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#702 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#703 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#704 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#705 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#706 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#707 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#708 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#709 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#710 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#711 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#712 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#713 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.263s

#714 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#715 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#716 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#717 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#718 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#719 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#720 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#721 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#722 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#723 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#724 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#725 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#726 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#727 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.263s

#728 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#729 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#730 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#731 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#732 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#733 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#734 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#735 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#736 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#737 linkCache_getLink using $NBC_LINKCACHE +0s … 0.263s

#738 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#739 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#740 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#741 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.264s

#742 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#743 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#744 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#745 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#746 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#747 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#748 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#749 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#750 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#751 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#752 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#753 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#754 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#755 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.264s

#756 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#757 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#758 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#759 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#760 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#761 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#762 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#763 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#764 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#765 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#766 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#767 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#768 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#769 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.264s

#770 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#771 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#772 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#773 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#774 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#775 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#776 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#777 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#778 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#779 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#780 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#781 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#782 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#783 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.264s

#784 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#785 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#786 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#787 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#788 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#789 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#790 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#791 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#792 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#793 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#794 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#795 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#796 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#797 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.264s

#798 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#799 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#800 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#801 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#802 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#803 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#804 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#805 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#806 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#807 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#808 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#809 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#810 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#811 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.264s

#812 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#813 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#814 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#815 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#816 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#817 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#818 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#819 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#820 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#821 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#822 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#823 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#824 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#825 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.264s

#826 linkCache_getLink using $NBC_LINKCACHE +0s … 0.264s

#827 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#828 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#829 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#830 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#831 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#832 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#833 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#834 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#835 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#836 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#837 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#838 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#839 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.265s

#840 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#841 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#842 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#843 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#844 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#845 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#846 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#847 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#848 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#849 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#850 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#851 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#852 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#853 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.265s

#854 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#855 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#856 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#857 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#858 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#859 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#860 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#861 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#862 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#863 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#864 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#865 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#866 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#867 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.265s

#868 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#869 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#870 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#871 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#872 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#873 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#874 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#875 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#876 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#877 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#878 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#879 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#880 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#881 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.265s

#882 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#883 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#884 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#885 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#886 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#887 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#888 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#889 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#890 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#891 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#892 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#893 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#894 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#895 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.265s

#896 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#897 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#898 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#899 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#900 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#901 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#902 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#903 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#904 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#905 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#906 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#907 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#908 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#909 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.265s

#910 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#911 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#912 linkCache_getLink using $NBC_LINKCACHE +0s … 0.265s

#913 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#914 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#915 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#916 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#917 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#918 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#919 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#920 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#921 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#922 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#923 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.266s

#924 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#925 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#926 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#927 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#928 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#929 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#930 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#931 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#932 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#933 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#934 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#935 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#936 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#937 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.266s

#938 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#939 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#940 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#941 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#942 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#943 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#944 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#945 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#946 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#947 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#948 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#949 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#950 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#951 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.266s

#952 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#953 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#954 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#955 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#956 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#957 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#958 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#959 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#960 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#961 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#962 linkCache_getLink using $NBC_LINKCACHE +0s … 0.266s

#963 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#964 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#965 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.267s

#966 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#967 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#968 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#969 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#970 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#971 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#972 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#973 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#974 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#975 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#976 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#977 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#978 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#979 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.267s

#980 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#981 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#982 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#983 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#984 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#985 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#986 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#987 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#988 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#989 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#990 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#991 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#992 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#993 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.267s

#994 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#995 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#996 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#997 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#998 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#999 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#1000 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#1001 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#1002 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#1003 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#1004 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#1005 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#1006 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#1007 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.267s

#1008 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#1009 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#1010 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#1011 linkCache_getLink using $NBC_LINKCACHE +0s … 0.267s

#1012 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1013 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1014 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1015 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1016 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1017 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1018 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1019 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1020 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1021 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.268s

#1022 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1023 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1024 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1025 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1026 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1027 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1028 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1029 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1030 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1031 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1032 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1033 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1034 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1035 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.268s

#1036 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1037 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1038 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1039 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1040 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1041 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1042 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1043 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1044 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1045 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1046 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1047 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1048 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1049 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.268s

#1050 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1051 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1052 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1053 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1054 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1055 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1056 linkCache_getLink using $NBC_LINKCACHE +0s … 0.268s

#1057 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1058 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1059 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1060 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1061 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1062 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1063 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.269s

#1064 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1065 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1066 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1067 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1068 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1069 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1070 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1071 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1072 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1073 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1074 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1075 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1076 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1077 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.269s

#1078 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1079 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1080 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1081 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1082 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1083 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1084 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1085 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1086 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1087 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1088 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1089 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1090 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1091 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.269s

#1092 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1093 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1094 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1095 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1096 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1097 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1098 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1099 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1102 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1104 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1105 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.269s

#1106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1107 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1110 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1111 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1112 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1113 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1114 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1116 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1119 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.269s

#1120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1123 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1124 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1125 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1126 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1127 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1128 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1129 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1130 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1133 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.269s

#1134 linkCache_getLink using $NBC_LINKCACHE +0s … 0.269s

#1135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1137 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1138 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1139 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1140 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1141 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1143 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1144 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1145 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1146 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1147 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.27s

#1148 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1149 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1150 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1151 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1152 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1153 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1154 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1155 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1156 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1157 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1158 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1160 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1161 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.27s

#1162 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1163 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1164 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1165 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1166 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1167 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1168 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1169 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1171 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1172 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1173 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1174 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1175 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.27s

#1176 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1179 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1180 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1181 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1182 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1183 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1184 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1185 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1186 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1187 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1188 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1189 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.27s

#1190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1191 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1192 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1193 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1194 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1195 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1196 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1197 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1198 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1199 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1200 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1201 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1202 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1203 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.27s

#1204 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1205 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1206 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1207 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1208 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1209 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1210 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1211 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1212 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1213 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1214 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1215 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1216 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1217 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.27s

#1218 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1219 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1220 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1221 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1222 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1223 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1224 linkCache_getLink using $NBC_LINKCACHE +0s … 0.27s

#1225 got data and put it in $dataArray +0.004s … 0.274s

#1226 linkCache_getLink using $NBC_LINKCACHE +0.063s … 0.338s

#1227 linkCache_getLink using $NBC_LINKCACHE +0s … 0.338s

#1228 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.338s

#1229 linkCache_getLink using $NBC_LINKCACHE +0s … 0.338s

#1230 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.339s

#1231 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.339s

#1232 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.34s

#1233 linkCache_getLink using $NBC_LINKCACHE +0s … 0.34s

#1234 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.341s

#1235 linkCache_getLink using $NBC_LINKCACHE +0s … 0.341s

#1236 linkCache_getLink using $NBC_LINKCACHE +0s … 0.341s

#1237 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.341s

#1238 linkCache_getLink using $NBC_LINKCACHE +0s … 0.341s

#1239 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.342s

#1240 linkCache_getLink using $NBC_LINKCACHE +0s … 0.342s

#1241 linkCache_getLink using $NBC_LINKCACHE +0s … 0.342s

#1242 linkCache_getLink using $NBC_LINKCACHE +0s … 0.342s

#1243 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.343s

#1244 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s

#1245 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.343s

#1246 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s

#1247 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s

#1248 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s

#1249 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s

#1250 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s

#1251 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s

#1252 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s

#1253 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.343s

#1254 linkCache_getLink using $NBC_LINKCACHE +0s … 0.343s

#1255 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.344s

#1256 linkCache_getLink using $NBC_LINKCACHE +0s … 0.344s

#1257 linkCache_getLink using $NBC_LINKCACHE +0s … 0.344s

#1258 linkCache_getLink using $NBC_LINKCACHE +0s … 0.344s

#1259 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.344s

#1260 linkCache_getLink using $NBC_LINKCACHE +0s … 0.344s

#1261 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.347s

#1262 linkCache_getLink using $NBC_LINKCACHE +0s … 0.347s

#1263 linkCache_getLink using $NBC_LINKCACHE +0s … 0.347s

#1264 linkCache_getLink using $NBC_LINKCACHE +0s … 0.347s

#1265 linkCache_getLink using $NBC_LINKCACHE +0s … 0.347s

#1266 linkCache_getLink using $NBC_LINKCACHE +0s … 0.347s

#1267 linkCache_getLink using $NBC_LINKCACHE +0s … 0.347s

#1268 linkCache_getLink using $NBC_LINKCACHE +0s … 0.347s

#1269 linkCache_getLink using $NBC_LINKCACHE +0s … 0.347s

#1270 linkCache_getLink using $NBC_LINKCACHE +0s … 0.347s

#1271 linkCache_getLink using $NBC_LINKCACHE +0s … 0.347s

#1272 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.347s

#1273 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.347s

#1274 linkCache_getLink using $NBC_LINKCACHE +0s … 0.347s

#1275 linkCache_getLink using $NBC_LINKCACHE +0s … 0.347s

#1276 linkCache_getLink using $NBC_LINKCACHE +0s … 0.347s

#1277 linkCache_getLink using $NBC_LINKCACHE +0s … 0.348s

#1278 linkCache_getLink using $NBC_LINKCACHE +0s … 0.348s

#1279 linkCache_getLink using $NBC_LINKCACHE +0s … 0.348s

#1280 linkCache_getLink using $NBC_LINKCACHE +0s … 0.348s

#1281 linkCache_getLink using $NBC_LINKCACHE +0s … 0.348s

#1282 linkCache_getLink using $NBC_LINKCACHE +0s … 0.348s

#1283 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.348s

#1284 linkCache_getLink using $NBC_LINKCACHE +0s … 0.348s

#1285 linkCache_getLink using $NBC_LINKCACHE +0s … 0.348s

#1286 linkCache_getLink using $NBC_LINKCACHE +0s … 0.348s

#1287 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.348s

#1288 linkCache_getLink using $NBC_LINKCACHE +0s … 0.348s

#1289 linkCache_getLink using $NBC_LINKCACHE +0s … 0.348s

#1290 linkCache_getLink using $NBC_LINKCACHE +0s … 0.348s

#1291 linkCache_getLink using $NBC_LINKCACHE +0s … 0.348s

#1292 linkCache_getLink using $NBC_LINKCACHE +0s … 0.348s

#1293 linkCache_getLink using $NBC_LINKCACHE +0s … 0.348s

#1294 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.349s

#1295 linkCache_getLink using $NBC_LINKCACHE +0s … 0.349s

#1296 linkCache_getLink using $NBC_LINKCACHE +0s … 0.349s

#1297 linkCache_getLink using $NBC_LINKCACHE +0s … 0.349s

#1298 linkCache_getLink using $NBC_LINKCACHE +0s … 0.349s

#1299 linkCache_getLink using $NBC_LINKCACHE +0s … 0.349s

#1300 linkCache_getLink using $NBC_LINKCACHE +0s … 0.349s

#1301 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.349s

#1302 linkCache_getLink using $NBC_LINKCACHE +0s … 0.349s

#1303 linkCache_getLink using $NBC_LINKCACHE +0s … 0.349s

#1304 linkCache_getLink using $NBC_LINKCACHE +0s … 0.349s

#1305 linkCache_getLink using $NBC_LINKCACHE +0s … 0.349s

#1306 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.35s

#1307 linkCache_getLink using $NBC_LINKCACHE +0s … 0.35s

#1308 linkCache_getLink using $NBC_LINKCACHE +0s … 0.35s

#1309 linkCache_getLink using $NBC_LINKCACHE +0s … 0.35s

#1310 linkCache_getLink using $NBC_LINKCACHE +0s … 0.35s

#1311 linkCache_getLink using $NBC_LINKCACHE +0s … 0.35s

#1312 linkCache_getLink using $NBC_LINKCACHE +0s … 0.35s

#1313 linkCache_getLink using $NBC_LINKCACHE +0s … 0.35s

#1314 linkCache_getLink using $NBC_LINKCACHE +0s … 0.35s

#1315 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.35s

#1316 linkCache_getLink using $NBC_LINKCACHE +0s … 0.35s

#1317 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.351s

#1318 linkCache_getLink using $NBC_LINKCACHE +0s … 0.351s

#1319 linkCache_getLink using $NBC_LINKCACHE +0s … 0.351s

#1320 linkCache_getLink using $NBC_LINKCACHE +0s … 0.351s

#1321 linkCache_getLink using $NBC_LINKCACHE +0s … 0.351s

#1322 linkCache_getLink using $NBC_LINKCACHE +0s … 0.351s

#1323 linkCache_getLink using $NBC_LINKCACHE +0s … 0.351s

#1324 linkCache_getLink using $NBC_LINKCACHE +0s … 0.351s

#1325 linkCache_getLink using $NBC_LINKCACHE +0s … 0.351s

#1326 linkCache_getLink using $NBC_LINKCACHE +0s … 0.351s

#1327 linkCache_getLink using $NBC_LINKCACHE +0s … 0.352s

#1328 linkCache_getLink using $NBC_LINKCACHE +0s … 0.352s

#1329 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.352s

#1330 linkCache_getLink using $NBC_LINKCACHE +0s … 0.352s

#1331 linkCache_getLink using $NBC_LINKCACHE +0s … 0.352s

#1332 linkCache_getLink using $NBC_LINKCACHE +0s … 0.352s

#1333 linkCache_getLink using $NBC_LINKCACHE +0s … 0.352s

#1334 linkCache_getLink using $NBC_LINKCACHE +0s … 0.352s

#1335 linkCache_getLink using $NBC_LINKCACHE +0s … 0.352s

#1336 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.353s

#1337 linkCache_getLink using $NBC_LINKCACHE +0s … 0.353s

#1338 linkCache_getLink using $NBC_LINKCACHE +0s … 0.353s

#1339 linkCache_getLink using $NBC_LINKCACHE +0s … 0.353s

#1340 linkCache_getLink using $NBC_LINKCACHE +0s … 0.353s

#1341 linkCache_getLink using $NBC_LINKCACHE +0s … 0.353s

#1342 linkCache_getLink using $NBC_LINKCACHE +0s … 0.353s

#1343 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.353s

#1344 linkCache_getLink using $NBC_LINKCACHE +0s … 0.353s

#1345 linkCache_getLink using $NBC_LINKCACHE +0s … 0.353s

#1346 linkCache_getLink using $NBC_LINKCACHE +0s … 0.353s

#1347 linkCache_getLink using $NBC_LINKCACHE +0s … 0.353s

#1348 linkCache_getLink using $NBC_LINKCACHE +0s … 0.353s

#1349 linkCache_getLink using $NBC_LINKCACHE +0s … 0.353s

#1350 linkCache_getLink using $NBC_LINKCACHE +0s … 0.353s

#1351 linkCache_getLink using $NBC_LINKCACHE +0s … 0.353s

#1352 linkCache_getLink using $NBC_LINKCACHE +0s … 0.353s

#1353 linkCache_getLink using $NBC_LINKCACHE +0s … 0.353s

#1354 linkCache_getLink using $NBC_LINKCACHE +0s … 0.353s

#1355 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.354s

#1356 linkCache_getLink using $NBC_LINKCACHE +0s … 0.354s

#1357 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.354s

#1358 linkCache_getLink using $NBC_LINKCACHE +0s … 0.354s

#1359 linkCache_getLink using $NBC_LINKCACHE +0s … 0.354s

#1360 linkCache_getLink using $NBC_LINKCACHE +0s … 0.354s

#1361 linkCache_getLink using $NBC_LINKCACHE +0s … 0.354s

#1362 linkCache_getLink using $NBC_LINKCACHE +0s … 0.354s

#1363 linkCache_getLink using $NBC_LINKCACHE +0s … 0.354s

#1364 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.355s

#1365 linkCache_getLink using $NBC_LINKCACHE +0s … 0.355s

#1366 linkCache_getLink using $NBC_LINKCACHE +0s … 0.355s

#1367 linkCache_getLink using $NBC_LINKCACHE +0s … 0.355s

#1368 linkCache_getLink using $NBC_LINKCACHE +0s … 0.355s

#1369 linkCache_getLink using $NBC_LINKCACHE +0s … 0.355s

#1370 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.356s

#1371 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.356s

#1372 linkCache_getLink using $NBC_LINKCACHE +0s … 0.356s

#1373 linkCache_getLink using $NBC_LINKCACHE +0s … 0.356s

#1374 linkCache_getLink using $NBC_LINKCACHE +0s … 0.356s

#1375 linkCache_getLink using $NBC_LINKCACHE +0s … 0.356s

#1376 linkCache_getLink using $NBC_LINKCACHE +0s … 0.356s

#1377 linkCache_getLink using $NBC_LINKCACHE +0s … 0.356s

#1378 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.356s

#1379 linkCache_getLink using $NBC_LINKCACHE +0s … 0.356s

#1380 linkCache_getLink using $NBC_LINKCACHE +0s … 0.356s

#1381 linkCache_getLink using $NBC_LINKCACHE +0s … 0.356s

#1382 linkCache_getLink using $NBC_LINKCACHE +0s … 0.356s

#1383 linkCache_getLink using $NBC_LINKCACHE +0s … 0.356s

#1384 linkCache_getLink using $NBC_LINKCACHE +0s … 0.356s

#1385 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.356s

#1386 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.357s

#1387 linkCache_getLink using $NBC_LINKCACHE +0s … 0.357s

#1388 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.358s

#1389 linkCache_getLink using $NBC_LINKCACHE +0s … 0.358s

#1390 linkCache_getLink using $NBC_LINKCACHE +0s … 0.358s

#1391 linkCache_getLink using $NBC_LINKCACHE +0s … 0.358s

#1392 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.358s

#1393 linkCache_getLink using $NBC_LINKCACHE +0s … 0.358s

#1394 linkCache_getLink using $NBC_LINKCACHE +0s … 0.358s

#1395 linkCache_getLink using $NBC_LINKCACHE +0s … 0.359s

#1396 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.359s

#1397 linkCache_getLink using $NBC_LINKCACHE +0s … 0.359s

#1398 linkCache_getLink using $NBC_LINKCACHE +0s … 0.359s

#1399 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.359s

#1400 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.36s

#1401 linkCache_getLink using $NBC_LINKCACHE +0s … 0.36s

#1402 linkCache_getLink using $NBC_LINKCACHE +0s … 0.36s

#1403 linkCache_getLink using $NBC_LINKCACHE +0s … 0.36s

#1404 linkCache_getLink using $NBC_LINKCACHE +0s … 0.36s

#1405 linkCache_getLink using $NBC_LINKCACHE +0s … 0.36s

#1406 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.361s

#1407 linkCache_getLink using $NBC_LINKCACHE +0s … 0.361s

#1408 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.361s

#1409 linkCache_getLink using $NBC_LINKCACHE +0s … 0.361s

#1410 linkCache_getLink using $NBC_LINKCACHE +0s … 0.361s

#1411 linkCache_getLink using $NBC_LINKCACHE +0s … 0.361s

#1412 linkCache_getLink using $NBC_LINKCACHE +0s … 0.361s

#1413 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.361s

#1414 linkCache_getLink using $NBC_LINKCACHE +0s … 0.361s

#1415 linkCache_getLink using $NBC_LINKCACHE +0s … 0.361s

#1416 linkCache_getLink using $NBC_LINKCACHE +0s … 0.361s

#1417 linkCache_getLink using $NBC_LINKCACHE +0s … 0.361s

#1418 linkCache_getLink using $NBC_LINKCACHE +0s … 0.361s

#1419 linkCache_getLink using $NBC_LINKCACHE +0s … 0.361s

#1420 linkCache_getLink using $NBC_LINKCACHE +0s … 0.361s

#1421 linkCache_getLink using $NBC_LINKCACHE +0s … 0.362s

#1422 linkCache_getLink using $NBC_LINKCACHE +0s … 0.362s

#1423 linkCache_getLink using $NBC_LINKCACHE +0s … 0.362s

#1424 linkCache_getLink using $NBC_LINKCACHE +0s … 0.362s

#1425 linkCache_getLink using $NBC_LINKCACHE +0s … 0.362s

#1426 linkCache_getLink using $NBC_LINKCACHE +0s … 0.362s

#1427 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.362s

#1428 linkCache_getLink using $NBC_LINKCACHE +0s … 0.362s

#1429 linkCache_getLink using $NBC_LINKCACHE +0s … 0.362s

#1430 linkCache_getLink using $NBC_LINKCACHE +0s … 0.362s

#1431 linkCache_getLink using $NBC_LINKCACHE +0s … 0.362s

#1432 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.363s

#1433 linkCache_getLink using $NBC_LINKCACHE +0s … 0.363s

#1434 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.364s

#1435 linkCache_getLink using $NBC_LINKCACHE +0s … 0.364s

#1436 linkCache_getLink using $NBC_LINKCACHE +0s … 0.365s

#1437 linkCache_getLink using $NBC_LINKCACHE +0s … 0.365s

#1438 linkCache_getLink using $NBC_LINKCACHE +0s … 0.365s

#1439 linkCache_getLink using $NBC_LINKCACHE +0s … 0.365s

#1440 linkCache_getLink using $NBC_LINKCACHE +0s … 0.365s

#1441 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.365s

#1442 linkCache_getLink using $NBC_LINKCACHE +0s … 0.365s

#1443 linkCache_getLink using $NBC_LINKCACHE +0s … 0.365s

#1444 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.366s

#1445 linkCache_getLink using $NBC_LINKCACHE +0s … 0.366s

#1446 linkCache_getLink using $NBC_LINKCACHE +0s … 0.366s

#1447 linkCache_getLink using $NBC_LINKCACHE +0s … 0.366s

#1448 linkCache_getLink using $NBC_LINKCACHE +0s … 0.366s

#1449 linkCache_getLink using $NBC_LINKCACHE +0s … 0.366s

#1450 linkCache_getLink using $NBC_LINKCACHE +0s … 0.366s

#1451 linkCache_getLink using $NBC_LINKCACHE +0s … 0.366s

#1452 linkCache_getLink using $NBC_LINKCACHE +0s … 0.366s

#1453 linkCache_getLink using $NBC_LINKCACHE +0s … 0.366s

#1454 linkCache_getLink using $NBC_LINKCACHE +0s … 0.366s

#1455 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.366s

#1456 linkCache_getLink using $NBC_LINKCACHE +0s … 0.366s

#1457 linkCache_getLink using $NBC_LINKCACHE +0s … 0.366s

#1458 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.367s

#1459 linkCache_getLink using $NBC_LINKCACHE +0s … 0.367s

#1460 linkCache_getLink using $NBC_LINKCACHE +0s … 0.367s

#1461 linkCache_getLink using $NBC_LINKCACHE +0s … 0.367s

#1462 linkCache_getLink using $NBC_LINKCACHE +0s … 0.367s

#1463 linkCache_getLink using $NBC_LINKCACHE +0s … 0.367s

#1464 linkCache_getLink using $NBC_LINKCACHE +0s … 0.367s

#1465 linkCache_getLink using $NBC_LINKCACHE +0s … 0.367s

#1466 linkCache_getLink using $NBC_LINKCACHE +0s … 0.367s

#1467 linkCache_getLink using $NBC_LINKCACHE +0s … 0.367s

#1468 linkCache_getLink using $NBC_LINKCACHE +0s … 0.367s

#1469 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.367s

#1470 linkCache_getLink using $NBC_LINKCACHE +0s … 0.367s

#1471 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.368s

#1472 linkCache_getLink using $NBC_LINKCACHE +0s … 0.368s

#1473 linkCache_getLink using $NBC_LINKCACHE +0s … 0.368s

#1474 linkCache_getLink using $NBC_LINKCACHE +0s … 0.368s

#1475 linkCache_getLink using $NBC_LINKCACHE +0s … 0.368s

#1476 linkCache_getLink using $NBC_LINKCACHE +0s … 0.368s

#1477 linkCache_getLink using $NBC_LINKCACHE +0s … 0.368s

#1478 linkCache_getLink using $NBC_LINKCACHE +0s … 0.368s

#1479 linkCache_getLink using $NBC_LINKCACHE +0s … 0.368s

#1480 linkCache_getLink using $NBC_LINKCACHE +0s … 0.368s

#1481 linkCache_getLink using $NBC_LINKCACHE +0s … 0.368s

#1482 linkCache_getLink using $NBC_LINKCACHE +0s … 0.368s

#1483 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.368s

#1484 linkCache_getLink using $NBC_LINKCACHE +0s … 0.368s

#1485 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.368s

#1486 linkCache_getLink using $NBC_LINKCACHE +0s … 0.368s

#1487 linkCache_getLink using $NBC_LINKCACHE +0s … 0.368s

#1488 linkCache_getLink using $NBC_LINKCACHE +0s … 0.368s

#1489 linkCache_getLink using $NBC_LINKCACHE +0s … 0.369s

#1490 linkCache_getLink using $NBC_LINKCACHE +0s … 0.369s

#1491 linkCache_getLink using $NBC_LINKCACHE +0s … 0.369s

#1492 linkCache_getLink using $NBC_LINKCACHE +0s … 0.369s

#1493 linkCache_getLink using $NBC_LINKCACHE +0s … 0.369s

#1494 linkCache_getLink using $NBC_LINKCACHE +0s … 0.369s

#1495 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.369s

#1496 linkCache_getLink using $NBC_LINKCACHE +0s … 0.369s

#1497 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.369s

#1498 linkCache_getLink using $NBC_LINKCACHE +0s … 0.369s

#1499 linkCache_getLink using $NBC_LINKCACHE +0s … 0.369s

#1500 linkCache_getLink using $NBC_LINKCACHE +0s … 0.369s

#1501 linkCache_getLink using $NBC_LINKCACHE +0s … 0.369s

#1502 linkCache_getLink using $NBC_LINKCACHE +0s … 0.369s

#1503 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.37s

#1504 linkCache_getLink using $NBC_LINKCACHE +0s … 0.37s

#1505 linkCache_getLink using $NBC_LINKCACHE +0s … 0.37s

#1506 linkCache_getLink using $NBC_LINKCACHE +0s … 0.37s

#1507 linkCache_getLink using $NBC_LINKCACHE +0s … 0.37s

#1508 linkCache_getLink using $NBC_LINKCACHE +0s … 0.37s

#1509 linkCache_getLink using $NBC_LINKCACHE +0s … 0.37s

#1510 linkCache_getLink using $NBC_LINKCACHE +0s … 0.37s

#1511 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.371s

#1512 linkCache_getLink using $NBC_LINKCACHE +0s … 0.371s

#1513 linkCache_getLink using $NBC_LINKCACHE +0s … 0.371s

#1514 linkCache_getLink using $NBC_LINKCACHE +0s … 0.371s

#1515 linkCache_getLink using $NBC_LINKCACHE +0s … 0.371s

#1516 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.372s

#1517 linkCache_getLink using $NBC_LINKCACHE +0s … 0.372s

#1518 linkCache_getLink using $NBC_LINKCACHE +0s … 0.372s

#1519 linkCache_getLink using $NBC_LINKCACHE +0s … 0.372s

#1520 linkCache_getLink using $NBC_LINKCACHE +0s … 0.372s

#1521 linkCache_getLink using $NBC_LINKCACHE +0s … 0.372s

#1522 linkCache_getLink using $NBC_LINKCACHE +0s … 0.372s

#1523 linkCache_getLink using $NBC_LINKCACHE +0s … 0.372s

#1524 linkCache_getLink using $NBC_LINKCACHE +0s … 0.372s

#1525 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.372s

#1526 linkCache_getLink using $NBC_LINKCACHE +0s … 0.372s

#1527 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.372s

#1528 linkCache_getLink using $NBC_LINKCACHE +0s … 0.372s

#1529 linkCache_getLink using $NBC_LINKCACHE +0s … 0.372s

#1530 linkCache_getLink using $NBC_LINKCACHE +0s … 0.372s

#1531 linkCache_getLink using $NBC_LINKCACHE +0s … 0.372s

#1532 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.373s

#1533 linkCache_getLink using $NBC_LINKCACHE +0s … 0.373s

#1534 linkCache_getLink using $NBC_LINKCACHE +0s … 0.373s

#1535 linkCache_getLink using $NBC_LINKCACHE +0s … 0.373s

#1536 linkCache_getLink using $NBC_LINKCACHE +0s … 0.373s

#1537 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.374s

#1538 linkCache_getLink using $NBC_LINKCACHE +0s … 0.374s

#1539 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.374s

#1540 linkCache_getLink using $NBC_LINKCACHE +0s … 0.374s

#1541 linkCache_getLink using $NBC_LINKCACHE +0s … 0.374s

#1542 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.374s

#1543 linkCache_getLink using $NBC_LINKCACHE +0s … 0.374s

#1544 linkCache_getLink using $NBC_LINKCACHE +0s … 0.375s

#1545 linkCache_getLink using $NBC_LINKCACHE +0s … 0.375s

#1546 linkCache_getLink using $NBC_LINKCACHE +0s … 0.375s

#1547 linkCache_getLink using $NBC_LINKCACHE +0s … 0.375s

#1548 linkCache_getLink using $NBC_LINKCACHE +0s … 0.375s

#1549 linkCache_getLink using $NBC_LINKCACHE +0s … 0.375s

#1550 linkCache_getLink using $NBC_LINKCACHE +0s … 0.375s

#1551 linkCache_getLink using $NBC_LINKCACHE +0s … 0.375s

#1552 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.375s

#1553 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.375s

#1554 linkCache_getLink using $NBC_LINKCACHE +0s … 0.375s

#1555 linkCache_getLink using $NBC_LINKCACHE +0s … 0.375s

#1556 linkCache_getLink using $NBC_LINKCACHE +0s … 0.375s

#1557 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.376s

#1558 linkCache_getLink using $NBC_LINKCACHE +0s … 0.376s

#1559 linkCache_getLink using $NBC_LINKCACHE +0s … 0.376s

#1560 linkCache_getLink using $NBC_LINKCACHE +0s … 0.376s

#1561 linkCache_getLink using $NBC_LINKCACHE +0s … 0.376s

#1562 linkCache_getLink using $NBC_LINKCACHE +0s … 0.376s

#1563 linkCache_getLink using $NBC_LINKCACHE +0s … 0.376s

#1564 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.377s

#1565 linkCache_getLink using $NBC_LINKCACHE +0s … 0.377s

#1566 linkCache_getLink using $NBC_LINKCACHE +0s … 0.377s

#1567 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.377s

#1568 linkCache_getLink using $NBC_LINKCACHE +0s … 0.377s

#1569 linkCache_getLink using $NBC_LINKCACHE +0s … 0.377s

#1570 linkCache_getLink using $NBC_LINKCACHE +0s … 0.377s

#1571 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.378s

#1572 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.379s

#1573 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.379s

#1574 linkCache_getLink using $NBC_LINKCACHE +0s … 0.379s

#1575 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.381s

#1576 linkCache_getLink using $NBC_LINKCACHE +0s … 0.381s

#1577 linkCache_getLink using $NBC_LINKCACHE +0s … 0.381s

#1578 linkCache_getLink using $NBC_LINKCACHE +0s … 0.381s

#1579 linkCache_getLink using $NBC_LINKCACHE +0s … 0.381s

#1580 linkCache_getLink using $NBC_LINKCACHE +0s … 0.381s

#1581 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.381s

#1582 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.381s

#1583 linkCache_getLink using $NBC_LINKCACHE +0s … 0.381s

#1584 linkCache_getLink using $NBC_LINKCACHE +0s … 0.381s

#1585 linkCache_getLink using $NBC_LINKCACHE +0s … 0.381s

#1586 linkCache_getLink using $NBC_LINKCACHE +0s … 0.381s

#1587 linkCache_getLink using $NBC_LINKCACHE +0s … 0.381s

#1588 linkCache_getLink using $NBC_LINKCACHE +0s … 0.381s

#1589 linkCache_getLink using $NBC_LINKCACHE +0s … 0.382s

#1590 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.382s

#1591 linkCache_getLink using $NBC_LINKCACHE +0s … 0.382s

#1592 linkCache_getLink using $NBC_LINKCACHE +0s … 0.382s

#1593 linkCache_getLink using $NBC_LINKCACHE +0s … 0.382s

#1594 linkCache_getLink using $NBC_LINKCACHE +0s … 0.382s

#1595 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.383s

#1596 linkCache_getLink using $NBC_LINKCACHE +0s … 0.383s

#1597 linkCache_getLink using $NBC_LINKCACHE +0s … 0.383s

#1598 linkCache_getLink using $NBC_LINKCACHE +0s … 0.383s

#1599 linkCache_getLink using $NBC_LINKCACHE +0s … 0.383s

#1600 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.384s

#1601 linkCache_getLink using $NBC_LINKCACHE +0s … 0.384s

#1602 linkCache_getLink using $NBC_LINKCACHE +0s … 0.384s

#1603 linkCache_getLink using $NBC_LINKCACHE +0s … 0.384s

#1604 linkCache_getLink using $NBC_LINKCACHE +0s … 0.384s

#1605 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.384s

#1606 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.385s

#1607 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.385s

#1608 linkCache_getLink using $NBC_LINKCACHE +0s … 0.385s

#1609 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.385s

#1610 linkCache_getLink using $NBC_LINKCACHE +0s … 0.385s

#1611 linkCache_getLink using $NBC_LINKCACHE +0s … 0.386s

#1612 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.386s

#1613 linkCache_getLink using $NBC_LINKCACHE +0s … 0.386s

#1614 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.387s

#1615 linkCache_getLink using $NBC_LINKCACHE +0s … 0.387s

#1616 linkCache_getLink using $NBC_LINKCACHE +0s … 0.387s

#1617 linkCache_getLink using $NBC_LINKCACHE +0s … 0.387s

#1618 linkCache_getLink using $NBC_LINKCACHE +0s … 0.387s

#1619 linkCache_getLink using $NBC_LINKCACHE +0s … 0.387s

#1620 linkCache_getLink using $NBC_LINKCACHE +0s … 0.387s

#1621 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.388s

#1622 linkCache_getLink using $NBC_LINKCACHE +0s … 0.388s

#1623 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.389s

#1624 linkCache_getLink using $NBC_LINKCACHE +0s … 0.389s

#1625 linkCache_getLink using $NBC_LINKCACHE +0s … 0.389s

#1626 linkCache_getLink using $NBC_LINKCACHE +0s … 0.389s

#1627 linkCache_getLink using $NBC_LINKCACHE +0s … 0.389s

#1628 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.389s

#1629 linkCache_getLink using $NBC_LINKCACHE +0s … 0.389s

#1630 linkCache_getLink using $NBC_LINKCACHE +0s … 0.389s

#1631 linkCache_getLink using $NBC_LINKCACHE +0s … 0.389s

#1632 linkCache_getLink using $NBC_LINKCACHE +0s … 0.39s

#1633 linkCache_getLink using $NBC_LINKCACHE +0s … 0.39s

#1634 linkCache_getLink using $NBC_LINKCACHE +0s … 0.39s

#1635 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.39s

#1636 linkCache_getLink using $NBC_LINKCACHE +0s … 0.39s

#1637 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.39s

#1638 linkCache_getLink using $NBC_LINKCACHE +0s … 0.39s

#1639 linkCache_getLink using $NBC_LINKCACHE +0s … 0.39s

#1640 linkCache_getLink using $NBC_LINKCACHE +0s … 0.39s

#1641 linkCache_getLink using $NBC_LINKCACHE +0s … 0.39s

#1642 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.391s

#1643 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1644 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1645 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1646 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1647 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1648 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1649 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1650 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1651 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.391s

#1652 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1653 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1654 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1655 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1656 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1657 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1658 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1659 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1660 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1661 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1662 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1663 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1664 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1665 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.391s

#1666 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1667 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1668 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1669 linkCache_getLink using $NBC_LINKCACHE +0s … 0.391s

#1670 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.392s

#1671 linkCache_getLink using $NBC_LINKCACHE +0s … 0.392s

#1672 linkCache_getLink using $NBC_LINKCACHE +0s … 0.392s

#1673 linkCache_getLink using $NBC_LINKCACHE +0s … 0.392s

#1674 linkCache_getLink using $NBC_LINKCACHE +0s … 0.392s

#1675 linkCache_getLink using $NBC_LINKCACHE +0s … 0.392s

#1676 linkCache_getLink using $NBC_LINKCACHE +0s … 0.392s

#1677 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.393s

#1678 linkCache_getLink using $NBC_LINKCACHE +0s … 0.393s

#1679 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.393s

#1680 linkCache_getLink using $NBC_LINKCACHE +0s … 0.393s

#1681 linkCache_getLink using $NBC_LINKCACHE +0s … 0.393s

#1682 linkCache_getLink using $NBC_LINKCACHE +0s … 0.393s

#1683 linkCache_getLink using $NBC_LINKCACHE +0s … 0.393s

#1684 linkCache_getLink using $NBC_LINKCACHE +0s … 0.393s

#1685 linkCache_getLink using $NBC_LINKCACHE +0s … 0.393s

#1686 linkCache_getLink using $NBC_LINKCACHE +0s … 0.393s

#1687 linkCache_getLink using $NBC_LINKCACHE +0s … 0.393s

#1688 linkCache_getLink using $NBC_LINKCACHE +0s … 0.393s

#1689 linkCache_getLink using $NBC_LINKCACHE +0s … 0.393s

#1690 linkCache_getLink using $NBC_LINKCACHE +0s … 0.393s

#1691 linkCache_getLink using $NBC_LINKCACHE +0s … 0.393s

#1692 linkCache_getLink using $NBC_LINKCACHE +0s … 0.393s

#1693 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.393s

#1694 linkCache_getLink using $NBC_LINKCACHE +0s … 0.393s

#1695 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.394s

#1696 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1697 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1698 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1699 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1700 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1701 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1702 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1703 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1704 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1705 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1706 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1707 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.394s

#1708 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1709 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1710 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1711 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1712 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1713 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1714 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1715 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1716 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1717 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1718 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1719 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1720 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1721 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.394s

#1722 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1723 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1724 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1725 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1726 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1727 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1728 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1729 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1730 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1731 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1732 linkCache_getLink using $NBC_LINKCACHE +0s … 0.394s

#1733 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.397s

#1734 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.399s

#1735 linkCache_getLink using $NBC_LINKCACHE +0. 002s … 0.401s

#1736 linkCache_getLink using $NBC_LINKCACHE +0.004s … 0.405s

#1737 linkCache_getLink using $NBC_LINKCACHE +0.004s … 0.408s

#1738 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.41s

#1739 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.413s

#1740 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.416s

#1741 linkCache_getLink using $NBC_LINKCACHE +0s … 0.416s

#1742 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.419s

#1743 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.421s

#1744 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.424s

#1745 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.428s

#1746 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.429s

#1747 linkCache_getLink using $NBC_LINKCACHE +0.005s … 0.434s

#1748 linkCache_getLink using $NBC_LINKCACHE +0s … 0. 434s

#1749 linkCache_getLink using $NBC_LINKCACHE +0s … 0.434s

#1750 linkCache_getLink using $NBC_LINKCACHE +0s … 0.434s

#1751 linkCache_getLink using $NBC_LINKCACHE +0s … 0.434s

#1752 linkCache_getLink using $NBC_LINKCACHE +0s … 0.434s

#1753 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.435s

#1754 linkCache_getLink using $NBC_LINKCACHE +0s … 0.435s

#1755 linkCache_getLink using $NBC_LINKCACHE +0s … 0.435s

#1756 linkCache_getLink using $NBC_LINKCACHE +0s … 0.435s

#1757 linkCache_getLink using $NBC_LINKCACHE +0s … 0.435s

#1758 linkCache_getLink using $NBC_LINKCACHE +0s … 0.435s

#1759 linkCache_getLink using $NBC_LINKCACHE +0s … 0.435s

#1760 linkCache_getLink using $NBC_LINKCACHE +0s … 0.435s

#1761 linkCache_getLink using $NBC_LINKCACHE +0s … 0.435s

#1762 linkCache_getLink using $NBC_LINKCACHE +0. 001s … 0.436s

#1763 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1764 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1765 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1766 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1767 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1768 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1769 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1770 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1771 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1772 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1773 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1774 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1775 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1776 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.436s

#1777 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1778 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1779 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1780 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1781 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1782 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1783 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1784 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1785 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1786 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1787 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1788 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1789 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1790 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.436s

#1791 linkCache_getLink using $NBC_LINKCACHE +0s … 0.436s

#1792 benchmarks composed for output. +0s … 0.436s

#1793 calculated avg scores. +0s … 0.436s

#1794 return log +0.003s … 0.439s

GTX 1070 SLI Benchmark vs. GTX 1080, GTX 1070 — Determining Best Value | GamersNexus

The Division Benchmark – GTX 1070 SLI vs. 1070, 1080 at 4K, 1440, & 1080p

The Division is intensive. We use its built-in benchmarking suite for analysis, but there are a few critical points to be aware of: As a game, The Division has pretty heavily varied FPS depending on effects in the environment. Walking through the smoldering ash clouds of an explosive will tank FPS hard for that brief instant in the cloud, but isn’t representative of greater gameplay (and is only an issue with some settings enabled). The Division is also an MMO, which isn’t something we can really test given the latency of the servers and the variability of players on FPS – we need a reproducible scenario.

And so we run the benchmark, but point-out these challenges. The benchmark tends to be representative of real-world, in-game performance (even with other players) as it is exceptionally heavy on the GPU despite a lack of other players.

The Division shows some reasonable gains for SLI. At 4K, we see a scaling of 29.27% against the single GTX 1070 FE, with clock-for-clock configurations. The SLI 1070s run 8.76% faster than a single GTX 1080 in average framerate. 1% and 0.1% lows struggle, meaning that frametimes and overall consistency of framerate (ms-to-ms) is worse than the single GTX 1080 or single GTX 1070.

1440p is a little more favorable for the dual-GPU setup. The GTX 1070s in SLI push 118.3FPS – they were likely choking on pixel count at 4K – and hold a substantial 32.76% lead over the GTX 1080. 1% and 0.1% lows might not be as high as they should be, but are still superior to the single GPU configurations. Against a single GTX 1070, the SLI configuration holds a 50. 37% lead in average FPS.

1080p more-or-less sticks to this. The SLI 1070s distance themselves by 20.54% over the single GTX 1080, and 38.3% lead over the single GTX 1070. The average framerate at 1080p is 157.3FPS, with a >100FPS 1% low.

Mirror’s Edge Catalyst Benchmark – GTX 1070 SLI vs. 1080, 1070 at Hyper

Mirror’s Edge Catalyst came out this week. We ran benchmarks on day-one, our tests finding some odd behavior with low frametimes on AMD devices (as of 16.6.1 hotfix) and VRAM-abusive behavior by the Hyper settings.

ME Catalyst is one of the most GPU-intensive games we’ve tested in recent years, remaining true to its heritage, and even pushes the GTX 1080 into a struggle at 4K/High. When the game’s fluid, it’s beautiful – but the high-paced movement does make a higher framerate desirable for best gameplay (we found 50-60+ FPS to be the preferred window).

NOTE: Mirror’s Edge is the one game where we ran an MSI GTX 1070 Gaming X as the single GTX 1070, rather than the Founders Edition. This is a change we will be making as we roll into the AIB partner cards, and ME Catalyst happened to be the game to initiate that transition. We try to move to AIB partner cards for AMD and nVidia once they ship, since we don’t currently recommend the reference devices and because they’re presently over-priced versus vendor pre-OC versions.

At 1080p/Hyper, the GTX 1070 SLI tops the bench with 105.67 FPS AVG and retains fairly strong 1% and 0.1% lows, despite being imperceptibly lower than the single GTX 1080. The SLI configuration scales 23.68% over a single GTX 1070 (83.3FPS), putting it within ~3FPS of the single GTX 1080 (Δ3.5%).

Moving to more intensive settings, 4K/High shows a gap of 4FPS between the 1080 and 1070 SLI, and a gap of 17FPS between the 1070 and 1070 SLI. As percentages, 4K/High distances the 1080 and 1070 SLI by Δ7.55%, but the 1% and 0.1% lows are much higher on the single GTX 1080 (Δ22.3% for 1% lows, Δ21.59% for 0.1% lows). This is a fairly constant trend for SLI/CrossFire. Against the 1070 non-SLI, we’re seeing delta values of Δ36.56% for the average FPS, with the 1% and 0.1% lows marginally improving. Note again that the single GTX 1070 here is the Gaming X, so the gap is shrunken versus a reference 1070 (with lower clock-rate). These metrics provide hope considering what we just saw with DOOM.

At 1440p, we see a delta of 8.4% between the 1070 SLI and 1070 (remember – settings have changed from “high” at 4K to “ultra” at 1440p, which shifts load to be more intensive after the rasterization step). The 0.1% lows are a fair bit reduced for SLI versus the non-SLI setup, posting 48.67FPS 0.1% low vs. 63FPS 0.1% low.

At 1080p/ultra, the GTX 1080 pulls ahead by 4.47%, with the GTX 1070 SLI setup leading a single GTX 1070 (pre-OC) by 14.12%.

Black Ops 3 Benchmark – SLI GTX 1070 vs. 1070, 1080, more at 4K, 1440, & 1080

Black Ops 3 remains one of the best-optimized games we’ve worked with – perhaps a testament to Activision’s experience in the space. The game has regularly posted strong performance for AMD devices as well, though the Fury X does still suffer at 4K.

At 4K, we’re seeing averages nearing 100FPS on the dual GTX 1070s in SLI, with 1% and 0.1% lows performing near 60FPS – a strong output overall. The single GTX 1080 FE pushes 68FPS average, so that’s a 35.15% difference versus the SLI config. Against a single GTX 1070, the dual setup runs ~58.15% faster in average framerates. The Fury X sustains very low 0.1% metrics because of the 4GB limitation, which is quickly saturated by BLOPS3 at 4K.

At 1440p, we’re seeing 180.3FPS AVG on the SLI GTX 1070s – somewhat absurdly high – netting a ~28.52% difference over the GTX 1080 and 51.29% difference over the single GTX 1070. Good gains over all, with performance well above the magical 144Hz number for ultra-competitive gamers, and nearing 200Hz.

1080p is just comical, with the 2x GTX 1070s pumping 218FPS AVG against the 166FPS AVG of a single card. It’s really not a use case that’s realistic, though; at this point, most dual-1070 users will not be playing 1080p, anyway. Especially with 1440p pushing 180FPS.

GTA V Benchmark – SLI GTX 1070 vs. 1070, 1080, 980 Ti, Fury X at 4K & 1080

GTA V is becoming one of the longer-standing titles on our bench. It’s been intensive, but reasonably well-optimized. We understand the graphics settings exceptionally well as a result of our graphics optimization guide, something which fuels our methodology.

GTA V at 4K also sees >50% scaling versus a single GTX 1070 (55.8%) in the AVG FPS department. 1% and 0.1% lows are also improved, and now land above 30FPS. Together, this makes 4K at Very High / Ultra completely playable on the SLI GTX 1070s, where a single GTX 1070 sees enough dips in performance (in the 1%/0.1% lows) to necessitate a very slight settings reduction. Versus a GTX 1080, the SLI GTX 1070 at 4K show a delta of 34.07%.

We hit a CPU bottleneck at 1080p, with the GTX 1080 and SLI 1070s – and effectively the 1x GTX 1070 – all landing at around the same ~120-125 limit.

Metro: Last Light Benchmark – SLI GTX 1070 vs.

980 Ti, Fury X at 4K, 1440, & 1080

Metro: Last Light will eventually be phased-out of our bench, but its reliability keeps it on for now.

At 4K, we’re seeing 81.3FPS AVG in MLL, equating a 24.28% lead over the GTX 1080 and 42.69% lead over a single GTX 1070. 1440p has the GTX 1070s exceeding 100FPS, with nearly identical percent differences between the single 1080 and 1070. 1080p has us bumping against a performance wall at the top-end of the chart (1080 & 1070s in SLI).

Shadow of Mordor Benchmark – GTX 1070 SLI vs. 1080, Fury X at 4K, 1440, & 1080

The last chart for this FPS bench, we see Shadow of Mordor operating at 87.3FPS on the SLI setup, a good ~27FPS lead (at 4K) over the 1080, or 35.95%, and ~40FPS lead over a single 1070, or 72.8% scaling. That makes Shadow of Mordor one of the most aggressively scaled games, producing real, measurable, and tangible gains otherwise unachievable on other devices.

« Prev Next »

Asus Strix GTX 1070/GTX 1080 O8G review: high-end SLI tested

This is becoming a habit. We don’t usually review aftermarket graphics cards, but when Asus came to us offering to check out the high-end OC versions of their GTX 1070 and GTX 1080, we couldn’t resist. Clinching the deal was the fact that two of each were delivered, meaning we could compare both of Nvidia’s GP104-based graphics cards in SLI with the GP102-based Titan X Pascal — the fastest single-chip GPU money can buy. In theory, both of them should be able to best Nvidia’s top-tier card and by extension, we should be able to get even better 4K performance.

Once the preserve of multi-thousand pound monitors, 4K is now becoming readily accessible at easy to absorb price-points. To put things into perspective, the 40-inch Samsung KU6400 we reviewed last week ranks as one of the best desktop monitors we’ve used — you retain an extreme pixel density, but you get some serious real estate to work with. Combine a screen like this with the Titan X Pascal and you get a stunning PC experience. GTX 1070 in SLI — in theory — looks particularly compelling, offering more performance than the Titan X, at just 63 per cent of the price.

However, it is fair to say that these more expensive Asus Strix cards are rather special. We’re looking at the 08G versions — large, tri-fan cards with ‘Aura’ RGB lighting, deluxe back plates and ultra-quiet operation. Out of the box, these things overclock to 1975-2025MHz depending on load, meaning that you’re getting pretty much everything out of the GP104 core without having to worry about stability. And on top of that load temperatures remain in the early 60 degrees Celsius range. This makes the 08G cards the coolest GP104 cards we’ve seen. Cheaper A8G cards are available that cost significantly less though, but virtually all GTX 1070s and 1080s tend to hit the core limit at 2.05GHz — which is worth bearing in mind here.

Also of interest with these cards is the tweaked port arrangement. Typically, Nvidia clusters three DisplayPorts with one HDMI 2.0 and a dual-link DVI output. Asus drops one of the DPs, instead opting for two HDMIs — and that’s a good thing for those with VR headsets and a UHD screen. Power inputs are limited to one eight-pin socket on the GTX 1070 (more than enough) and a perhaps OTT six/eight-pin arrangement on the 1080. To the best of our knowledge, Nvidia has locked down over-volting on Pascal, so pushing GP104 beyond 2.05GHz is entirely down to the silicon lottery.

Rich presents a video review of the Asus Strix GTX 1070/GTX 1080 O8G cards, with particular emphasis on their SLI prowess.

Similar to competitor cards, there are three performance profiles available with the Strix cards, accessed via a tool called GPU Tweak 2, which also controls the ‘aura’ RGB lighting. OC mode is the standard setting, giving us that circa 2GHz clock with no further tweaking necessary, while gaming mode drops back a couple of percentage points. Silent mode pulls back clocks still further in order to maintain a more discrete profile. Typically, this brings performance down on par with reference clocks, but we found that both Strix 1070 and 1080 still marginally out-perform the Founders Edition cards even with throttled back horsepower. This may change in more thermally constricted environments, however, as the emphasis here is always on discrete acoustics.

Overall then, the O8G Strix cards are superb pieces of engineering but there is an irony in that products geared towards high-end overclockers are actually of more use to those who don’t overclock at all. At most, you can only extract a further 50-75MHz out of the core before stability issues intrude — and those additional clocks will have very little impact on the gameplay experience. You can boost memory on all of these cards by between 600-700MHz (we recommend staying at the former) and the increase in bandwidth certainly helps, but to be frank, this is a tweak that should be possible on every GTX 1070 or GTX 1080 out there.

It all serves to emphasise that the days of overclocks in excess of 20 per cent from the Maxwell days are all but over, and of course, there’s no chance of even the most high-end GTX 1070 matching 1080 performance in the way that GTX 970 could draw on level with 980. And with that circa 2.05GHz hard and fast limit in place on GP104 products, there are strong arguments that you don’t really need beautifully high-end products like this one.

Caption

Attribution

GTX 1070 AC Unity 1440p Asus Silent Asus Gaming Asus OC Asus +50/+600 OC
Low/Avg Frame-Rate 43.0/53.4 44.0/54.4 44.0/54.5 47.0/59.6
SLI Low/Avg Frame-Rate 79.0/102.0 79.0/102.8 79.0/103.8 88.0/109.5
GTX 1080 AC Unity 1440p Asus Silent Asus Gaming Asus OC Asus +50/+600 OC
Low/Avg Frame-Rate 54.0/66.4 55.0/68.2 56.0/69.5 57.0/70.7
SLI Low/Avg Frame-Rate 80. 0/121.0 81.0/122.5 81.0/124.7 99.0/130.9

The core of our work here is going be in assessing SLI performance, but before we do that, we should talk about the practicalities of the set-up. Nvidia has all but abandoned multi-GPU set-ups in excess of two cards (rightly so in our opinion), and has introduced a new SLI bridge that apparently solves bandwidth issues with the old ribbon connectors. You need the right bridge for your motherboard, and choosing the right one is all about the spacing between the main two PCI Express slots on the board.

And this leads us on to another practicality with SLI — thermal management. The cooling assembly used by the likes of Asus, MSI and EVGA pumps heat out into the case, as opposed to the reference designs that propel heat out of the rear of the PC. A general rule of thumb is that custom coolers provide huge benefits in single-card set-ups, but SLI sees tangible benefits from the blower-style thermal solutions typically employed on reference cards. And we definitely saw the results in our tests. With GTX 1070, the second GPU — with plenty of cool air surrounding it — operated at 58 degrees Celsius (a remarkable result for a 2GHz GPU). However, the first GPU, with limited airflow ran a full 10 degrees hotter.

A sub 70 degree result is still exceptional, but generally speaking, our advice would be to space cards with Strix-style coolers as far apart as possible — not so easy on a standard mainstream Z170 motherboard. Typically the higher-end enthusiast boards have more flexibility there. Regardless, the Strix cards still worked beautifully in SLI on our MSI Gaming M7 board, we got nowhere near thermal limits (Nvidia Pascal processors tend to start throttling back around 82 to 83 degrees), and the results were excellent.

4K — and multi-monitor setups — is where SLI scaling is most effective and where we get the most consistently improved performance. When it’s implemented correctly, even GTX 1070 SLI will beat out Titan X Pascal.

3840×2160 (4K) GTX 1070 GTX 1070 SLI GTX 1080 GTX 1080 SLI Titan X Pascal
Assassin’s Creed Unity, Ultra High, FXAA 27.7 56.1 35.4 67.5 43.1
Ashes of the Singularity, Extreme, 0x MSAA, DX12 50.0 65.2 60.8 81.8 63.7
Crysis 3, Very High, SMAA T2x 33.5 54.8 42.3 66.2 50.0
The Division, Ultra, SMAA 33.4 52.8 41.0 63.9 49.6
Far Cry Primal, Ultra, SMAA 35.4 64.2 44.6 79.6 54.7
Rise of the Tomb Raider, Very High, High Textures, SMAA, DX11 38.8 70.1 50.7 86.6 62.3
The Witcher 3, Ultra, Post AA, No HairWorks 39.5 68. 4 50.0 82.2 63.2

We’ll start with 4K, where we see some fascinating results. The performance benchmark for the fastest single-chip solution money can buy is set by Nvidia’s stupendous Titan X Pascal, and the benchmarks are revealing. In every case, GTX 1070 SLI beats the Titan. The margin may well vary from title to title, but the end result is clear — there’s a cheaper route to achieving locked 4K, 60fps gameplay with minimal settings compromises than investing so much in the top-tier Titan. GTX 1070 SLI achieves similar results to Titan X on the hugely demanding Crysis 3, but other titles see big improvements. Rise of the Tomb Raider yoyos between 45-60fps on max settings at 4K during gameplay — GTX 1070 SLI is much more stable, with far less fluctuation from the target 60fps.

Perhaps not surprisingly, GTX 1080 in SLI powers on still further, generally offering 30 per cent more performance than Titan X, rising up to 57 per cent on games that scale exceptionally well, like Assassin’s Creed Unity. And this all comes from a base asking price pretty much on par with the Titan’s cost. Obviously the arrival of GTX 1080 Ti will upset that balance somewhat, but regardless, GTX 1080 SLI throws up exceptional levels of power. Connected up to a 4K screen, the visual payback from titles like Rise of the Tomb Raider and Assassin’s Creed Unity is simply epic.

The drawbacks? They’re the same as they’ve always been. The Division still exhibits some profound micro-stutter issues — you get the frame-rate boost on paper, but the actual real life experience is not great. Curiously though, The Witcher 3 used to exhibit the exact same problems and this has now been resolved. And of course, there’s the fact that some titles simply don’t support SLI, or that the implementation arrives some time after launch. We played Gears of War 4 at 4K60 on the Titan X Pascal and had a great time. Were we to do the same with our 1070/1080 SLI set-ups, that second card would be sat there doing nothing.

Bottlenecking starts to creep in at 1440p resolution and overall scalability suffers. It’s worth remembering that even a single GTX 1070 offers excellent 1440p performance.

2560×1440 (1440p) GTX 1070 GTX 1070 SLI GTX 1080 GTX 1080 SLI Titan X Pascal
Assassin’s Creed Unity, Ultra High, FXAA 54.5 103.8 69.5 122.5 79.4
Ashes of the Singularity, Extreme, 0x MSAA, DX12 64.6 81.6 75.3 91.8 83.7
Crysis 3, Very High, SMAA T2x 70.0 111.1 89.1 131.8 102.8
The Division, Ultra, SMAA 59.7 91.1 73.5 108.0 84.8
Far Cry Primal, Ultra, SMAA 65.0 99.3 80.8 96.0 96.3
Rise of the Tomb Raider, Very High, High Textures, SMAA, DX11 74.2 108.4 96.5 120. 5 114.4
The Witcher 3, Ultra, Post AA, No HairWorks 70.5 112.2 89.1 126.3 108.3

Results begin to close up a little at 1440p in several respects. While there’s still a tangible gain over single card solutions, several titles begin to see performance equalise whether we’re using Titan X Pascal, or either GTX 1070 or GTX 1080 SLI solution. Rise of the Tomb Raider DX11 and Far Cry Primal are perhaps the most obvious examples, demonstrating that the further down the resolution scale we move, the less effective SLI generally becomes — we’re hitting bottlenecks elsewhere within the system. A potential way forward is accept the lower frame-rates and stack up on GPU features instead, where scalability should improve. We tend to use cheap anti-aliasing solutions in our GPU tests, but MSAA would be an option here.

The games that generally tend to scale well still do so, however. Perennial SLI favourite Assassin’s Creed Unity really does see some terrific gains no matter what we throw at it. Even Crysis 3 hands in some impressive returns. However, the fact that we’re approaching system limits also throws up some interesting metrics — scalability improves on the lower-end GTX 1070. Looking at the benchmarks in context via our FCAT analysis demonstrates that with GTX 1080 and to a lesser extent Titan X Pascal, we simply have too much GPU power, meaning we hit a system bottleneck. GTX 1070 SLI scales up to that limit pretty closely, whereas GTX 1080 slams straight into a wall. SLI can also cause some ‘weirdness’ too. For example, Far Cry Primal actually sees a regression in performance on GTX 1080, while GTX 1070 SLI works fine. The same thing happens at 1080p too.

The bottom line seems clear though — GTX 1070, 1080 and Titan X Pascal all produce excellent results at 1440p in single-card configurations, once you’ve adjusted settings to match your hardware. The idea with SLI is that you could in theory service a 120 or 144Hz display, but the reality is that on modern games at least, draw-heavy areas top out at 90-100fps. It’s a nice boost but questions need to be asked about the value proposition here. Perhaps waiting for GTX 1080 Ti to come along seems like a better bet if GTX 1080 isn’t doing it for you.

GTX 1080 and Titan X Pascal are so powerful at 1080p that it’s possible to hit limits elsewhere in the system quite easily. So it’s no real surprise that dual GTX 1070 or 1080 set-ups slam into that same wall in sometimes spectacular style. Suffice to say that even for high frequency display owners, SLI is not recommended for 1080p PC gaming.

1920×1080 (1080p) GTX 1070 GTX 1070 SLI GTX 1080 GTX 1080 SLI Titan X Pascal
Assassin’s Creed Unity, Ultra High, FXAA 84.3 139.9 105.2 150.4 119.2
Ashes of the Singularity, Extreme, 0x MSAA, DX12 71.4 87.9 84.9 90.1 87.6
Crysis 3, Very High, SMAA T2x 111. 3 163.9 137.5 179.4 153.9
The Division, Ultra, SMAA 83.6 124.5 101.4 143.0 117.9
Far Cry Primal, Ultra, SMAA 91.8 98.7 113.3 90.4 132.2
Rise of the Tomb Raider, Very High, High Textures, SMAA, DX11 111.9 137.6 141.9 129.8 160.6
The Witcher 3, Ultra, Post AA, No HairWorks 98.3 129.1 119.4 130.9 137.6

Finally, we have 1080p metrics, and we’ve included these for the two reasons — firstly, full HD remains the most popular gaming resolution according to the Steam hardware survey, and secondly, once again, there are a lot of high frequency refresh displays out there where, in theory, an SLI set-up could really help.

However, the bottom line is clear — we hit system limits fast. It’s true that you do seem some scalability in performance, but obviously the average frame-rates are depressed somewhat. But the key here is that we are talking about the increase as an average, suggesting a sustained performance boost across the gameplay. Watch the performance video above and the reality becomes clear — frame-rates jump high then crash down low. There is little in the way of a uniform boost in most titles and much of your GPU power is wasted here.

There’s further food for thought as we look at lowest recorded frame-rates. With the exception of Ashes of the Singularity, GTX 1070 under the most immense loads always remains above 60fps in our benchmark titles. There’s still further sustained scalability by moving up to a single GTX 1080, but beyond that the bottlenecks can hit hard — whether we’re using Titan X Pascal or SLI.

Caption

Attribution

The Asus Strix cards we tested were beautifully designed, exceptionally well put together and they overclocked like demons out of the box with zero user effort required. However, in common with the MSI GTX 1080 Gaming Z we tested a while back, gains to core clock beyond the factory OC are limited, with the biggest boosts coming from overclocking VRAM — though results there will obviously very on the title you’re playing. And with that hard and fast limit in place, much cheaper examples of the card can effectively reach the same speeds — though perhaps not with the exceptional thermal and acoustic performance seen here.

SLI testing proved to be a fascinating experiment, but it’s safe to say that performance can vary wildly at lower resolution and it’s really at ultra HD (or with multi-monitor support) where SLI really starts to make sense. Going into our tests, we expected limited scalability, with Titan X Pascal still taking point — if not in terms of frame-rates, certainly in terms of stability. However, The Division aside, GTX 1070 did an excellent job of matching and exceeding Titan X performance. It’s interesting to note though, that GTX 1080 SLI only adds around 10-15fps at 4K — it’s a very useful cushion to have, but similar results can be achieved by careful settings management on a 1070 SLI set-up without too much of a hit to image quality.

And with that in mind, of both the SLI configurations tested, it’s GTX 1070 that sort of makes the most sense. You get the GPU power required to hit 4K at 60fps in a great many demanding titles, it’s the cheapest Pascal SLI set-up available and clearly offers the best balance of price vs performance. At 4K with a 60fps limit in place, the actual experience offered by 1070 and 1080 in SLI was remarkably close, and on key test titles like Rise of the Tomb Raider and Crysis 3, the vast amount of extra cash you’d need for GTX 1080 SLI actually translated into little more than improved anti-aliasing and an improved grip on the target frame-rate. We’re left wondering what Titan X Pascal or a prospective GTX 1080 Ti SLI could actually offer when even 1070 SLI is so, so good.

But of course, it’s the spectre of the inevitable upcoming GTX 1080 Ti (we hope to see it by January) that should make anyone think very carefully about a prospective SLI purchase in the short term. We can safely assume it’ll be cheaper than any Pascal SLI configuration in the here and now, and using Titan X as a rough performance guideline, the price vs performance outlook for high-end users should be impressive. And on top that, its arrival may also see a price-cut for the GTX 1080. But beyond the theoreticals, the reality is this — 4K gaming at 60fps is terrific with the right display, and while Titan X Pascal is the current best choice in terms of single-chip GPUs, even GTX 1070 SLI still packs one hell of a punch.

Video accelerator Nvidia GeForce GTX 1070 Ti

Part 1: theory and architecture

Contents

  • Part 1 — Theory and Architecture
  • Part 2 — Practical Introduction
    • Video card features
    • Synthetic test results
  • Part 3 — Game Test Results and Conclusions

Introducing the basic detailed review of the Nvidia GeForce GTX 1070 Ti.

Reference

  • Gaming Video Card Buyer’s Guide

  • AMD Radeon HD 7xxx/Rx
  • Handbook

  • Nvidia GeForce GTX 6xx/7xx/9xx/1xxx Handbook
  • Full HD video stream processing capabilities
  • 3D game testing methodology and settings

Object of study : 3D graphics accelerator (video card) Nvidia GeForce GTX 1070 Ti 8 GB 256-bit GDDR5

Developer information : Nvidia Corporation (Nvidia trademark) was founded in 1993 in the USA. Headquarters in Santa Clara (California). Develops graphic processors, technologies. Until 1999, the main brand was Riva (Riva 128/TNT/TNT2), from 1999 to the present — GeForce. In 2000, the assets of 3dfx Interactive were acquired, after which the 3dfx / Voodoo trademarks were transferred to Nvidia. There is no production. The total number of employees (including regional offices) is about 5,000 people.

Part 1: Theory and Architecture

It would seem, why would Nvidia release something else in 2017, because they already have a rather slender line of video cards covering almost all niches? But their competitor recently deigned to release not one, but two models of their high-end graphics solutions, although with different parameters and price, but the difference in speed between them was not as big as between the GTX 1080 and GTX 1070, and the Radeon RX The Vega 56 ended up being slightly more powerful than the GeForce GTX 1070 and much closer to the GTX 1080 at a lower recommended price.

That is why a small niche has formed for the release of another possible variant of the video card, which is aimed at today’s novelty — the GeForce GTX 1070 Ti. The new model sits between the very popular GeForce GTX 1080 and GTX 1070 graphics cards. It is clear to everyone that this is a direct competitor for the Radeon RX Vega 56. In principle, Nvidia could not release anything against the Vega 56 at all, since the latter is still sold at a higher price. the recommended price and is not such a terrible competitor for them, but they still decided to fill, albeit a small, but still manifested hole in their lineup.

And now the modern line of Nvidia GeForce GTX video cards based on the Pascal architecture consists of the following models: GeForce GTX 1080 Ti, GeForce GTX 1080, GeForce GTX 1070 Ti, GeForce GTX 1070, GeForce GTX 1060 6GB (oh, you could call it also Ti — for beauty), GeForce GTX 1060 3GB, GeForce GTX 1050 Ti, GeForce GTX 1050, GeForce GT 1030. And so the rather slender Nvidia line just became a little denser.

The GeForce GTX 1070 Ti launches today, right after or right before the release of several high-profile games this fall: Destiny 2, Star Wars Battlefront II, Call of Duty: WWII, Need for Speed: Payback and many more. The new graphics card is a great option for enthusiasts who require enough power from the video subsystem for all modern games at maximum quality settings. And the new model has enough performance to provide a comfortable frame rate in almost all games at maximum or very high settings and high resolutions.

Compared to its predecessor, which Nvidia itself considers the GeForce GTX 970, the GTX 1070 Ti should provide about twice the final performance (according to company experts), and for those who want to achieve even greater performance, the GeForce GTX 1070 Ti provides considerable room for overclocking, allowing you to almost catch up with the speed of the GeForce GTX 1080, operating at standard frequencies.

Since Nvidia’s new video card is based on the Pascal architecture GPU we already know, which has much in common with the previous second generation Maxwell architecture, before reading this material, we advise you to read the early articles about the company’s most notable video cards:

  • [03/09/17] Nvidia GeForce GTX 1080 Ti is the new king of gaming 3D graphics, far ahead of other top accelerators
  • [17. 05.16] Nvidia GeForce GTX 1080 is the new leader in 3D gaming graphics on PC
  • [06/01/15] Nvidia GeForce GTX 980 Ti is the fastest single-GPU gaming accelerator
  • [22.04.15] Nvidia GeForce GTX Titan X — the most powerful single-processor accelerator
  • [19.09.14] Nvidia GeForce GTX 980 is a follower of the GeForce GTX 680, outperforming even the GTX 780 Ti

Let’s take a look at the detailed specifications of the GeForce GTX 1070 Ti based on a stripped down version of the GP104 GPU.

hardware support

GeForce GTX 1070 Ti
Parameter Meaning
Chip code name GP104
Production technology 16nm FinFET
Number of transistors 7.2 billion
Kernel area 314 mm²
Architecture Unified, with an array of common processors for stream processing of multiple types of data: vertices, pixels, etc.
DirectX DirectX 12, with Feature Level 12_1 support 9009four
Memory bus 256-bit: Eight independent 32-bit memory controllers supporting GDDR5 and GDDR5X memory
GPU frequency 1607 (1683) MHz
Computer units 19 (out of 20 physical) streaming multiprocessors, including 2432 (out of 2560 physical) scalar ALUs for floating point calculations within the IEEE 754-2008 standard;
Texture blocks 152 (out of 160 physical) texture addressing and filtering units with support for FP16 and FP32 components in textures and support for trilinear and anisotropic filtering for all texture formats
Raster Operation Blocks (ROP) 8 wide ROPs (64 pixels) with support for various anti-aliasing modes, including programmable and with FP16 or FP32 frame buffer format. Blocks consist of an array of configurable ALUs and are responsible for generating and comparing depth, multisampling and blending
Monitor support Integrated support for up to four monitors connected via Dual Link DVI, HDMI 2. 0b and DisplayPort 1.2 (1.3/1.4 Ready)

GeForce GTX 1070 Ti Reference Specifications
Parameter Meaning
Core frequency 1607 (1683) MHz 9009four
Number of universal processors 2432
Number of texture units 152
Number of blending units 64
Effective memory frequency 8000 (4×2000) MHz
Memory type GDDR5
Memory bus 256-bit
Memory capacity 8 GB
Memory bandwidth 256 GB/s
Computing performance (FP32) about 8 teraflops
Theoretical maximum fill rate 103 gigapixels/s
Theoretical texture sampling rate 244 gigatexels/s
Tire PCI Express 3. 0
Connectors One Dual Link DVI, one HDMI and three DisplayPort
Power consumption up to 180 W
Power supply One 8-pin connector
Number of slots occupied in the system chassis 2
List price $449 (US), 33,990 (Russia)

The new model of the GeForce GTX 1070 Ti video card received a quite logical name for the company’s solutions. Since it is located in the line between the GTX 1080 and GTX 1070, they decided to call it traditionally, simply adding the Ti prefix to the smaller value. The novelty does not replace any video cards in the current line of the company, but complements the modern GeForce 1000 family. Below it in the hierarchy is the GeForce GTX 1070 model, based on an even more stripped down version of the GP104 chip and having lower performance, and above it is the GTX 1080 on the full version the same GPU, and using GDDR5X memory.

The recommended price for a new Nvidia video card starts at $449 (33,990 in Russia), and this is a very good offer, given that the new product should not be too seriously inferior to the GTX 1080. Although Nvidia’s response to the Radeon RX Vega 56 had to wait for some time, the blow to the competitor today is quite strong — at a speed close to the GTX 1080, the new product looks very attractive. To date, the GeForce GTX 1070 Ti is, in principle, one of the best solutions on the market for powerful gaming graphics cards in terms of price and performance.

The video card under consideration today is based on the GP104 chip, which has a 256-bit memory bus, but, unlike the GeForce GTX 1080, it was decided to install not a new type of GDDR5X memory, but the good old GDDR5, operating at a fairly high effective frequency of 8 GHz , which gives a decent peak throughput of 256 GB/s. The amount of memory installed on a video card with such a bus could be equal to 4 or 8 GB, but a lower value is simply unacceptable in modern conditions, so the GTX 1070 Ti logically received 8 GB of memory, which is enough to run any 3D applications with any quality settings both now and in the coming years.

As has become a tradition for Nvidia, they also release their own special edition of the video card — the GeForce GTX 1070 Ti Founders Edition, which is based on the same dual-FET five-phase power system as the older GeForce GTX 1080 board Founders Edition, which provides good headroom for overclocking and decent power efficiency. The printed circuit board of the reference GeForce GTX 1070 Ti, for obvious reasons, differs little from the same GTX 1080. The length of the PCB from the GeForce GTX 1070 Ti is the traditional 27 cm, and one HDMI, two DVI and three DisplayPort connectors are offered as image output ports. Like its sisters, the board is content with one 8-pin auxiliary power connector, but partners are free to install other, more powerful power systems that have a power reserve.

Unsurprisingly, the GeForce GTX 1070 Ti Founders Edition features the same copper vapor chamber cooler we saw on the stock GTX 1080 board. The 180W Edition clearly has a lot of headroom in terms of cooling efficiency, which will also allow enthusiasts to raise the GPU’s turbo frequency and power consumption limit, providing a noticeable boost in the final 3D performance.

As far as Nvidia’s custom-designed graphics cards are concerned, they’ve traditionally offered a wide selection of their own GeForce GTX 1070 Ti models since launch day, including options with custom PCB designs and even more efficient cooling systems. And some of the company’s partners are also offering miniature variants of the GeForce GTX 1070 Ti that will fit into smaller Mini-ITX cases.

Architectural features

The GeForce GTX 1070 Ti is far from the first generation of the Pascal graphics architecture, it is based on the same GP104 GPU as the GeForce GTX 1080 with the GTX 1070. The use of 16 nm FinFET manufacturing process in the production of these GPUs at TSMC made it possible to significantly increase chip complexity and clock frequency while maintaining a relatively low area and cost. Architecturally, the Pascal family chip is similar to similar solutions from previous generations of Nvidia, but there are some differences, which can be read in detail in the reviews of the company’s previous solutions.

Each Streaming Multiprocessor (SM) is paired with a PolyMorph Engine that handles texture sampling, tessellation, transformation, vertex attribute setting, and perspective correction. The combination of an SM multiprocessor with one Polymorph Engine is traditionally called TPC — Texture Processor Cluster for Nvidia, and several TPCs, together with a rasterization engine, form graphics clusters — Graphics Processor Cluster (GPC).

The GP104 GPU has four GPC clusters and enough power for all kinds of games, but it is also very energy efficient with only one 8-pin power connector for power consumption below 200W. However, in order not to make the GeForce GTX 1080 model completely useless after the release of the GTX 1070 Ti, the new product uses a chip cut down to 19Streaming Multiprocessor (SM), one of which is disabled at the hardware level:

That is, the GPU in the GeForce GTX 1070 Ti has 2432 active CUDA cores and 152 texture units, and in these characteristics it is much closer to the GTX 1080 (2560 CUDA cores and 160 TMUs) than the GTX 1070 (1920 CUDA cores and 120 TMUs). But what the new model has left of the GeForce GTX 1070 is the entire memory subsystem. The GeForce GTX 1070 Ti also has 8 GB of GDDR5 video memory operating at an effective frequency of 8 GHz and is connected to the GPU via a 256-bit bus consisting of eight 32-bit controllers. Eight ROPs and 256 KB of L2 cache are tied to each of the memory controllers. That is, the stripped-down GP104 chip also contains 64 ROPs and 2048 KB of L2 cache, just like the full-fledged one.

Accordingly, in terms of memory bandwidth, the new product is no different from its younger sister, but this practically does not limit performance in most applications — in games, after all, computational and texture performance is much more important, in which the new product is noticeably faster than the GTX 1070 and only slightly behind from the GTX 1080. Largely because both the base and turbo frequencies of the GeForce GTX 1070 Ti are left quite high: the base frequency is 1607 MHz, and the turbo is 1683 MHz. At the same time, the turbo frequency is only the average frequency at which the GPU operates in a test set of gaming and other applications, and the real one in many cases will be even higher thanks to GPU Boost 3.0 technology.

With all the other features of the GP104 GPU, including details of the GPU Boost 3.0 algorithm, improved framebuffer compression, support for asynchronous computing, multi-projection technology, and improvements to output and video data processing units, you can find out in our review of the GeForce GTX 1080, because the new is no different from this early model in terms of functionality.

Theoretical Conclusion

Judging by the technical specifications and peak theoretical values, the new GeForce GTX 1070 Ti should be a very strong competitor for the Radeon RX Vega 56 in the market. Both of these graphics cards are designed for any modern game at maximum quality settings and on displays with a resolution of at least 2560 × 1440 pixels. Also, the novelty from Nvidia is perfect for those rare players who use virtual reality helmets that are even more demanding on GPU power.

By the way, even though Nvidia itself advises using even more powerful solutions like the GeForce GTX 1080 Ti or Titan X for monitors with 4K resolution, even a single GeForce GTX 1070 Ti will allow you to play many games in such conditions with quite acceptable frame rate, although for the most demanding projects it would really be better to put either a more powerful GPU or at least a second GTX 1070 Ti in an SLI configuration (and put up with some features and limitations of multi-chip rendering at the same time). In addition, the GeForce GTX 1070 Ti is distinguished not only by high performance, but also by rich functionality, support for many new features and algorithms — everything that the Pascal family can do.

The availability of video cards of the new GeForce GTX 1070 Ti model from Nvidia partners (Asus, EVGA, Gigabyte, Innovision 3D, MSI, Palit and Zotac) in retail sales is expected immediately from the day of the announcement — November 2, but the reference GeForce GTX 1070 Ti Founders Edition of Nvidia itself should appear in the online store of the company’s Russian website towards the end of the same month.

In the following parts of our material, we will evaluate the performance of the new GeForce GTX 1070 Ti video card in practice, comparing its speed with other similarly priced single-chip video systems from Nvidia and AMD, related to modern generations of graphics processors. First, let’s look at the data obtained in our synthetic test suite, and then we’ll get to the games.

Nvidia GeForce GTX 1070 Ti — Part 2: Card Features and Synthetic Benchmarks →

Average price (number of offers) in Moscow retail:
Cards in question Competitors
GTX 1070 Ti 8 GB — 34,000 (as of 11/01/17) GTX 1080 8 GB — 36,000 (as of 11/01/17)
GTX 1070 Ti 8 GB — 34,000 (as of 11/01/17) R9 Fury X 4 GB — 28,700 (as of 08/03/17)
GTX 1070 Ti 8 GB — 34,000 (as of 11/01/17) RX Vega 56 8 GB — 36,500 (as of 11/01/17)
GTX 1070 Ti 8 GB — 34,000 (as of 11/01/17) RX Vega 64 8 GB — 39,500 (as of 11/01/17)

We thank the company Nvidia Russia
and personally Irina Shekhovtsova
for the video card provided for testing

Seasonic Prime 1000 W Titanium power supply for test bench supplied by Seasonic

AMD Radeon R9 8 GB 3200 MHz UDIMMs for test bench courtesy of AMD

Asus ROG Crosshair VI Hero test bench provided by AMD

CPU Cooler Antec Kuhler h3O 920 for test bench provided by AMD

Dell UltraSharp U3011 Test Bench Monitor provided by Ulmart

Corsair Obsidian 800D Full Tower Test Bench provided by Corsair

Seagate Barracuda 7200. 14 3 TB hard drive for test bench courtesy of Seagate

ASUS ROG STRIX GTX 1070 Ti GAMING Advanced Video Card Review: Upgraded

In early November, NVIDIA expanded its line of discrete gaming graphics with the introduction of the GeForce GTX 1070 Ti. The model is based on the already familiar GP104 processor with Pascal architecture, but the proposed combination of technical characteristics and price may well be of interest to those who have already grown out of middle-class devices, but are not ready to spend money on buying top-end video cards. Simultaneously with the reference models, the original versions of the adapters were also presented. Today we are reviewing ASUS ROG-STRIX-GTX1070TI-A8G-GAMING — a modification from the ROG STRIX line, which has recognizable external features and interesting equipment.

Help

Zmіst

  • 1 NVIDIA GEFORCE GTX 1070 TI
  • 2 ASUS ROG-STRIX-GTX1070TI-A8G-GAMING
  • 9000 3 Design set and componing

    9000 9000 9000 6 RECOMP 7 Performance

NVIDIA GeForce GTX 1070 Ti

The history of the GeForce GTX 1070 Ti is quite short. It is unlikely that Californians planned to fill the niche between the GTX 1080 and GTX 1070 before entering the graphics arena in the face of the Radeon RX Vega 56/64. These models are well balanced and provide decent results in their niches. However, NVIDIA decided not to disregard the appearance of direct rivals from the opposing camp.

So what is the GeForce GTX 1070 Ti? The already well-known GP104 chip with Pascal architecture is used for the video card. In this case, a modification of the GP104-300 processor is used, which includes 2432 calculators, 132 texture modules and 64 rasterizers.

Course

Development in Python

Introduce popular language programming to earn $1300 via rіk

REGISTER!

GeForce GTX 1080 Ti GeForce GTX 1080 GeForce GTX 1070 Ti GeForce GTX 1070
Crystal name GP102-350 GP104-400 GP104-300 GP104-200
Manufacturing process, nm 16 16 16 16
Chip area, mm² 471 314 314 314
Number of transistors, billion 12 7. 2 7.2 7.2
GPU clock frequency, MHz 1480/1582 1607/1733 1607/1733 1506/1683
Number of stream processors 3584 2560 2432 1920
Number of texture units 224 160 132 120
Number of ROPs 88 64 64 64
Memory (type, volume), MB GDDR5X, 11264 GDDR5X, 8192 GDDR5, 8192 GDDR5, 8192
Memory bus bit 352 256 256 256
Effective memory clock frequency, MHz 11 008 10 008 8008 8008
Memory bandwidth, GB/s 484 320 256 256
TDP W 250 180 180 150

To compare quantitative values, we suggest that you familiarize yourself with the technical characteristics of the neighbors on the graphic ruler. As you can see, the number of CUDA calculators and TMUs has increased significantly compared to those for the GTX 1070, but the number of rasterization units remains the same for all three video cards.

The memory subsystem configuration is similar to that used for the GeForce GTX 1070. We are talking about a 256-bit bus and GDDR5 chips operating at an effective 8008 MHz. The total throughput is 256.3 GB / s. It is the memory subsystem that is the main advantage of the GeForce GTX 1080. If the difference is already minimal in terms of the number of active functional units in the GPU, then it is precisely due to the GDDR5X chips operating at 10,008 MHz, and, accordingly, increased bandwidth to 320 GB / s, the older model will offer more performance. But again, suppose that even in this case the difference will not be striking.

The GeForce GTX 1070 Ti claims the same TDP as the GTX 1080 at 180W, while the GTX 1070 has a TDP of 150W.

The reference model GeForce GTX 1070 Ti is visually no different from its neighbors in the lineup. To connect additional power, one 8-pin connector is provided, and for a system with such a video card, the developer recommends using a PSU with a power of 500 W or more. The interface panel has a familiar set of video outputs — DVI-D, HDMI and three DisplayPort.

In terms of price, the recommended price for the base versions is $430, while the reference modification from the Founders Edition will be offered from $450.

Along with the reference version, original versions from video card manufacturers were also presented. It didn’t require a lot of effort, except for minimal tweaks to the designs used for the GeForce GTX 1070/1080. Therefore, it is not surprising that already at the start of sales of the GeForce GTX 1070 Ti, alternative versions of adapters are offered on the market.

ASUS ROG-STRIX-GTX1070TI-A8G-GAMING

ASUS offered three modifications of the GeForce GTX 1070 Ti at once — a pair of ROG STRIX series models and one version of the TURBO line with a cooling system equipped with one centrifugal fan.

It is curious that the ROG-STRIX-GTX1070TI-A8G-GAMING and ROG-STRIX-GTX1070TI-8G-GAMING modifications are not only similar in appearance, but also have the same frequency formulas. As you can see, the designation of the older model does not contain the usual “OS” or “O” indices, which imply factory overclocking of the video card. Initially, it was supposed by the manufacturer, however, in order to avoid possible competition with the GeForce GTX 1080, NVIDIA strongly discouraged offering original versions of video cards with higher frequencies. As a result, without exception, all GeForce GTX 1070 Ti models have the same frequency formula, corresponding to that of the reference video card — a base frequency of 1607 MHz and an average acceleration of up to 1683 MHz.

For graphics card manufacturers, this was probably not a very pleasant surprise. Frequency variation just allows you to build a line of adapters of the same series, expanding the range with various modifications.

ASUS had to get out of the situation by using a new term for the top version — Advanced Edition. When using the OC Mode profile, the frequency formula for the GPU takes the form of 1683/1759 MHz, while in the regular version of ROG-STRIX-GTX1070TI-8G-GAMING the same software overclocking corresponds to the 1645/1721 MHz mode.

Delivery set

The video card is supplied in a large box. Included with the video card is only a manual, a disk with drivers and software, as well as two reusable cable ties for laying power cables.

Design and layout

The external design of the video card with a strict graphite casing is well recognizable. This design has been used by the manufacturer for top-end video cards for some time. On closer examination, the original GTX 1070 Ti does not even resemble the GTX 1070/1080 of the STRIX series, but the GTX 1080 Ti model of the same line.

The fact is that the new «titanium» version uses a cooling system with an enlarged radiator block.

Cooler modification has two compartments made of aluminum plates. In this case, the width of the ribs of the main module is 27 mm. The blocks are interconnected by heat pipes, which accelerate the removal of heat to remote areas.

Another difference from the GTX 1070/1080 coolers is the rejection of the technology of direct contact between the heat pipes and the GPU chip. This method has both its advantages and disadvantages. Apparently, the latter still outweighed, therefore, for the latest models, ASUS developers use an additional heat-removing plate, which excludes the appearance of local overheating zones.

For better contact with the GPU chip, the surface of the heat sink is polished, and additional processing is named MaxContact by the manufacturer.

Of the curious design features, we note the developers’ attempt to maximize the heatsink’s dissipation area, because some of the plates have a complex profile shape in those areas where it allows the placement of surface-mounted elements.

Close examination of the unit reveals traces of soldering in the places where the heat pipes meet the plates and in the area of ​​contact with the main heat sink.

The radiator block is blown by three 90mm axial fans.

The video card uses a minimally modified platform from the GeForce GTX 1070 STRIX series. The power subsystem has a 7-phase layout (6+1).

Uses Vishay SIC620 MOSFET assembly and UPI uP9511P master controller. The main radiator block is used to cool the power elements.

Like all GTX 1070 Ti series graphics cards, the original version from ASUS is equipped with 8 GB of GDDR5 memory. In this case, Micron D9 microcircuits are used.TCB, with a recommended effective frequency of 8000 MHz. Eight chips are arranged in a U-shape around the GPU. Part of the microcircuits is additionally cooled by a metal plate, although its profile is more like a bracket that connects the printed circuit board to the fixing plate and increases the strength of the structure. It does not cover all memory chips, and only partially contacts with some. Nothing new here, the same «cooler-hardener» was used for the manufacturer’s GTX 1070/1080.

Due to the enlarged radiator block, the graphics card has a 2.5-slot layout. That is, in fact, it occupies all three expansion slots. This is generally not a problem for ATX format systems. After integrating sound and network controllers on the motherboard, more often additional slots remain unclaimed. In any case, the increased dimensions of ASUS ROG-STRIX-GTX1070TI-A8G-GAMING should be taken into account, especially for owners of mATX motherboards. The length of the video card is also a considerable 298 mm — another reason to first make sure that the adapter has a place in the case.

There are two 4-pin fan connectors at the back of the PCB. ASUS FanConnect II technology allows you to set the behavior of the fans installed in the case using the temperature readings of the GPU.

Of course, additional illumination is provided for the video card. Moreover, the manufacturer pays great attention to this issue. The light guides are woven along the perimeter of the upper casing.

The name of the line is illuminated on the top hem and a large series logo sparkles on the back. Of course, we are talking about multi-color RGB backlighting, the parameters of which can be controlled in the proprietary ASUS AURA application.

When using an ASUS motherboard and other system components that support AURA Sync technology, the illumination of all devices can be synchronized.

From the functional illumination, we note the presence of LEDs next to the power supply connector. The red light is on if you have not yet connected an additional source, and the white one indicates the supply of 12 V.

An anodized aluminum plate covers the back of the video card. An additional rear cover will not hurt, and it adds spectacularity to the device, although it does not participate in the cooling of the elements.

The interface panel has five video outputs — DVI-D, a pair of DisplayPort and two HDMI. Part of the plate is dedicated to the air outlet grille.

In use

At rest, the graphics card is in passive mode. Chip temperature is kept at 33C at 23C indoors.

Under load, the GPU warmed up to 65 degrees, while the fan speed increased to 1300 rpm.

Video card is very quiet. The increased dimensions of the radiator block are justified. In this case, it is possible to improve the cooling efficiency without increasing the fan speed. The latter begin to rotate when the chip temperature rises to 55–57C. The start is smooth from 600–700 rpm. Disabled when the GPU cools down to 47C.

Under load, the GPU automatically accelerates up to 1885 MHz. Weak chip heating allows GPU Boost to keep a high frequency even in difficult modes. Despite the identical frequency formula of all GeForce GTX 1070 Ti models, the actual frequency will depend on the capabilities of the cooling system of a particular adapter model.

Overclocking

NVIDIA’s strong recommendation not to offer accelerated versions of adapters fortunately affected only video card manufacturers. Owners can feel free to experiment with their devices.

The frequency potential of the GP104 chip as a whole has already been well studied, so we shouldn’t expect any revelations here. As usual, the final values ​​largely depend on the success of a particular instance of the GPU.

In our case, after increasing the supply voltage by 20 mV and setting the Power Limit slider to 120%, we managed to increase the base clock frequency of the chip from 1607 to 1767 MHz, that is, by almost 10%. Memory chips worked stably at 8808 MHz, that is, the same + 10%.

After overclocking in dynamics, the processor automatically overclocked to 2025-2050 MHz — typical values ​​for the accelerated GP104. The chip often easily takes the bar at 2 GHz, and anything higher depends on luck and your perseverance.

With an increase in frequencies, the chip was heated to 67C, and the fan speed automatically increased to 1400 rpm at the peak.

Performance

The GeForce GTX 1070 and GeForce GTX 1080 video cards will allow you to fully evaluate the performance of the new product. Without pretending to be a seer, even before the start of testing, we can say that the GeForce GTX 1070 Ti is an intermediate link between these models with the appropriate level of performance . However, actual measurements allow us to more accurately determine the position of the new video card, as well as understand the prospects and evaluate the effectiveness of additional overclocking. The presence of GeForce GTX 1080 Ti indicators on the diagrams allows you to set the upper bar. In this case, a cozy cabal of models on the GP104 will dilute the top model with a higher class.

To evaluate the capabilities of the video card, we used popular graphics modes with resolutions of 1920×1080, 2560×1440 and 3840×2160.

Futuremark’s gaming synthetics set the tone. The GeForce GTX 1070 Ti is located exactly between the GTX 1070 and GTX 1080, while the new product gravitates towards the older model, and after overclocking it can catch up or even outperform the GPU version with a large number of computing units and faster memory.

If we evaluate the results in real games, the situation is largely similar. The GeForce GTX 1070 Ti in stock mode is inferior to the GeForce GTX 1080 by an average of 5-10%, in turn, outperforming the GeForce GTX 1070 by 10-15%. Depending on the game, there are slight distortions, but in general the balance of forces remains the same. As you can see, in Full HD mode, in many cases, the GeForce GTX 1080 Ti is redundant even when using heavy graphics modes. The extra headroom never hurts, especially when using a monitor with a refresh rate above 60Hz, but at this screen resolution, you may find that the performance gain is more modest than the price increase, even if your system is equipped with a top-end 6-core Core i7-8700K.

In 1440p mode, the situation is largely the same among GP104-based models, with the only difference being that the GTX 1070 Ti even after additional overclocking became more difficult to outperform the GTX 1080. Still, the latter has a larger number of computing units and an increased bandwidth of the memory subsystem due to GDDR5X chips operating at an effective 10,008 MHz. However, there is no need to talk about cardinal differences here. The stock GeForce GTX 1070 Ti is still closer to the older model of the line and catches up with it after overclocking. We observed situations when even after the afterburner the new product turned out to be half a step away from the GTX 1080, but in these cases it was a maximum of 1-2 frames / s.

At a resolution of 2560×1440, the GeForce GTX 1080 Ti already confidently breaks away from its pursuers. The columns with the values ​​of the model on the GP102 chip proudly rise above those for the lower devices of the line. 30-40% is already the difference that you expect from the flagship of the “thousandth” GTX line.

4K resolution brings no surprises. Models on the GP104 retain their positions and balance of power. The GeForce GTX 1070 Ti is 8-12% ahead of the GTX 1070, yielding to the older model by 5-10%. Lagging behind the GTX 1080 can often be compensated by overclocking, which is not possible in the case of the GTX 1070. Although it is not always easy to provide an advantage over a model with a higher memory subsystem bandwidth by brazenly increasing the GPU frequency, and this is especially true in higher resolution modes. Of course, when overclocking the GTX 1080, it will once again move away from the daring novelty, which is literally stepping on its heels.

Summarizing the results obtained, we can only affirm that the appearance of the «titanium» version of the GTX 1070 in the lineup is primarily associated with the introduction of competing Radeon RX Vega 56/64 models. For NVIDIA, it was rather a matter of principle not to give way to the position of the younger «vega» in its category, and the GTX 1070, apparently, did not always cope with this task. Has the situation changed now? We have yet to verify this from our own experience.

4.5

ITC.UA score

Pros:
High performance; efficient quiet cooling system; powerful power subsystem; the possibility of independent overclocking; spectacular backlight RGB AURA

Cons:
Price at the start of sales; increased dimensions; not provided for factory overclocking

Output:
ASUS ROG STRIX GTX 1070 Ti GAMING Advanced is the original model of a new line of adapters that occupy a place in the top gaming segment. We can note the increased dimensions of the device, an efficient quiet cooler, a powerful power subsystem and attractive backlighting. In terms of performance, the GeForce GTX 1070 Ti is often inferior to the older GTX 1080 by only 5-10%, and this difference can be easily compensated by overclocking the video card. Given its hot new status, the retail price of the GTX 1070 Ti is often only slightly lower than that of the older model, and in this case, there are fewer arguments in favor of the novelty. On the other hand, if we consider models of equivalent equipment, then the GTX 1070 Ti will be 10% cheaper than the GTX 1080, so if you want to save a little, this choice will be justified.

Specifications

Test device provided by MTI, www.distri.mti.ua

Video card Palit GeForce GTX 1070 Ti 1607MHz PCI-E 3.0 8192MB 8000MHz 256 bit DVI HDMI HDCP Super JetStream

Advantages

Defects

Comment

Estimated

I accept the terms
providing data.

  • NVIDIA GEFORCE GTX 1070 TI
  • 8000 8000 MB GDDR5
  • Frequency Nucleus/Memory: 1607/8192 MHz
  • Support SLI/Crossfire
  • , DIPLAYPORT X3
  • Vulkan
  • work with 4 monitors

Average rating Video card Palit GeForce GTX 1070 Ti 1607MHz PCI-E 3.0 8192MB 8000MHz 256 bit DVI HDMI HDCP Super JetStream — 5
A total of 8 reviews are known about Video Card Palit GeForce GTX 1070 Ti 1607MHz PCI-E 3.0 8192MB 8000MHz 256 bit DVI HDMI HDCP Super JetStream

HDMI HDCP Super JetStream?

From 11 sources we collected 8 negative, negative and positive reviews.

We will show all the advantages and disadvantages Palit GeForce GTX 1070 Ti 1607MHz PCI-E 3.0 8192MB 8000MHz 256 bit DVI HDMI HDCP Super JetStream detected by users. We do not hide anything and post all positive and negative honest customer reviews about Palit GeForce GTX 1070 Ti 1607MHz PCI-E 3.0 8192MB 8000MHz 256 bit DVI HDMI HDCP Super JetStream video card, and we also offer alternative analogues. Is it worth it to buy — the decision is only yours!

Best deals on Video Card Palit GeForce GTX 1070 Ti 1607MHz PCI-E 3.0 8192MB 8000MHz 256 bit DVI HDMI HDCP Super JetStream

Reviews of Video card Palit GeForce GTX 1070 Ti 1607MHz PCI-E 3.0 8192MB 8000MHz 256 bit DVI HDMI HDCP Super JetStream

Review information updated on 09/28/2022

write a feedback

Natalia F., 01/14/2020

Pros: Excellent video card, very quiet, even at maximum loads.

Disadvantages: Price ))

Comment: When buying, do not forget about the dimensions. Excellent cooling led to an increase in the radiator.

A. V., 01/02/2020

Advantages: Everything in it is fine, without the operation of valves in idle time and surf on an Internet 33 degrees for mine) Battle warmed it up by only 64) top for my money 🙂

Oleg, 11/17/2019

Pros: Good performance, cooling system, reliability.

Disadvantages: Not convenient, crookedly made proprietary utility from palit.

Comment: An excellent video card that will not burn out, unlike MSiai and Gigabytes. I set up the operation of coolers from 38 degrees (on the Internet and the desktop does not rise more than 36, the fans are silent), there is no desire to heat up to auto operation)

alexander s. , 11/12/2019

Advantages: To begin with, this is already my third Palit card, before that there were 550ti and 760, and those cards still work in the computers of my friends, to whom I gave them, so I decided on the manufacturer a long time ago.
I took my 1070 at the beginning of 2017, with the expectation of a performance margin when playing in FullHD, everything suits me. The announcement of the 30th series is coming soon, but I’m not thinking about changing the map yet. By the way, these cards come with factory overclocking, so those who like to get the most for their money will be satisfied, if you wish, you can squeeze it to the full using the standard program, Thunder Master, everything is very simple there, you can figure it out in 5 minutes.
Performance is good even at the moment, few games drop below 45 at the worst moments. RDR2, Battlefield 5, Hell let loose (I recommend it to hardcore fans), Borderlands 3, everything flies, swims, explodes perfectly.
Cooling is simply top. I could not believe when I played not very heavy toys that the courier was on the map, the map was cooled in a passive mode! Now it’s probably not so surprising, but it seemed a miracle to me). In the active cooling mode, it is quite comfortable to play up to the power of the coolers at 70%, above that the noise from the video card already blocks the processor cooler and the PSU. But she tries not to gain such speed often, only sometimes turning on the turbo mode and cooling down, she switches back to a measured rumble.

Disadvantages: I connect a monitor and a TV to a computer and what I didn’t like exactly was one HDMI connector. I had to go for an adapter to the display port. But these are trifles.
You can also write down the noise of the cooling system at speeds closer to 100% power as a minus.

Comment: I am satisfied with the card, especially since I managed to buy it before the price increase. I don’t see much point in talking about the backplate (a steel plate for rigidity at the back of the card) and RGB backlighting, the plate is just needed for such a card, and I don’t play around with backlighting, for fans there is the ability to adjust the color, set the color change program even under load. But for me, the main thing is reliability and performance, and this card with such qualities is all right.

Nowaday l., 09/13/2019

Advantages: — Cooling system:
In FurMark under full load 65 degrees
— Silence
— Beautiful outwardly

Disadvantages: None

Comment: I thought between taking 1066 or adding and taking 1070ti, in the end I took the latter and did not regret it, for + 50% to the cost (30k instead of 20) received +50% to productivity, further according to this scheme it is no longer so profitable. 1070 makes no sense to take because. 1070 is about 30, 1070 is about 32, the difference between them is by no means 2k

Alexey F., 09/06/2019

Advantages: + Pulls all games at 144 fps on ultras (with i7 8700k, 16 gb, 144 hertz monitor)
+ Overclocked from the factory
+ Often palit SUPER jetstream is cheaper than usual
+ Cooling

Disadvantages: -Heats up to 73 in games and drops to 65 in the menu (average 70)

Comment: For some reason, suddenly everyone started drowning for burning that he was a topper, so I took it (I wanted to check, but the card LIKE is not bad)
Next time I’ll take an asus.

Mark S., 09/02/2019

Advantages: Excellent cooling system, quiet, insanely beautiful video card, I think that Palit did a very good job in the production of this video card 🙂

Disadvantages: It bends without a special holder, but these are trifles)

Comment: When you take this video card in your hands, you immediately understand that the product is of high quality, because a good device should weigh a LOT 😀
And such a weight is due to a huge radiator that is able to independently cool the video card without fans. Plus a metal backplate which is also involved in cooling.
Definitely the best price/performance ratio belongs to this card in the tenth GTX line 🙂

Alexey Shmurov, 01/14/2019

Advantages: + Silent operation (read the comment for details)
+ Good cooling (see comment)
+ Good price / performance ratio with a reserve for the future (for FullHD resolution). It is much more powerful than 1060 (which will not be enough in a couple of years), and not much weaker than 1080, which is significantly more expensive than
+ Good overclocking potential + cooling system has this. In overclocking, it overtakes the stock 1080.
+ Design, but everything is subjective here. I like her discreet but strict appearance. But someone will find the backlight boring.
+ Very well packaged: a thick layer of protective material + a bunch of film on the video card itself (by the way, it doesn’t peel off very well, but it’s much better than scratches/scuffs).

Disadvantages: — Dimensions and weight. The card is really big and heavy. It occupies almost 3 slots in height, and on my motherboard it simultaneously closes two of the six SATA hard drive connectors. The width is also not small — on my case I could not install support for a video card, since it is curved inside the case (see photo). The length is 285 mm, so you need to carefully choose the case, because. can rest against the basket for disks. The card is quite heavy and sags a bit. Therefore, I strongly advise you to put additional support (you can order it on Aliexpress).

Comment: A little more about the quiet operation. This video card is not completely silent throughout the fan range. But up to 40% of the rotation speed, the card is not audible AT ALL. You can notice the noise only after 50%, starting from 55% the sound of the work is compared with the sound of the system, and only after 60% the video card starts to noticeably make noise. BUT! Due to the good heat dissipation (massive tubes, a large number of thermal pads and a huge heatsink), the card cools well even without a fan. Automatically set so that the turntables work after 50 °, and work quietly at low speed. If desired, you can adjust the fan speed yourself in the Palit software.
Now as for the temperature: in idle 31-33°, in the browser (several open tabs + video in FullHD on YouTube) 36-38°, in games I reached 68° at ultra settings and 170+ FPS, but at the same time remained quiet. In AIDA 64, the vidyuha heated up to a maximum of 66 °.
The best 1070 Ti you can find on the market. And in general, Palit did a great job, all 1060/1070/1080 versions of JetStream and Super JetStream cards are quiet and have excellent cooling. If it’s the right size, feel free to take it.

93 285x133x58
mm Number of slots occupied 3 Additional information Boost video processor frequency — 1683 MHz; OC Mode: GPU frequency — 1708 MHz (Boost — 1797 MHz)

Manufacturers

  • ASUS1189
  • GIGABYTE1047
  • MSI955
  • Sapphire659
  • Palit655
  • PowerColor390
  • ZOTAC382
  • Inno3D278
  • XFX266
  • Gainward257
  • HIS204
  • EVGA164
  • PNY109
  • Leadtek83
  • KFA275
  • Sparkle72
  • Point of View56
  • HP41
  • VTX3D33
  • ECS27
  • Albatron27
  • Manli26
  • Colorful20
  • GALAXY20
  • Foxconn20
  • GeCube16
  • Chaintech23
  • Club-3D13
  • Forsa10
  • BFG10
  • AMD9
  • ASRock7
  • XpertVision6
  • GALAX6
  • FORCE3D6
  • AFOX5
  • OCZ2
  • ZOGIS2
  • Matrox2
  • Diablotek2
  • Sysconn2
  • Diamond2
  • VVIKOO2
  • Lenovo2
  • Jetway2
  • Biostar2
  • NVIDIA1

show more

Overview of Colorful iGame GTX 1070 Ti Vulcan AD

About the Chinese company

Colorful is the largest Chinese graphics accelerator manufacturer in Asia. In addition to video cards, Colorful produces motherboards, solid state drives, ATX power supplies, etc. The list of manufactured goods covers a huge range of PC components and peripherals.

The company is headquartered in Shenzhen (深圳市 or Guangdong) close to the border with Hong Kong. After all, sending goods from Hong Kong guarantees a refund of VAT (VAT).
In addition, Colorful founded Segotep, a computer case and peripherals company, and Colorfly, a tablet company.

If you look at Google in English, you will notice that from year to year, Colorful products, in particular video cards, slip more and more in reviews on Youtube, and this brand is gaining popularity outside of China.

Purchase

Anyone who has been visiting GroupB.ru for a long time must have seen the previous review of the Colorful GTX 970 TOP video card. This is one of the first Russian-language reviews of Colorful video cards. Up to this point, there were few reviews about this card, as well as about the manufacturer, on the Internet, but after «personal acquaintance» I can say with confidence that this manufacturer is no worse than famous brands, and this review confirms this.

A good friend of mine has long wanted to replace an old video card Asus 7790 and asked to find him a good replacement. It was on the eve of the Chinese sale on 11-11-2017 on Gearbest.

During the biggest sale of the year, prices for video cards in the Gearbest store went down and up as fast as the hryvnia against the US dollar. The pricing of the goods did not lend itself to a logical explanation.

For example, a GTX 1070 U-Top was sold at a regular price for $475.99, the next day the Flash price of the video card was $499.99, and the next day it dropped to $459.99$. The same thing happened with the Ati line, the RX580 was sold at a special price with a coupon for $329.99, and in a couple of days they could put the price of $259-289.99 minus everything that is. Therefore, having bought a product at a super discount, you might find that in a few days the product you bought without discounts can cost significantly less. This is fine. This is China!

Approximately the same situation happened with the GTX 1070Ti. The usual price for this video card in the store ranged from $550-$599 (at the same time, the Yeston GTX 1080 was sold for $59$9 for more than a month…), but during the sale days the price dropped to $535, and a few days later it broke through the $529.99 mark in the flash sale (which means that you can apply points + minus everything that is).

The interesting price of the Yeston RX580 was tempting, but it was decided to take the GTX 1070Ti Vulcan AD. Comparing prices in online stores (Hotline, F.ua, Rozetka) and on Gearbest, the choice of the store was obvious and, as they say in the Daily Sale, you have to take it, bira! Said, done, bought.

The GTX 1070 Ti series, in my opinion, is one of the most successful graphics cards from Nvidia in recent times. The 1070 Ti line was supposed to take an intermediate place between the GTX 1070 and GTX 1080, but it did not turn out at all as expected and planned. 93 Pascal Technician, Nm 16 Nm FINFET 16 Nm Finfet 16 Nm Finfet Number of transistors, million

7,20094 7 200

0900

0900

0900

0

0

0

0

0

0

0

9009EV MSC: Base Clock / Boost Clock 1607 /1 683 1607 /1 683 1607 /1 733 The number of shader 2 432

094

2000 (8000) 2000 (8000) 2500 (10 000) volume, MB 8 192 PCI 3. 0 x16 PCI Express 3.0 x16 PCI Express 3.0 x16 Performance 0003

  • GTX 1070 — if your budget is limited, but you do not want to buy a GTX 1060. The price of the video card varies between $399 — $499
  • GTX 1070 Ti — if you are ready to pay $60-100 extra and get a pre-top 10 series video card. The price of the video card varies within $520-590. For comparison, the estimated price of the GTX 1080 is $600-700.
  • GTX 1080 Ti is the top 10XX graphics card. The price varies between $799-$899.

*prices are before the miners bought all the cards, thus creating a shortage of cards in the market.

In simple terms, if you pay $40-100 more and buy a 1070Ti, you get almost the same performance as the GTX 1080, but for less money. So why pay more? The miners, who are also miners, fully appreciated the novelty and stopped buying the “big brother” in the person of 1080.

Delivery

I advise buyers from Ukraine to consider all options for purchase and delivery. It may be more profitable to purchase goods through an intermediary in order to avoid charging customs duties if the parcel is delayed by customs (DHL, TNT, Priority Line — Nova Poshta / UTEC. The last carrier is quite “loyal” about exceeding the cost of the parcel, but no one knows how long it will last knows).
Buyers from the Russian Federation with a limit of 1000 euros per month have nothing to worry about at all.

Packaging

Unfortunately, Gearbest does not provide adequate packaging from certain stocks. As long as the cost of the goods does not exceed $100-130, you can still turn a blind eye to this, but when buying an expensive product, I would like to get at least one layer of bubble wrap. Of course, the miracle did not happen, and the goods were sent wrapped in a regular 1mm bag. You can see the results in the photo.

Looking ahead, we can say that the product got off with a slight fright: a couple of scratches and a few shallow dents. It could have been worse. .. Fortunately, the video card manufacturer approached it more responsibly and provided good protection for the native packaging.

Appearance

Unlike the budget models of Colorful, the packaging of 1070Ti looks decent: thick, structured paper, excellent print quality. Despite the fact that this product is intended mainly for the local Chinese market, all the inscriptions on the packaging are in English. This, of course, does not affect the performance of the card, but it pleases the eye. On the back of the package, three top iGame series of video cards are listed:

  • iGame Kudan is the top version with hybrid cooling of the chip. Only available for Nvidia flagships (980/ti, 1080ti).
  • iGame Vulcan — with improved and significantly improved and modified conductive and convection cooling of the chip. It is worth noting that the Vulcan series is divided into three subspecies: Vulcan X, Vulcan X Top and Vulcan AD. The latest version is the most budget. A review of the Vulcan X Top version is coming soon.
  • iGame Neptun — water-cooled chip. Installed only on flagship video cards.

On the manufacturer’s website, a video card in the iGame line (there are also more budget lines) is presented in four versions:

U-top — the most budget version, Vulcan AD and X / X-Top. I must say right away that specifically for 1070Ti there is no point in overpaying for Vulcan X and X Top. In the new packages, an inscription appeared in large red hieroglyphs (does this mean that this inscription is not relevant for a European buyer? ?)

The weight and dimensions of the package are quite impressive. The total weight of the package is 1 kilogram and 795 grams, and the dimensions are 24x10x38cm.

The Chinese inscription on the side of the package reads: “Mining is not profitable!”. But seriously, the manufacturer warns that it removes the product from the guarantee if it was used for cryptocurrency mining. True, the manufacturer does not specify how exactly this can be found out, unless the buyer himself admits this.

To access the card, simply remove the outer packaging. The card is packaged in an additional dark cardboard box without any identifying marks or markings.

The contents of the black box are literally sealed in a very thick layer of polypropylene sealant. The thickness of the seal varies from 1.5 cm at the bottom and top of the box (with a velvet lining) to 5 cm in the middle.

At the bottom of the package, the manufacturer put two Molex — 8 pin adapters in case your connectors are occupied by another video card and there are no free 8 pin connectors in the power supply.

The adapter looks good enough, but in any case, before using, I advise you to check the contacts for crimping. And if possible, avoid using any adapters at all.

Complete set

Colorful iGame complete set differs from the usual one for the better and includes:

  • Video card
  • Installation and connection instructions0008
  • Two molex to 8 pin adapters
  • Gloves
  • Branded multitool
  • 10 tips of different shapes
  • Chinese bonus or discount card

English

User manual not only in Russian, but also in German. The most useful and interesting of the set is an adapter and a multitool.

It’s hard to call this multi-tool of high quality, but if the manufacturer adds it for free, then why not? It is quite enough for small simple jobs without much effort, and 10 pieces of cue balls for screwdrivers of different sizes and shapes will more than cover any dismantling and installation of computer components.

Card layout

Graphic cards of the iGame line can hardly be called compact. Compared with competitors MSI, Gigabyte, EVGA, Palit, the length of Colorfula video cards is 1.5-4 cm longer, which can be a problem when placing a video card in small cases. But this is the price for good and silent cooling.

It’s impossible to call this video card light or tiny. The weight of the card is 1 kilogram and 91 grams. Be sure to fasten the video card well during installation in order to avoid cracks in the PCB in the PCI slot.

Outputs 3x Displayport 1. 3/1.4
1x HDMI 2.0
1x Dual-Link-DVI Idle fan disable

Yes. At temperatures below 56-58 °C

The width of the card is 44mm. Officially, the manufacturer claims that the card occupies two slots, but in practice it turns out a little more, namely 3 slots, due to the embossed metal casing.

Video card comes in a fully sealed anti-static bag. All video outputs, and the card has as many as 4 of them, Sli and PCI contacts have silicone plugs that provide protection during transportation. On the rear backplate of the card there is a proprietary protective film, which must be removed when installing the video card.

In addition, the backplate has a sticker with the serial number of the card, batch number and a unique scratch code for technical assistance if necessary. On the English site, this function is activated, but does not work.

On the outside of the card there is a Turbo button (more on that below) for automatic overclocking, and 4 video outputs: 3 Display Port 1. 3/1.4, 1 DVI and one HDMI 2.0 output. This kit is enough to assemble a multi-monitor PC on one video card.

Unlike the reference design, Colorful has completely redesigned the board and power system. First of all, the changes affected the power supply of the card. Instead of the usual 8-pin connector, the Colorful GTX 1070Ti uses 8+8 pin power. Thus, when connected by two independent 8+8 pin power lines, the card can receive a total of up to 375 watts (150W+150W+75W PCI). This is almost twice as much as this model needs and more than it could physically take.

The video card power subsystem is based on the 8+2 phase scheme. Colorful is limited to 10 phases, unlike competitors who have 10+2 phases (Msi, EVGA). The manufacturer claims that it uses the proprietary development of the IPP power system — IGame Pure Power.

Backlight

The card has three LEDs, of which two are adjustable and one is not adjustable. The LED on the fan and the side logo can be turned off or the backlight change rate can be changed. But the inscription igame on the back of the textolite cannot be changed or disabled.

LED backlighting of the card is quite aggressive and bright, fortunately, it can be adjusted to your taste and color. In this regard, I really like the white, concise backlighting of cards from EVGA.

About Boost:

You can see that cards of reference design and non-reference design don’t differ in memory and chip frequency lately. This is due to the fact that NVIDIA has banned factory overclocking, so the clock speeds for all cards of the same series remain unchanged. Of course, this state of affairs did not suit card manufacturers much, and they found a way out in the form of using Boost. Formally, the base clock frequency remains the same, but with the help of a boost, you can carry out factory overclocking. The most common Boost methods are to increase the clock speed programmatically or by raising the TDP.

Colorful was able to bypass the limitation with the physical Turbo button on the back of the graphics card. On the one hand, overclocking the card can be done with a single click and avoid installing proprietary software, and on the other hand, every time you need to look for the Turbo button in order to enable or disable overclocking. Agree that this is not very convenient.

Overclocking:

The maximum factory frequency of the GeForce GTX 1070 Ti with boost is 1683 MHz. This is not the highest figure among competitors, but this result, as practice has shown, can be easily increased using manual overclocking in MSI Afterburner.

Overclocked and monitored using programs:

  • Msi AfterBurner 4.4.2.12
  • GPU-Z 2.7.0
  • Furmark 1.20.01

34% of the nominal 100%, unlike competitors who received a TDP cap of +20%. The Afterburnera interface allows you to move the slider up to + 34% Power Limit, but in reality the figures varied between 130-135% TDP. This is quite enough to pass the 2GHz mark and surpass the overclocking results of some competitors.

In the maximum overclock, the peak frequency of the GPU reached 2065.5-2075 MHz, while the memory clock frequency in this bundle was able to overcome the mark of 8706 MHz (possibly due to the fact that the memory was caught by Micron), VDDC 1.0430 V. Limit increase TDP not only entails a significant increase in the power consumption of the video card, namely 190-199 watts (+20-30 watts from nominal values ​​\u200b\u200bat 100% TDP), but also a significant temperature jump from 56 to 64-68 degrees Celsius. Unfortunately, these frequencies cannot be called stable. It was not possible to stabilize the result in all applications, namely in Furmarke.

We managed to fix a stable result at around 2025 MHz for the GPU and 8706 MHz for the memory. This is not the best result among competitors, but in general, the increase in frequency for the GPU was ~ + 20% and ~ + 9% for memory, which is quite good. Overclocking was carried out with Boost disabled due to the inability to stabilize the overclocking result with this parameter.

Cooling

The Chinese company did a great job on the cooling system, as a result of which the card turned out to be not only efficient, but also very quiet. As a passive cooling element, a dual-zone radiator is used, which is interconnected by 4 8-mm nickel-plated heat pipes and one 6-mm one.

The manufacturer did not fork out for an all-copper cooling system, as MSI did, and limited itself to an aluminum radiator divided into two cooling zones.

The main part of the heatsink received a soldered copper plate for better cooling of hot parts — the central processor and the memory around it. The second zone is designed for cooling power transistors through a thermal interface (namely, 2.5mm thermal pads).

On the back side, the card is protected by a metal backplate, which not only ensures reliable rigidity of the lightweight construction, but also partially participates in cooling.

The metal shroud on the front side of the board not only has a decorative function, but also acts as an airflow guide. The manufacturer equipped the card with three fans.

Of these, two received a diameter of 90mm, and one 80mm in the original i-Ring design — metal fins on the outside. In practice, the i-Ring technology is just a design move. Fans can be dismantled without voiding the warranty. To do this, just unscrew the three screws.

The fans have received the smart-stop function and turn on to actively cool the card only if the temperature of the card exceeds 62 degrees Celsius (according to the passport). In reality, the fans turn on at a chip temperature of 56-58 degrees Celsius.

Noise

When using a computer to surf the Internet, watch Youtube, movies, the user receives an absolutely silent video card that passively dissipates heat in the PC case. In games, fans are connected, which still work silently at 1200-1300 rpm (34% of the maximum fan speed) and keep the temperature of the card within 55-57 degrees Celsius. At 1500-1700 rpm (45%) in a closed case, the noise from the fans is still imperceptible. A distinct noise appears when overcoming the mark in 1800-1

  • World of Tanks
  • 3D Mark Time Spy

    In the popular 3D Mark Time Spy test, the video card scored 5938 points without overclocking and 6256 points with overclocking +205MHz / 300MHz from default values. Screen resolutions 2560×1080.

    Luxmark

    The LuxMark 3.0 test lets you test and demonstrate the capabilities of your GPU when performing complex computational calculations. In the lightest LuxBall HDR test, the Colorful card achieved 16037 points, in the Neumann test it scored 8256 points, and in the most difficult test the Hotel Lobby scored 3216 points. All results correspond to the default values ​​of the video card.

    With PowerLimit 100 overclocking, Core — +205MHz, Memory — +300MHz, the results are as follows:

    In the Luxball test — 17279 points, Neumann — 8813 points and in the Hotel lobby test 3607 points.

    Middle-earth: Shadow of War

    All settings are set to Ultra quality and Large Page technology is enabled. When this option is activated, the game starts to use larger amounts of memory, which should theoretically improve performance on a PC with more RAM. In practice, I did not notice much difference in speed.

    The minimum recorded FPS in the game was 62 fps, the average FPS is around 65-67 fps in combat and 80-110 fps out of combat.

    Fallout 4

    In Fallaut 4 at maximum graphics settings and 2K resolution, the average FPS at default frequencies was around 75-80 frames per second. In overclocking +205/305 MHz, the average FPS rose slightly, to 80-85 frames per second.

    World of Tanks Encore

    It makes no sense to test a video card in the old WoT client, because FPS in the game is limited at any settings and stays around 115-130 frames per second on powerful video cards, regardless of the power of the video card. In the new WoT Encore benchmark, built on a new engine, the situation is slightly different.

    A total of 4 tests were performed on ultra settings. Two tests at 3620×1527 resolution at stock and overclocked +205MHz/+300MHz, and two tests at 2560×1080 resolution stock and overclocked:

    The following results were obtained: for 2K resolution — 20138 points at factory frequencies and 22062 points with overclocking. When tested at a resolution of 3620 × 1527, it turned out to achieve 11741 points and 12635 points in stock and overclocking, respectively. For example, the Colorful GTX 970 only scored 13116 points at 2K, a 35% drop from the GTX 1070 Ti.

    World of Tanks — Beta Test

    As mentioned above, there is no point in testing the game in the old client, but now a public beta test of the new version is open, where you can test your video card in a real battle on the new engine. It is clear that this is just a beta release and a lot will still be optimized and improved, but in general you can get an approximate picture right now. Testing was carried out in 2K resolution on ultra settings:

    The average FPS in the game at stock settings is kept at 115-130 fps with rare exceptions when there is a subsidence of up to 80-90 fps when objects break (trees, buildings, etc. ). I assume this bug will be fixed soon.

    With OS, the results get a little better, but not much. The average FPS in the game has grown to 140-150 frames per second. All the same, the optimization of the game is not bad and the power of this video card is enough in abundance.

    The Witcher

    On ultra settings at 2560×1080 the average FPS in the game is around 77-85 fps. In the city, FPS sags to a minimum of 71-31 frames per second. In overclocking +205/305 MHz, the card gained an average of 4-7 FPS.

    Mining

    One of the fastest and easiest ways to determine the daily profit of the card for inexperienced miners is to install the NiceHash program and conduct testing. I didn’t have time to deal with wallets and mining principles, so I just ran the program without specifying a wallet in demo mode:

    As for experienced miners, they do not need special programs to determine profitability, but it is enough to know the card model, memory type and overclocking of the card, the algorithm used and the complexity of the network. And most of all in the map they are interested in cooling. The colder the card, the better the sleep at night ?

    According to Nicehash, the estimated daily income from one Colorful GTX 1070 Ti card is $2.97 (excluding electricity costs).

    As for mining on the pool in the Equihash algorithm, the miner used is EWBF 0.3.4b.

    • With Power Limite 100%, Core Clock + 240 MHz, Memory Clock +430 MHz, the card produced 513-520 Sol/s, the temperature of the card reached 59 degrees, the card consumption was 180W, the efficiency was 2.83 Sol/Watt.
    • With Power Limit 75%, Core Clock + 240 MHz, Memory Clock +430 MHz, the card produced 490-499 Sol / s, the temperature of the card reached 55 degrees, the consumption of the card dropped to 130-134W, the efficiency was 3.72 Sol / Watt.
    • With a Power Limit of 60%, Core Clock + 240 MHz, Memory Clock +430 MHz, the card produced 460 Sol/s, the temperature of the card reached 53 degrees, the card consumption dropped to 105-110W, the efficiency was 4. 3 Sol/Watt. The fan speed was 1250-1300 rpm.

    According to the reviews on the Internet, these are standard results for the GTX 1070 Ti at these parameters, but the temperature of the card really pleased. Still, Colorful made excellent cooling. When manually fixing the fan speed at 50% (1900 rpm), the temperature of the card dropped to 45 degrees Celsius.


    TOP-X Line vs. Vulcan AD Comparison

    Unlike last year’s GTX 970 Top-X, the GTX 1070 Ti Vulcan AD does not have an additional heatsink, but instead has a 2 cm longer main heatsink. the area of ​​​​the main radiator more than compensates for the lack of an additional one. The Vulcan AD uses larger fans to improve efficiency and reduce noise.

    The rear backplate has also been changed. Instead of an all-metal perforated backplate, a lighter backplate with decorative cutouts is used. This not only reduces the weight of the card, but also minimizes heat buildup on the back of the PCB. The photo clearly shows the difference in the length of the PCB and heatsink of the GTX 970 and 1070Ti.

    Colorful iGame Zone II

    iGame Zone II is the official app of Colorful. With it, you can not only change the color of the LED backlight, but also monitor and overclock the card. The app is available in English and Chinese. Unfortunately, it is difficult to call it convenient to use. The only useful function, in my opinion, is turning off or modifying the LED backlight. For OC or monitoring, I advise you to use the Msi Afterburner program, which does an excellent job of this.

    The application can be downloaded from the supplied CD or from the official site. I would like to note that the English version of the site is not updated and is currently abandoned by the manufacturer. For up-to-date information, I advise you to use the Chinese version of the site or simply follow the link — iGameZoneII-2.1-Installer. At the time of this writing, the current version of iGame Zone II ver 2. 1.

    Guarantee

    When buying goods on the Internet, you should really be aware of the possible risks and upcoming costs in the event of a warranty event. But if this does not scare you, and the lower price compared to offline stores is really a significant advantage, you can safely order this product online. Most importantly, do not choose one-day sellers and pay for the goods through Paypal. The difference between online and local prices can reach 20-40%.

    If in doubt, it’s better to pay a little more and get the product from a local store with a guarantee.

    Of course, the Gearbest store is not an EVGA service center (which can replace a broken video card with a new one after the warranty period has expired), but all warranty cases for the return and exchange of goods in the Gearbest store took place without any problems (apart from a long correspondence with managers).

    Conclusion

    The Colorful iGame GTX 1070 Ti Vulcan AD is a great silent video card that currently delivers a comfortable FPS => 60 fps in any game on ultra setting in 2K resolution. The card failed to break the overclocking record, but it demonstrated excellent cooling and quiet operation, which is much more important in everyday use. A nice bonus in the form of a branded multi-tool is always better than its absence. And of course, do not believe the reviews on the Internet about the low quality of Chinese video cards. Colorful has done a good job. Therefore, if you are satisfied with the price, then I safely recommend this video card for purchase.

    I advise you to view both the Russian version and the global version of the Gearbest website. Sometimes the same product can cost 5-30% less.

    video cards on www.ru.gearbest.com
    video cards on www.gearbest.com

    pluses:

    • Excellent assembly quality
    • Sundant work 9000
    • Multitool screwdriver
    • Backplate
    • Reliable packaging

    Cons:

    • No local warranty when buying online (there is a store warranty). But this applies to all goods when buying online.
    • Disgusting package.

    what video cards can be combined in SLI

    After the guide on connecting two AMD Radeon video cards in Crossfire, Nvidia’s turn came. Its GeForce GPUs are just as popular with gamers as their competitors. Both companies go hand in hand in the market, offering customers solutions that are similar in terms of performance and price. Therefore, it would be unfair to devote material to building a CrossFire configuration, but to bypass the similar capabilities of Nvidia products.

    Read also: How to combine video cards in CrossFire

    A bit of history

    1998 can be considered the beginning of the SLI era. Then the company 3dfx for the first time managed to realize the possibility of combining several video cards to solve one problem. However, the development of the AGP interface slowed down developments in this direction, since all motherboards of that time were equipped with only one slot for a video card.

    SLI from 3DFX — the «grandfather» of modern technology

    After 3dfx was bought by Nvidia in 2001, all developments in this direction waited in the wings, which came only in 2004. It was then, in the GeForce 6000 series (the first video cards designed specifically for the latest PCI-Express interface at that time), that the existing developments were improved and introduced into mass consumption products.

    SLI of two GeForce 6600GT

    At first, it was possible to combine two GeForce 6600 or 6800 video cards, with the release of the 7000 series (which introduced the first full-fledged dual-processor board from Nvidia, 7900GX2) it became possible to build a four-processor configuration (from 2 cards), and later it became possible to combine 3 or 4 separate GPUs.

    How to combine video cards in SLI: requirements

    As with CrossFire, it is not enough to buy two Nvidia video cards to configure them in SLI. There are a number of computer requirements that must be met to ensure the normal functioning of the bundle.

    Which video cards can be combined in SLI

    Connecting two video cards with an SLI bridge is possible only if this bridge has an interface on the board. You can also try to combine them with software tools, but in this case you can’t do without “dances with a tambourine”. And it makes no sense to build a tandem of two GT610 or GT720. One card, the performance of which will be 2 or 3 times faster than that of a similar bundle, will cost less than a set of a pair of office cards and a compatible motherboard. That is, the lack of an SLI interface on the younger representatives of graphic accelerators is not at all caused by the manufacturer’s greed. Nobody puts bridges, because it will make the map more expensive, but there will be no sense from them. Thus, the connection of two SLI video cards is possible for models of the middle and top class. These include GPUs whose second digit is 5 or higher (GTX5 5 0Ti, GTX9 6 0, GTX6 7 0, GTX7 8 0, etc. ).

    GeForce GT 720 does not have an SLI bridge

    Before connecting two video cards to SLI, you should make sure that they are built on the same version of the graphics processor. For example, the GeForce GTX650 and GTX650Ti, despite the similarity of names, operate on the basis of completely different GPUs and therefore cannot work in tandem.

    Is there any practical use for SLI?

    Before you combine video cards in SLI, it is advisable to get acquainted with the experience of using such configurations by other gamers and study the specifications of their cards, as well as the characteristics of more powerful solutions in the line. Often, neither in terms of savings, nor in terms of performance, a two-card configuration gives a win. For example, two GTX950 in SLI show results comparable to a single GTX970. The difference in price (about $200 and $400, respectively) of the cards themselves is justified, but if you take into account the additional costs for a powerful PSU, a two-slot motherboard, a high-quality and well-ventilated case, it looks doubtful.

    The situation is completely different if the connection of two SLI video cards is an integral part of the upgrade procedure for an existing PC purchased a couple of years ago. Cards of the GTX650Ti or GTX750 level can still be found on sale at a reasonable price (the difference with the new models is approximately equivalent to the differences in speed), and technical progress for 3 years has not presented anything revolutionary for video cards (except for the HBM memory introduced by AMD, but Nvidia is until it touches). Therefore, adding another GPU is a completely rational step for such players.

    SLI: connecting video cards

    If the computer meets the requirements for creating an SLI configuration, a suitable second video card has been purchased — you can proceed with the assembly. After turning off the PC, remove the cover of the system unit, install the second board in the appropriate slot, connect an additional power cable to it (if required) and connect the two cards with the bridge that comes with the kit. The hardware connection of two video cards in SLI is now complete and you can proceed to the software setup.

    Power cables connected to the SLI bundle

    Connecting two SLI video cards in Windows

    In order for the dual GPU bundle to function properly, you need to install Windows Vista or later versions (7, 8, 8.1 or 10) on your PC. It is also recommended to download the latest graphics card driver from the Nvidia website. After that, you can proceed to the setting.

    After applying the settings, the bundle is ready for use. You may need to set specific settings in the Software Settings submenu to properly configure SLI for some games. But, as a rule, most modern software does not need this.

    ROG-STRIX-GTX1070TI-A8G-GAMING | ROG Strix | Gaming Graphics Cards|ROG

    Outsmarting the competition

    The ROG Strix GTX 1070 Ti graphics card is a top-of-the-line gaming card packed with many exclusive ASUS technologies. The cooling system used on it boasts high efficiency due to dust-proof fans with optimized impeller geometry, and the ability to connect 4-pin case fans will ensure the most comfortable temperature conditions for such a powerful device. The Aura Sync lighting system helps enhance your PC design with original lighting effects, while VR-compatible HDMI ports give gamers an immersive virtual reality experience. The ROG Strix GTX 1070 Ti comes with GPU Tweak II (for tweaking and monitoring graphics card settings) and XSplit Gamecaster (for real-time recording and streaming of gameplay).

    High Efficiency Cooling

    Larger Radiator Surface

    Cooler and Quieter

    The new ROG Strix series graphics cards feature a 2.5-slot thick form factor that allows for a 40% larger heatsink surface compared to the standard 2 form factor slot. The increased heat dissipation area contributes to improved cooling of the device.

    * Image is for illustration purposes only.

    MaxContact 9 technology0003

    Improved heat dissipation of the graphics chip

    MaxContact is the name of a new technology for manufacturing the base of the copper heatsink that is mounted on the GPU. With a smoother surface than conventional heatsinks, this heatsink provides a larger contact area and therefore better heat transfer.

    Optimized Fans

    Enhanced Airflow and Static Pressure

    The high quality fans with optimized impeller geometry included in this graphics card’s cooling system increase airflow and increase static pressure compared to the reference model cooler. At the same time, they produce three times less noise.

    Silent operation

    Enjoy the silence!

    At low and medium load levels, when the temperature of the GPU remains below the set level*, the cooler will cool the video card in a passive mode, that is, with zero noise from the fans.

    *For ROG Strix GeForce GTX 1070 Ti, the temperature threshold is 55°.

    IP5X Certified

    Extended Lifespan

    The fans used on ROG Strix series graphics cards are IP5X dustproof. This means their durability, which in turn increases the life of the entire device.

    ASUS FanConnect II technology

    Connecting case fans

    ASUS FanConnect II technology means that the graphics card has a pair of 4-pin connectors for connecting PWM or voltage controlled case fans. Changing their speed is carried out based on the temperature of the central and graphics processor — automatically. In addition, the user is given the opportunity to flexibly adjust the adjustment algorithm manually.

    * Image is for illustration purposes only. The actual location of the components may vary.

    The GPU Tweak II utility allows you to use the following FanConnect II modes:

    Auto mode:
    Fans are adjusted according to a preset algorithm based on the temperature of the GPU.

    Manual setting:
    Set a fixed speed for connected fans.

    User mode:
    The user can select which component (GPU or CPU) to adjust the speed of the connected fans based on the temperature of which, as well as set the algorithm for changing it in order to achieve the optimal balance between cooling efficiency and noise level.

    Quality and Reliability

    Auto-Extreme Technology

    Automated Manufacturing

    A fully automated manufacturing process (Auto-Extreme Technology) contributes to the high quality of the finished device, meeting more stringent environmental regulations by eliminating harmful chemicals and reducing energy consumption by 50% .

    Fully automated
    no human error

    Overclocking stability

    Strict quality control

    Innovative technology

    Smooth PCB back

    Flux-free manufacturing

    Super Alloy Power II 7-Phase Power System

    Selected Components

    Modern ASUS graphics cards use selected components (Super Alloy Power II technology) for superior power efficiency, cooler operating temperatures and enhanced performance.

    Personalization

    Aura Sync Lighting

    Outshining the competition

    The stylish Aura Sync LED lighting featured on ROG Strix series graphics cards offers millions of color combinations combined with six mesmerizing visual effects. In addition, by connecting the video card to the appropriate ASUS motherboard, you can synchronize their backlighting with each other.

    Experience Aura
    Color and brightness

    Special effects

    Static

    Steady light

    Pulsation

    Fade on and off

    Strobe

    Backlight turns on with short flashes

    Cycle

    Cycle through different colors

    Music

    Pulsation to the rhythm of the melody being played

    Temperature

    Color change depending on processor temperature

    Immersive gaming

    VR ready HDMI connectors

    Experience another reality

    ROG Strix graphics cards feature two HDMI connectors, allowing you to connect both a display and a VR system at the same time.

    ASUS Beyond VR Ready: Expand your PC experience.

    The perfect image

    The perfect combination of monitor and graphics card

    ASUS Swift series gaming monitors feature NVIDIA G-SYNC technology, which synchronizes the screen refresh rate with the frame rate of the GeForce GTX GPU. G-SYNC eliminates annoying frame tearing and reduces display lag, resulting in both better picture quality and better game responsiveness. Swift monitors and Strix graphics cards are the perfect combination for a gaming PC!

    Learn more about ASUS gaming monitors.

    More speed!

    Speed ​​up your SLI link with the ROG SLI HB Bridge

    The ROG SLI HB Bridge is designed to combine two graphics cards occupying 3 or 4 slot space into a single graphics subsystem that will have the increased performance required for maximum comfort in modern computer games at the highest picture quality settings. The bridge is equipped with the Aura Sync lighting system, which can output many different colors and synchronize with the lighting of other ASUS devices.

    Learn more >

    Full control

    GPU Tweak II utility with XSplit Gamecaster

    For flexible graphics card customization

    Modern ASUS graphics cards are compatible with the exclusive GPU Tweak II utility, which allows you to take full control over your computer’s graphics subsystem. For example, the new Gaming Booster feature allows you to instantly allocate all available computing resources to a 3D application to ensure maximum performance.

    Learn more >

    Gaming Booster

    One-Click Optimization

    Visual Effects:

    Improve performance by turning off visual effects in the Windows interface.

    System Services:

    Automatic or manual shutdown of Windows services and processes.

    Memory defragmentation:

    Free up system memory without closing running processes.

    XSplit Gamecaster 9 Utility0003

    Game Casting over the Internet

    The software bundled with this video card includes a 1-year license for XSplit Gamecaster, a handy utility for broadcasting and recording gameplay (the cost of such a license, purchased separately, is $99).