GeForce GTX 950 vs GeForce GTX 960 Graphics cards Comparison
If you are going to buy a new graphics card and are choosing between GeForce GTX 950 and GeForce GTX 960, there are a couple of things to consider. Cards with more VRAM in general perform better and allow you to play on higher graphics settings. Size also makes a difference. A model with a large heatsink can occupy up to three expansion slots on a motherboard. Be sure you have enough room in your PC case. When comparing GPUs with different architectures, more processing cores and even higher TFLOPS will not always translate to better performance. To help you decide which GPU you need, we have measured frame rates in a number of popular games. For more on how the GeForce GTX 950 stacks up against GeForce GTX 960, check out specs charts below.
GeForce GTX 950
Check Price
GeForce GTX 960
Check Price
Main Specs
GeForce GTX 950 | GeForce GTX 960 | |
Power consumption (TDP) | 90 Watt | 120 Watt |
Interface | PCIe 3. 0 x16 | PCIe 3.0 x16 |
Supplementary power connectors | 1x 6-pins | 1x 6-pins |
Memory type | GDDR5 | GDDR5 |
Maximum RAM amount | 2 GB | 4 GB |
Display Connectors | 1x DVI, 1x HDMI, 3x DisplayPort | 1x DVI, 1x HDMI, 3x DisplayPort |
Recommended system power (PSU) | 350 Watt | 400 Watt |
Check Price |
Check Price |
- GeForce GTX 960 has 33% more power consumption, than GeForce GTX 950.
- Both video cards are using PCIe 3.0 x16 interface connection to a motherboard.
- GeForce GTX 960 has 2 GB more memory, than GeForce GTX 950.
- Both cards are used in Desktops.
- GeForce GTX 950 and GeForce GTX 960 are build with Maxwell architecture.
- Core clock speed of GeForce GTX 960 is 103 MHz higher, than GeForce GTX 950.
- GeForce GTX 950 and GeForce GTX 960 are manufactured by 28 nm process technology.
- GeForce GTX 960 is 2 mm longer, than GeForce GTX 950.
- Memory clock speed of GeForce GTX 960 is 1 MHz higher, than GeForce GTX 950.
Game benchmarks
Assassin’s Creed OdysseyBattlefield 5Call of Duty: WarzoneCounter-Strike: Global OffensiveCyberpunk 2077Dota 2Far Cry 5FortniteForza Horizon 4Grand Theft Auto VMetro ExodusMinecraftPLAYERUNKNOWN’S BATTLEGROUNDSRed Dead Redemption 2The Witcher 3: Wild HuntWorld of Tanks | ||
high / 1080p | 35−40 | 35−40 |
ultra / 1080p | 21−24 | 21−24 |
QHD / 1440p | 16−18 | 16−18 |
4K / 2160p | 10−11 | 10−11 |
low / 720p | 60−65 | 60−65 |
medium / 1080p | 40−45 | 40−45 |
GeForce GTX 950 and GeForce GTX 960 have the same average FPS in Assassin’s Creed Odyssey. | ||
high / 1080p | 55−60 | 55−60 |
ultra / 1080p | 45−50 | 45−50 |
QHD / 1440p | 35−40 | 35−40 |
4K / 2160p | 18−20 | 18−20 |
low / 720p | 100−110 | 100−110 |
medium / 1080p | 60−65 | 60−65 |
GeForce GTX 950 and GeForce GTX 960 have the same average FPS in Battlefield 5. | ||
low / 768p | 50−55 | 50−55 |
QHD / 1440p | 0−1 | 0−1 |
GeForce GTX 950 and GeForce GTX 960 have the same average FPS in Call of Duty: Warzone. | ||
low / 768p | 250−260 | 250−260 |
medium / 768p | 220−230 | 220−230 |
ultra / 1080p | 180−190 | 180−190 |
QHD / 1440p | 110−120 | 110−120 |
4K / 2160p | 70−75 | 70−75 |
high / 768p | 210−220 | 210−220 |
GeForce GTX 950 and GeForce GTX 960 have the same average FPS in Counter-Strike: Global Offensive. | ||
low / 768p | 60−65 | 60−65 |
medium / 1080p | 55−60 | 55−60 |
GeForce GTX 950 and GeForce GTX 960 have the same average FPS in Cyberpunk 2077. | ||
low / 768p | 120−130 | 120−130 |
medium / 768p | 110−120 | 110−120 |
ultra / 1080p | 100−110 | 100−110 |
GeForce GTX 950 and GeForce GTX 960 have the same average FPS in Dota 2. | ||
high / 1080p | 45−50 | 45−50 |
ultra / 1080p | 40−45 | 40−45 |
QHD / 1440p | 27−30 | 27−30 |
4K / 2160p | 14−16 | 14−16 |
low / 720p | 80−85 | 80−85 |
medium / 1080p | 45−50 | 45−50 |
GeForce GTX 950 and GeForce GTX 960 have the same average FPS in Far Cry 5. | ||
high / 1080p | 60−65 | 60−65 |
ultra / 1080p | 45−50 | 45−50 |
QHD / 1440p | 27−30 | 27−30 |
4K / 2160p | 27−30 | 27−30 |
low / 720p | 180−190 | 180−190 |
medium / 1080p | 110−120 | 110−120 |
GeForce GTX 950 and GeForce GTX 960 have the same average FPS in Fortnite. | ||
high / 1080p | 60−65 | 60−65 |
ultra / 1080p | 45−50 | 45−50 |
QHD / 1440p | 30−35 | 30−35 |
4K / 2160p | 24−27 | 24−27 |
low / 720p | 100−110 | 100−110 |
medium / 1080p | 65−70 | 65−70 |
GeForce GTX 950 and GeForce GTX 960 have the same average FPS in Forza Horizon 4. | ||
low / 768p | 140−150 | 140−150 |
medium / 768p | 120−130 | 120−130 |
high / 1080p | 70−75 | 70−75 |
ultra / 1080p | 30−35 | 30−35 |
QHD / 1440p | 21−24 | 21−24 |
GeForce GTX 950 and GeForce GTX 960 have the same average FPS in Grand Theft Auto V. | ||
high / 1080p | 24−27 | 24−27 |
ultra / 1080p | 20−22 | 20−22 |
QHD / 1440p | 16−18 | 16−18 |
4K / 2160p | 8−9 | 8−9 |
low / 720p | 65−70 | 65−70 |
medium / 1080p | 30−35 | 30−35 |
GeForce GTX 950 and GeForce GTX 960 have the same average FPS in Metro Exodus. | ||
low / 768p | 130−140 | 130−140 |
medium / 1080p | 120−130 | 120−130 |
GeForce GTX 950 and GeForce GTX 960 have the same average FPS in Minecraft. | ||
ultra / 1080p | 14−16 | 14−16 |
low / 720p | 100−110 | 100−110 |
medium / 1080p | 18−20 | 18−20 |
GeForce GTX 950 and GeForce GTX 960 have the same average FPS in PLAYERUNKNOWN’S BATTLEGROUNDS. | ||
high / 1080p | 24−27 | 24−27 |
ultra / 1080p | 16−18 | 16−18 |
QHD / 1440p | 10−11 | 10−11 |
4K / 2160p | 7−8 | 7−8 |
low / 720p | 65−70 | 65−70 |
medium / 1080p | 35−40 | 35−40 |
GeForce GTX 950 and GeForce GTX 960 have the same average FPS in Red Dead Redemption 2. | ||
low / 768p | 130−140 | 130−140 |
medium / 768p | 85−90 | 85−90 |
high / 1080p | 45−50 | 45−50 |
ultra / 1080p | 24−27 | 24−27 |
4K / 2160p | 16−18 | 16−18 |
GeForce GTX 950 and GeForce GTX 960 have the same average FPS in The Witcher 3: Wild Hunt. | ||
low / 768p | 90−95 | 90−95 |
medium / 768p | 60−65 | 60−65 |
ultra / 1080p | 50−55 | 50−55 |
high / 768p | 60−65 | 60−65 |
GeForce GTX 950 and GeForce GTX 960 have the same average FPS in World of Tanks. |
Full Specs
GeForce GTX 950 | GeForce GTX 960 | |
Architecture | Maxwell | Maxwell |
Code name | GM206 | GM206 |
Type | Desktop | Desktop |
Release date | 20 August 2015 | 22 January 2015 |
Pipelines | 768 | 1024 |
Core clock speed | 1024 MHz | 1127 MHz |
Boost Clock | 1188 MHz | 1178 MHz |
Transistor count | 2,940 million | 2,940 million |
Manufacturing process technology | 28 nm | 28 nm |
Texture fill rate | 49. 2 billion/sec | 72 billion/sec |
Floating-point performance | 1,825 gflops | 2,413 gflops |
Length | 7.938″ (20.2 cm) | 9.5″ (24.1 cm) |
Memory bus width | 128 Bit | 128 Bit |
Memory clock speed | 6.6 GB/s | 7.0 GB/s |
Memory bandwidth | 105.6 GB/s | 112 GB/s |
Shared memory | — | — |
G-SYNC support | + | + |
DirectX | 12 (12_1) | 12 (12_1) |
Shader Model | 6.4 | 6.4 |
OpenGL | 4.5 | 4.4 |
OpenCL | 1.2 | 1. 2 |
Vulkan | 1.1.126 | 1.1.126 |
CUDA | + | + |
Monero / XMR (CryptoNight) | 0.27 kh/s | |
CUDA cores | 768 | 1024 |
Bus support | PCI Express 3.0 | PCI Express 3.0 |
Height | 4.376″ (11.1 cm) | 4.376″ (11.1 cm) |
SLI options | + | + |
Multi monitor support | 4 displays | 4 displays |
HDCP | + | + |
Maximum VGA resolution | 2048×1536 | 2048×1536 |
Audio input for HDMI | Internal | Internal |
Bitcoin / BTC (SHA256) | 233 Mh/s | 318 Mh/s |
Decred / DCR (Decred) | 0. 92 Gh/s | |
Ethereum / ETH (DaggerHashimoto) | 9.97 Mh/s | 8 Mh/s |
Zcash / ZEC (Equihash) | 141.47 Sol/s | |
GameStream | + | + |
GeForce ShadowPlay | + | + |
GPU Boost | 2.0 | 2.0 |
GameWorks | + | + |
Check Price |
Check Price |
Similar compares
- GeForce GTX 950 vs Radeon RX 560X mobile
- GeForce GTX 950 vs Tiger Lake U Xe Graphics G7
- GeForce GTX 960 vs Radeon RX 560X mobile
- GeForce GTX 960 vs Tiger Lake U Xe Graphics G7
- GeForce GTX 950 vs GeForce GTX 1650 Ti Max Q
- GeForce GTX 950 vs Quadro K5200
- GeForce GTX 960 vs GeForce GTX 1650 Ti Max Q
- GeForce GTX 960 vs Quadro K5200
NVIDIA GeForce GTX 950 vs NVIDIA GeForce GTX 960
The following benchmarks stem from our benchmarks of review laptops. The performance depends on the used graphics memory, clock rate, processor, system settings, drivers, and operating systems. So the results don’t have to be representative for all laptops with this GPU. For detailed information on the benchmark results, click on the fps number.
For more games that might be playable and a list of all games and graphics cards visit our Gaming List
log 12. 22:58:35
#0 checking url part for id 6461 +0s … 0s
#1 checking url part for id 6311 +0s … 0s
#2 not redirecting to Ajax server +0s … 0s
#3 did not recreate cache, as it is less than 5 days old! Created at Mon, 12 Sep 2022 17:26:57 +0200 +0s … 0s
#4 linkCache_getLink using $NBC_LINKCACHE +0.045s … 0.046s
#5 linkCache_getLink using $NBC_LINKCACHE +0.004s … 0.05s
#6 linkCache_getLink using $NBC_LINKCACHE +0s … 0.05s
#7 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.05s
#8 linkCache_getLink using $NBC_LINKCACHE +0s … 0.05s
#9 linkCache_getLink using $NBC_LINKCACHE +0s … 0.05s
#10 linkCache_getLink using $NBC_LINKCACHE +0s … 0.05s
#11 composed specs +0s … 0.05s
#12 did output specs +0s … 0.05s
#13 start showIntegratedCPUs +0s … 0.05s
#14 linkCache_getLink no uid found +0.032s … 0.082s
#15 getting avg benchmarks for device 6461 +0.002s … 0.084s
#16 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.084s
#17 got single benchmarks 6461 +0.006s … 0.09s
#18 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.093s
#19 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.095s
#20 getting avg benchmarks for device 6311 +0s … 0.095s
#21 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.096s
#22 got single benchmarks 6311 +0.006s … 0.102s
#23 got avg benchmarks for devices +0s . .. 0.102s
#24 linkCache_getLink no uid found +0s … 0.102s
#25 linkCache_getLink no uid found +0s … 0.103s
#26 linkCache_getLink no uid found +0s … 0.103s
#27 linkCache_getLink no uid found +0s … 0.103s
#28 linkCache_getLink no uid found +0s … 0.104s
#29 linkCache_getLink no uid found +0s … 0.104s
#30 linkCache_getLink using $NBC_LINKCACHE +0s … 0.104s
#31 linkCache_getLink no uid found +0s … 0.105s
#32 linkCache_getLink no uid found +0s … 0.105s
#33 linkCache_getLink using $NBC_LINKCACHE +0s … 0.105s
#34 linkCache_getLink no uid found +0s … 0.105s
#35 linkCache_getLink no uid found +0s … 0.105s
#36 linkCache_getLink no uid found +0s … 0.105s
#37 linkCache_getLink no uid found +0s … 0.106s
#38 linkCache_getLink using $NBC_LINKCACHE +0s … 0.106s
#39 linkCache_getLink no uid found +0s . .. 0.106s
#40 linkCache_getLink using $NBC_LINKCACHE +0s … 0.107s
#41 linkCache_getLink no uid found +0s … 0.107s
#42 linkCache_getLink no uid found +0.001s … 0.107s
#43 linkCache_getLink no uid found +0s … 0.107s
#44 linkCache_getLink using $NBC_LINKCACHE +0s … 0.107s
#45 linkCache_getLink no uid found +0s … 0.107s
#46 linkCache_getLink no uid found +0s … 0.108s
#47 linkCache_getLink no uid found +0s … 0.108s
#48 linkCache_getLink no uid found +0s … 0.108s
#49 linkCache_getLink using $NBC_LINKCACHE +0s … 0.108s
#50 linkCache_getLink no uid found +0s … 0.109s
#51 linkCache_getLink no uid found +0s … 0.109s
#52 linkCache_getLink no uid found +0s … 0.11s
#53 linkCache_getLink no uid found +0s … 0.11s
#54 linkCache_getLink using $NBC_LINKCACHE +0s … 0.11s
#55 linkCache_getLink no uid found +0s . .. 0.111s
#56 linkCache_getLink using $NBC_LINKCACHE +0s … 0.111s
#57 linkCache_getLink no uid found +0s … 0.111s
#58 linkCache_getLink using $NBC_LINKCACHE +0s … 0.112s
#59 linkCache_getLink no uid found +0s … 0.112s
#60 linkCache_getLink using $NBC_LINKCACHE +0s … 0.112s
#61 linkCache_getLink no uid found +0s … 0.113s
#62 linkCache_getLink using $NBC_LINKCACHE +0s … 0.113s
#63 linkCache_getLink no uid found +0s … 0.113s
#64 linkCache_getLink using $NBC_LINKCACHE +0s … 0.114s
#65 linkCache_getLink no uid found +0s … 0.114s
#66 linkCache_getLink using $NBC_LINKCACHE +0s … 0.114s
#67 linkCache_getLink no uid found +0s … 0.115s
#68 linkCache_getLink using $NBC_LINKCACHE +0s … 0.115s
#69 linkCache_getLink no uid found +0s … 0.115s
#70 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.115s
#71 linkCache_getLink no uid found +0s … 0.116s
#72 linkCache_getLink using $NBC_LINKCACHE +0s … 0.116s
#73 linkCache_getLink no uid found +0s … 0.116s
#74 linkCache_getLink no uid found +0s … 0.117s
#75 linkCache_getLink using $NBC_LINKCACHE +0s … 0.117s
#76 linkCache_getLink no uid found +0s … 0.117s
#77 linkCache_getLink no uid found +0s … 0.117s
#78 linkCache_getLink no uid found +0s … 0.118s
#79 linkCache_getLink no uid found +0s … 0.118s
#80 linkCache_getLink no uid found +0s … 0.119s
#81 linkCache_getLink no uid found +0s … 0.119s
#82 linkCache_getLink no uid found +0s … 0.119s
#83 min, max, avg, median took s +0s … 0.12s
#84 before gaming benchmark output +0s … 0.12s
#85 Got 384 rows for game benchmarks. +0.012s … 0.132s
#86 composed SQL query for gamebenchmarks +0s . .. 0.132s
#87 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#88 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#89 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#90 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#91 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#92 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#93 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#94 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#95 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#96 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#97 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#98 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#99 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#101 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.132s
#102 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#104 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#105 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#107 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#110 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#111 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#112 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#113 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#114 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#115 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.132s
#116 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#123 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#124 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#125 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#126 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#127 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#128 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#129 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.132s
#130 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.132s
#133 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#134 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#137 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#138 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#139 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#140 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#141 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#143 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.133s
#144 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#145 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#146 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#147 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#148 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#149 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#150 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#151 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#152 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#153 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#154 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#155 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#156 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#157 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.133s
#158 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#160 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#161 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#162 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#163 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#164 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#165 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#166 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#167 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#168 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#169 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#171 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.133s
#172 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#173 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#174 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#175 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#176 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#179 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#180 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#181 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#182 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#183 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#184 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#185 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.133s
#186 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#187 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#188 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#189 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#191 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#192 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#193 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#194 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#195 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#196 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#197 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#198 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#199 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.133s
#200 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#201 linkCache_getLink using $NBC_LINKCACHE +0s … 0.133s
#202 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#203 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#204 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#205 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#206 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#207 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#208 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#209 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#210 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#211 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#212 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#213 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.134s
#214 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#215 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#216 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#217 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#218 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#219 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#220 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#221 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#222 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#223 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#224 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#225 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#226 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#227 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.134s
#228 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#229 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#230 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#231 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#232 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#233 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#234 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#235 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#236 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#237 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#238 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#239 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#240 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#241 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.134s
#242 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#243 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#244 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#245 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#246 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#247 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#248 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#249 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#250 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#251 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#252 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#253 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#254 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#255 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.134s
#256 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#257 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#258 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#259 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#260 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#261 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#262 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#263 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#264 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#265 linkCache_getLink using $NBC_LINKCACHE +0s … 0.134s
#266 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#267 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#268 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#269 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.135s
#270 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#271 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#272 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#273 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#274 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#275 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#276 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#277 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#278 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#279 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#280 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#281 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#282 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#283 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.135s
#284 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#285 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#286 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#287 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#288 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#289 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#290 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#291 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#292 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#293 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#294 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#295 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#296 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#297 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.135s
#298 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#299 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#300 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#301 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#302 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#303 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#304 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#305 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#306 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#307 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#308 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#309 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#310 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#311 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.135s
#312 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#313 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#314 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#315 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#316 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#317 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#318 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#319 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#320 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#321 linkCache_getLink using $NBC_LINKCACHE +0s … 0.135s
#322 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#323 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#324 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#325 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.136s
#326 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#327 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#328 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#329 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#330 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#331 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#332 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#333 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#334 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#335 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#336 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#337 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#338 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#339 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.136s
#340 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#341 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#342 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#343 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#344 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#345 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#346 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#347 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#348 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#349 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#350 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#351 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#352 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#353 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.136s
#354 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#355 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#356 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#357 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#358 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#359 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#360 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#361 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#362 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#363 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#364 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#365 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#366 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#367 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.136s
#368 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#369 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#370 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#371 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#372 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#373 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#374 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#375 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#376 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#377 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#378 linkCache_getLink using $NBC_LINKCACHE +0s … 0.136s
#379 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#380 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#381 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.137s
#382 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#383 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#384 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#385 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#386 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#387 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#388 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#389 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#390 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#391 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#392 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#393 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#394 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#395 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.137s
#396 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#397 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#398 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#399 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#400 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#401 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#402 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#403 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#404 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#405 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#406 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#407 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#408 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#409 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.137s
#410 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#411 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#412 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#413 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#414 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#415 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#416 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#417 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#418 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#419 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#420 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#421 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#422 linkCache_getLink using $NBC_LINKCACHE +0s … 0.137s
#423 got data and put it in $dataArray +0. 006s … 0.143s
#424 linkCache_getLink using $NBC_LINKCACHE +0.029s … 0.172s
#425 linkCache_getLink using $NBC_LINKCACHE +0s … 0.172s
#426 linkCache_getLink using $NBC_LINKCACHE +0s … 0.172s
#427 linkCache_getLink using $NBC_LINKCACHE +0s … 0.172s
#428 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.173s
#429 linkCache_getLink using $NBC_LINKCACHE +0s … 0.173s
#430 linkCache_getLink using $NBC_LINKCACHE +0s … 0.173s
#431 linkCache_getLink using $NBC_LINKCACHE +0s … 0.173s
#432 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.174s
#433 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#434 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#435 linkCache_getLink using $NBC_LINKCACHE +0s … 0.174s
#436 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.178s
#437 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.178s
#438 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#439 linkCache_getLink using $NBC_LINKCACHE +0s … 0.178s
#440 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.179s
#441 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#442 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#443 linkCache_getLink using $NBC_LINKCACHE +0s … 0.179s
#444 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.18s
#445 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#446 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#447 linkCache_getLink using $NBC_LINKCACHE +0s … 0.18s
#448 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.183s
#449 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#450 linkCache_getLink using $NBC_LINKCACHE +0s … 0.183s
#451 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.183s
#452 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.187s
#453 linkCache_getLink using $NBC_LINKCACHE +0s … 0.187s
#454 linkCache_getLink using $NBC_LINKCACHE +0s … 0.187s
#455 linkCache_getLink using $NBC_LINKCACHE +0s … 0.187s
#456 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.187s
#457 linkCache_getLink using $NBC_LINKCACHE +0s … 0.187s
#458 linkCache_getLink using $NBC_LINKCACHE +0s … 0.187s
#459 linkCache_getLink using $NBC_LINKCACHE +0s … 0.187s
#460 benchmarks composed for output. +0.002s … 0.189s
#461 calculated avg scores. +0s … 0.189s
#462 linkCache_getLink using $NBC_LINKCACHE +0.046s … 0.235s
#463 return log +0.003s … 0.237s
Asus GeForce GTX 950 vs Nvidia GeForce GTX 960: What is the difference?
39points
Asus GeForce GTX 950
51points
Nvidia GeForce GTX 960
Comparison winner
vs
54 facts in comparison
Asus GeForce GTX 950
Nvidia GeForce GTX 960
Why is Asus GeForce GTX 950 better than Nvidia GeForce GTX 960?
- 30W lower TDP?
90Wvs120W - 30. 2mm narrower?
210.8mmvs241mm
Why is Nvidia GeForce GTX 960 better than Asus GeForce GTX 950?
- 101MHz faster GPU clock speed?
1127MHzvs1026MHz - 0.73 TFLOPS higher floating-point performance?
2.31 TFLOPSvs1.58 TFLOPS - 3.3 GPixel/s higher pixel rate?
36.1 GPixel/svs32.8 GPixel/s - 100MHz faster memory clock speed?
1753MHzvs1653MHz - 400MHz higher effective memory clock speed?
7012MHzvs6612MHz - 22.9 GTexels/s higher texture rate?
72.1 GTexels/svs49.2 GTexels/s - 6.2GB/s more memory bandwidth?
112GB/svs105.8GB/s - 256 more shading units?
1024vs768
Which are the most popular comparisons?
Asus GeForce GTX 950
vs
AMD Radeon RX Vega 8
Nvidia GeForce GTX 960
vs
AMD Radeon RX 550
Asus GeForce GTX 950
vs
Nvidia GeForce GT 1030 DDR4
Nvidia GeForce GTX 960
vs
Nvidia GeForce GTX 1050
Asus GeForce GTX 950
vs
Nvidia GeForce RTX 3050 Laptop
Nvidia GeForce GTX 960
vs
Nvidia GeForce GTX 1060
Asus GeForce GTX 950
vs
Nvidia GeForce MX330
Nvidia GeForce GTX 960
vs
Nvidia GeForce GTX 1650
Asus GeForce GTX 950
vs
Nvidia GeForce MX150
Nvidia GeForce GTX 960
vs
Nvidia GeForce GTX 750 Ti
Asus GeForce GTX 950
vs
Nvidia GeForce GTX 750 Ti
Nvidia GeForce GTX 960
vs
AMD Radeon RX 570
Asus GeForce GTX 950
vs
Nvidia GeForce MX130
Nvidia GeForce GTX 960
vs
Nvidia GeForce RTX 3050 Laptop
Asus GeForce GTX 950
vs
Nvidia GeForce MX450 Laptop
Nvidia GeForce GTX 960
vs
AMD Radeon RX 560
Asus GeForce GTX 950
vs
Nvidia Quadro K4000
Nvidia GeForce GTX 960
vs
Nvidia GeForce MX330
Asus GeForce GTX 950
vs
Nvidia GeForce GTX 1050
Nvidia GeForce GTX 960
vs
Nvidia GeForce MX150
Price comparison
User reviews
Overall Rating
Asus GeForce GTX 950
0 User reviews
Asus GeForce GTX 950
0. 0/10
0 User reviews
Nvidia GeForce GTX 960
3 User reviews
Nvidia GeForce GTX 960
9.3/10
3 User reviews
Features
Value for money
No reviews yet
8.3/10
3 votes
Gaming
No reviews yet
8.7/10
3 votes
Performance
No reviews yet
9.0/10
3 votes
Fan noise
No reviews yet
8.0/10
3 votes
Reliability
No reviews yet
10.0/10
3 votes
Performance
1.GPU clock speed
1026MHz
1127MHz
The graphics processing unit (GPU) has a higher clock speed.
2.GPU turbo
1190MHz
1178MHz
When the GPU is running below its limitations, it can boost to a higher clock speed in order to give increased performance.
3.pixel rate
32. 8 GPixel/s
36.1 GPixel/s
The number of pixels that can be rendered to the screen every second.
4.floating-point performance
1.58 TFLOPS
2.31 TFLOPS
Floating-point performance is a measurement of the raw processing power of the GPU.
5.texture rate
49.2 GTexels/s
72.1 GTexels/s
The number of textured pixels that can be rendered to the screen every second.
6.GPU memory speed
1653MHz
1753MHz
The memory clock speed is one aspect that determines the memory bandwidth.
7.shading units
Shading units (or stream processors) are small processors within the graphics card that are responsible for processing different aspects of the image.
8.texture mapping units (TMUs)
TMUs take textures and map them to the geometry of a 3D scene. More TMUs will typically mean that texture information is processed faster.
9.render output units (ROPs)
The ROPs are responsible for some of the final steps of the rendering process, writing the final pixel data to memory and carrying out other tasks such as anti-aliasing to improve the look of graphics.
Memory
1.effective memory speed
6612MHz
7012MHz
The effective memory clock speed is calculated from the size and data rate of the memory. Higher clock speeds can give increased performance in games and other apps.
2.maximum memory bandwidth
105.8GB/s
112GB/s
This is the maximum rate that data can be read from or stored into memory.
3.VRAM
VRAM (video RAM) is the dedicated memory of a graphics card. More VRAM generally allows you to run games at higher settings, especially for things like texture resolution.
4.memory bus width
128bit
128bit
A wider bus width means that it can carry more data per cycle. It is an important factor of memory performance, and therefore the general performance of the graphics card.
5.version of GDDR memory
Newer versions of GDDR memory offer improvements such as higher transfer rates that give increased performance.
6.Supports ECC memory
✖Asus GeForce GTX 950
✖Nvidia GeForce GTX 960
Error-correcting code memory can detect and correct data corruption. It is used when is it essential to avoid corruption, such as scientific computing or when running a server.
Features
1.DirectX version
DirectX is used in games, with newer versions supporting better graphics.
2.OpenGL version
OpenGL is used in games, with newer versions supporting better graphics.
3.OpenCL version
Some apps use OpenCL to apply the power of the graphics processing unit (GPU) for non-graphical computing. Newer versions introduce more functionality and better performance.
4.Supports multi-display technology
✔Asus GeForce GTX 950
✔Nvidia GeForce GTX 960
The graphics card supports multi-display technology. This allows you to configure multiple monitors in order to create a more immersive gaming experience, such as having a wider field of view.
5.load GPU temperature
Unknown. Help us by suggesting a value. (Asus GeForce GTX 950)
A lower load temperature means that the card produces less heat and its cooling system performs better.
6.supports ray tracing
✖Asus GeForce GTX 950
✖Nvidia GeForce GTX 960
Ray tracing is an advanced light rendering technique that provides more realistic lighting, shadows, and reflections in games.
7.Supports 3D
✖Asus GeForce GTX 950
✔Nvidia GeForce GTX 960
Allows you to view in 3D (if you have a 3D display and glasses).
8.supports DLSS
✖Asus GeForce GTX 950
✖Nvidia GeForce GTX 960
DLSS (Deep Learning Super Sampling) is an upscaling technology powered by AI. It allows the graphics card to render games at a lower resolution and upscale them to a higher resolution with near-native visual quality and increased performance. DLSS is only available on select games.
9.PassMark (G3D) result
Unknown. Help us by suggesting a value. (Asus GeForce GTX 950)
This benchmark measures the graphics performance of a video card. Source: PassMark.
Ports
1.has an HDMI output
✔Asus GeForce GTX 950
✔Nvidia GeForce GTX 960
Devices with a HDMI or mini HDMI port can transfer high definition video and audio to a display.
2.HDMI ports
Unknown. Help us by suggesting a value. (Nvidia GeForce GTX 960)
More HDMI ports mean that you can simultaneously connect numerous devices, such as video game consoles and set-top boxes.
3.HDMI version
HDMI 2.0
Unknown. Help us by suggesting a value. (Nvidia GeForce GTX 960)
Newer versions of HDMI support higher bandwidth, which allows for higher resolutions and frame rates.
4.DisplayPort outputs
Allows you to connect to a display using DisplayPort.
5.DVI outputs
Allows you to connect to a display using DVI.
6.mini DisplayPort outputs
Allows you to connect to a display using mini-DisplayPort.
Price comparison
Cancel
Which are the best graphics cards?
GeForce GTX 960 vs GeForce GTX 950
- Home
- VGA Benchmarks
- GeForce GTX 960 vs GeForce GTX 950
-
GeForce GTX 960
122%
-
GeForce GTX 950
100%
Relative performance
-
GeForce GTX 960
124%
-
GeForce GTX 950
100%
Relative performance
Reasons to consider GeForce GTX 960 |
24% higher gaming performance. |
Supports PhysX |
Supports G-Sync |
Supports ShadowPlay (allows game streaming/recording with minimum performance penalty) |
Based on an outdated architecture (Nvidia Maxwell), there may be no performance optimizations for current games and applications |
Reasons to consider GeForce GTX 950 |
Supports PhysX |
Supports G-Sync |
Supports ShadowPlay (allows game streaming/recording with minimum performance penalty) |
Based on an outdated architecture (Nvidia Maxwell), there may be no performance optimizations for current games and applications |
HWBench recommends GeForce GTX 960
The GeForce GTX 960 is the better performing card based on the game benchmark suite used (58 combinations of games and resolutions).
Core Configuration
GeForce GTX 960 | GeForce GTX 950 | |||
---|---|---|---|---|
GPU Name | GM206 (GM206-300-A1) | vs | GM206 (GM206-250-A1) | |
Fab Process | 28 nm | vs | 28 nm | |
Die Size | 228 mm² | vs | 228 mm² | |
Transistors | 2,940 million | vs | 2,940 million | |
Shaders | 1024 | vs | 768 | |
Compute Units | 8 | vs | 6 | |
Core clock | 1127 MHz | vs | 1024 MHz | |
ROPs | 32 | vs | 32 | |
TMUs | 64 | vs | 48 |
Memory Configuration
GeForce GTX 960 | GeForce GTX 950 | |||
---|---|---|---|---|
Memory Type | GDDR5 | vs | GDDR5 | |
Bus Width | 128 bit | vs | 128 bit | |
Memory Speed | 1753 MHz 7012 MHz effective |
vs | 1653 MHz 6612 MHz effective |
|
Memory Size | 2048 Mb | vs | 2048 Mb |
Additional details
GeForce GTX 960 | GeForce GTX 950 | |||
---|---|---|---|---|
TDP | 120 watts | vs | 90 watts | |
Release Date | 22 Jan 2015 | vs | 20 Aug 2015 |
-
GeForce GTX 960
36. 10 GP/s
-
GeForce GTX 950
32.80 GP/s
GigaPixels — higher is better
-
GeForce GTX 960
72.10 GT/s
-
GeForce GTX 950
49.20 GT/s
GigaTexels — higher is better
-
GeForce GTX 960
112.20 GB/s
-
GeForce GTX 950
105.80 GB/s
GB/s — higher is better
-
GeForce GTX 960
2308.10 GFLOPs
-
GeForce GTX 950
1572.90 GFLOPs
GFLOPs — higher is better
-
GeForce GTX 960
10380
-
GeForce GTX 950
8490
Points (higher is better)
DX11, Max Detail, 2xMSAA 16xAF
-
GeForce GTX 960
56
-
GeForce GTX 950
44
FPS (higher is better)
DX11, Ultra Quality, 4xAA
-
GeForce GTX 960
28
-
GeForce GTX 950
23
FPS (higher is better)
-
GeForce GTX 960
10. 4
-
GeForce GTX 950
9.6
FPS (higher is better)
-
GeForce GTX 960
43.7
-
GeForce GTX 950
37.8
FPS (higher is better)
-
GeForce GTX 960
31.2
-
GeForce GTX 950
27.3
FPS (higher is better)
DX11, Ultra Quality, 4xMSAA,EP3 Gator Bait
-
GeForce GTX 960
25
-
GeForce GTX 950
22
FPS (higher is better)
DX11, Ultra, DDOD, FXAA
-
GeForce GTX 960
47
-
GeForce GTX 950
41
FPS (higher is better)
-
GeForce GTX 960
68.3
-
GeForce GTX 950
51.3
FPS (higher is better)
-
GeForce GTX 960
45.9
-
GeForce GTX 950
35.8
FPS (higher is better)
-
GeForce GTX 960
15.8
-
GeForce GTX 950
13.8
FPS (higher is better)
OpenGL, Ultra Quality, SMAA 1tx
-
GeForce GTX 960
30
-
GeForce GTX 950
22
FPS (higher is better)
DX11, Ultra Details, Godrays, High shadows
-
GeForce GTX 960
33
-
GeForce GTX 950
26
FPS (higher is better)
DX11, Very High Settings
-
GeForce GTX 960
27
-
GeForce GTX 950
24
FPS (higher is better)
DX11, Max Details, 16:1 AF, 2xMSAA
-
GeForce GTX 960
37
-
GeForce GTX 950
31
FPS (higher is better)
DX12, Ultra Quality, MSAA, 16x AF
-
GeForce GTX 960
25
-
GeForce GTX 950
16
FPS (higher is better)
DX11, High Quality, 2x MSAA, 16x AF
-
GeForce GTX 960
34
-
GeForce GTX 950
31
FPS (higher is better)
DX11, Very High Detail
-
GeForce GTX 960
44
-
GeForce GTX 950
37
FPS (higher is better)
Very High Details, Pure Hair On, FXAA/HBAO+ enabled, 16x AF, DirectX12, Windows 10 x64
-
GeForce GTX 960
21
-
GeForce GTX 950
19
FPS (higher is better)
DX11,Max Details, 16:1 HQ-AF, +AA
-
GeForce GTX 960
27
-
GeForce GTX 950
20
FPS (higher is better)
DX11, Very High Details
-
GeForce GTX 960
29
-
GeForce GTX 950
26
FPS (higher is better)
DX11, Max Details, 16:1 AF
-
GeForce GTX 960
30
-
GeForce GTX 950
24
FPS (higher is better)
Ultra Quality, Windows 10 x64
-
GeForce GTX 960
20
-
GeForce GTX 950
17
FPS (higher is better)
DX11, Ultra Quality, 4xAA
-
GeForce GTX 960
46
-
GeForce GTX 950
37
FPS (higher is better)
-
GeForce GTX 960
19. 7
-
GeForce GTX 950
16.3
FPS (higher is better)
-
GeForce GTX 960
71.5
-
GeForce GTX 950
62
FPS (higher is better)
-
GeForce GTX 960
49.2
-
GeForce GTX 950
43.4
FPS (higher is better)
DX11, Ultra Quality, 4xMSAA,EP3 Gator Bait
-
GeForce GTX 960
34
-
GeForce GTX 950
32
FPS (higher is better)
-
GeForce GTX 960
94.5
-
GeForce GTX 950
75
FPS (higher is better)
-
GeForce GTX 960
66.4
-
GeForce GTX 950
52.4
FPS (higher is better)
-
GeForce GTX 960
26.3
-
GeForce GTX 950
22.9
FPS (higher is better)
OpenGL, Ultra Quality, SMAA 1tx
-
GeForce GTX 960
38
-
GeForce GTX 950
30
FPS (higher is better)
DX11, Ultra Details, Godrays, High shadows
-
GeForce GTX 960
53
-
GeForce GTX 950
40
FPS (higher is better)
DX11, Very High Settings
-
GeForce GTX 960
42
-
GeForce GTX 950
37
FPS (higher is better)
DX11, Max Details, 16:1 AF, 2xMSAA
-
GeForce GTX 960
53
-
GeForce GTX 950
45
FPS (higher is better)
DX12, Ultra Quality, MSAA, 16x AF
-
GeForce GTX 960
31
-
GeForce GTX 950
22
FPS (higher is better)
Very High Details, Pure Hair On, FXAA/HBAO+ enabled, 16x AF, DirectX12, Windows 10 x64
-
GeForce GTX 960
31
-
GeForce GTX 950
28
FPS (higher is better)
DX11,Max Details, 16:1 HQ-AF, +AA
-
GeForce GTX 960
36
-
GeForce GTX 950
27
FPS (higher is better)
DX11, Very High Details
-
GeForce GTX 960
40
-
GeForce GTX 950
38
FPS (higher is better)
DX11, Max Details, 16:1 AF
-
GeForce GTX 960
40
-
GeForce GTX 950
35
FPS (higher is better)
Ultra Quality, Windows 10 x64
-
GeForce GTX 960
30
-
GeForce GTX 950
24
FPS (higher is better)
DX11, Ultra Quality, 4xAA
-
GeForce GTX 960
17
-
GeForce GTX 950
13
FPS (higher is better)
-
GeForce GTX 960
9. 6
-
GeForce GTX 950
9.5
FPS (higher is better)
-
GeForce GTX 960
20.9
-
GeForce GTX 950
18
FPS (higher is better)
-
GeForce GTX 960
14.4
-
GeForce GTX 950
12.8
FPS (higher is better)
-
GeForce GTX 960
38.9
-
GeForce GTX 950
27
FPS (higher is better)
-
GeForce GTX 960
28
-
GeForce GTX 950
21.2
FPS (higher is better)
-
GeForce GTX 960
10.5
-
GeForce GTX 950
9.2
FPS (higher is better)
OpenGL, Ultra Quality, SMAA 1tx
-
GeForce GTX 960
3
-
GeForce GTX 950
2
FPS (higher is better)
DX11, Ultra Details, Godrays, High shadows
-
GeForce GTX 960
14
-
GeForce GTX 950
11
FPS (higher is better)
DX11, Very High Settings
-
GeForce GTX 960
10
-
GeForce GTX 950
8
FPS (higher is better)
DX12, Ultra Quality, MSAA, 16x AF
-
GeForce GTX 960
10
-
GeForce GTX 950
8
FPS (higher is better)
DX11, Very High Detail
-
GeForce GTX 960
22
-
GeForce GTX 950
17
FPS (higher is better)
Very High Details, Pure Hair On, FXAA/HBAO+ enabled, 16x AF, DirectX12, Windows 10 x64
-
GeForce GTX 960
9
-
GeForce GTX 950
5
FPS (higher is better)
DX11,Max Details, 16:1 HQ-AF, +AA
-
GeForce GTX 960
14
-
GeForce GTX 950
11
FPS (higher is better)
DX11, Very High Details
-
GeForce GTX 960
7
-
GeForce GTX 950
7
FPS (higher is better)
DX11, Max Details, 16:1 AF
-
GeForce GTX 960
11
-
GeForce GTX 950
6
FPS (higher is better)
Ultra Quality, Windows 10 x64
-
GeForce GTX 960
6
-
GeForce GTX 950
4
FPS (higher is better)
DX11, Very High Detail
-
GeForce GTX 960
13
-
GeForce GTX 950
8
FPS (higher is better)
VS | ||
GeForce GTX 960 | GeForce GTX 1050 3 GB |
VS | ||
GeForce GTX 960 | GeForce GTX 1050 |
VS | ||
GeForce GTX 950 | Radeon RX 560 |
VS | ||
GeForce GTX 950 | Radeon RX 460 |
VS | ||
Radeon R9 380 | Radeon R9 380 OEM |
VS | ||
Radeon R9 380 OEM | Radeon R9 285 |
Please enable JavaScript to view the comments powered by Disqus.
NVIDIA GeForce GTX 950 vs NVIDIA GeForce GTX 960
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 12. 22:58:42
#0 checking url part for id 6461 +0s … 0s
#1 checking url part for id 6311 +0s … 0s
#2 not redirecting to Ajax server +0s … 0s
#3 did not recreate cache, as it is less than 5 days old! Created at Mon, 12 Sep 2022 17:26:57 +0200 +0s … 0.001s
#4 linkCache_getLink using $NBC_LINKCACHE +0.049s … 0.05s
#5 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.053s
#6 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.053s
#7 linkCache_getLink using $NBC_LINKCACHE +0s … 0.053s
#8 linkCache_getLink using $NBC_LINKCACHE +0s … 0.053s
#9 linkCache_getLink using $NBC_LINKCACHE +0s … 0.053s
#10 linkCache_getLink using $NBC_LINKCACHE +0s … 0.053s
#11 composed specs +0s … 0.054s
#12 did output specs +0s … 0.054s
#13 start showIntegratedCPUs +0s … 0.054s
#14 getting avg benchmarks for device 6461 +0.036s … 0.09s
#15 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.091s
#16 got single benchmarks 6461 +0.007s … 0.097s
#17 linkCache_getLink using $NBC_LINKCACHE +0.004s … 0.101s
#18 linkCache_getLink using $NBC_LINKCACHE +0.004s … 0.104s
#19 getting avg benchmarks for device 6311 +0s … 0.104s
#20 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.105s
#21 got single benchmarks 6311 +0.008s . .. 0.113s
#22 got avg benchmarks for devices +0s … 0.113s
#23 linkCache_getLink no uid found +0s … 0.113s
#24 linkCache_getLink no uid found +0s … 0.113s
#25 linkCache_getLink no uid found +0s … 0.114s
#26 linkCache_getLink no uid found +0.001s … 0.114s
#27 linkCache_getLink no uid found +0s … 0.115s
#28 linkCache_getLink no uid found +0s … 0.115s
#29 linkCache_getLink using $NBC_LINKCACHE +0s … 0.115s
#30 linkCache_getLink no uid found +0s … 0.116s
#31 linkCache_getLink no uid found +0s … 0.116s
#32 linkCache_getLink using $NBC_LINKCACHE +0s … 0.116s
#33 linkCache_getLink no uid found +0s … 0.116s
#34 linkCache_getLink no uid found +0s … 0.116s
#35 linkCache_getLink no uid found +0s … 0.116s
#36 linkCache_getLink no uid found +0s … 0.117s
#37 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.117s
#38 linkCache_getLink no uid found +0s … 0.117s
#39 linkCache_getLink using $NBC_LINKCACHE +0s … 0.118s
#40 linkCache_getLink no uid found +0s … 0.118s
#41 linkCache_getLink no uid found +0.001s … 0.118s
#42 linkCache_getLink no uid found +0s … 0.118s
#43 linkCache_getLink using $NBC_LINKCACHE +0s … 0.119s
#44 linkCache_getLink no uid found +0s … 0.119s
#45 linkCache_getLink no uid found +0.001s … 0.119s
#46 linkCache_getLink no uid found +0s … 0.119s
#47 linkCache_getLink no uid found +0s … 0.12s
#48 linkCache_getLink using $NBC_LINKCACHE +0s … 0.12s
#49 linkCache_getLink no uid found +0s … 0.12s
#50 linkCache_getLink no uid found +0s … 0.121s
#51 linkCache_getLink no uid found +0s … 0.121s
#52 linkCache_getLink no uid found +0.001s … 0.122s
#53 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.122s
#54 linkCache_getLink no uid found +0s … 0.122s
#55 linkCache_getLink using $NBC_LINKCACHE +0s … 0.123s
#56 linkCache_getLink no uid found +0s … 0.123s
#57 linkCache_getLink using $NBC_LINKCACHE +0s … 0.123s
#58 linkCache_getLink no uid found +0s … 0.124s
#59 linkCache_getLink using $NBC_LINKCACHE +0s … 0.124s
#60 linkCache_getLink no uid found +0s … 0.125s
#61 linkCache_getLink using $NBC_LINKCACHE +0s … 0.125s
#62 linkCache_getLink no uid found +0s … 0.125s
#63 linkCache_getLink using $NBC_LINKCACHE +0s … 0.126s
#64 linkCache_getLink no uid found +0s … 0.126s
#65 linkCache_getLink using $NBC_LINKCACHE +0s … 0.126s
#66 linkCache_getLink no uid found +0s … 0.127s
#67 linkCache_getLink using $NBC_LINKCACHE +0s … 0.127s
#68 linkCache_getLink no uid found +0s . .. 0.127s
#69 linkCache_getLink using $NBC_LINKCACHE +0s … 0.127s
#70 linkCache_getLink no uid found +0.001s … 0.128s
#71 linkCache_getLink using $NBC_LINKCACHE +0s … 0.128s
#72 linkCache_getLink no uid found +0s … 0.128s
#73 linkCache_getLink no uid found +0.001s … 0.129s
#74 linkCache_getLink using $NBC_LINKCACHE +0s … 0.129s
#75 linkCache_getLink no uid found +0s … 0.129s
#76 linkCache_getLink no uid found +0s … 0.13s
#77 linkCache_getLink no uid found +0s … 0.13s
#78 linkCache_getLink no uid found +0s … 0.131s
#79 linkCache_getLink no uid found +0s … 0.131s
#80 linkCache_getLink no uid found +0s … 0.131s
#81 linkCache_getLink no uid found +0s … 0.132s
#82 min, max, avg, median took s +0s … 0.132s
#83 before gaming benchmark output +0s … 0.132s
#84 Got 384 rows for game benchmarks. +0.02s … 0.153s
#85 composed SQL query for gamebenchmarks +0s … 0.153s
#86 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#87 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#88 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#89 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#90 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#91 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#92 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#93 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#94 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#95 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#96 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#97 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#98 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.153s
#99 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#100 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#101 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#102 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#103 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#104 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#105 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#106 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#107 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#108 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#109 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#110 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#111 linkCache_getLink using $NBC_LINKCACHE +0s … 0.153s
#112 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.154s
#113 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#114 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#115 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#116 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#117 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#118 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#119 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#120 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#121 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#122 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#123 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#124 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#125 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#126 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.154s
#127 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#128 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#129 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#130 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#131 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#132 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#133 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#134 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#135 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#136 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#137 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#138 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#139 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#140 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.154s
#141 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#142 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#143 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#144 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#145 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#146 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#147 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#148 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#149 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#150 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#151 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#152 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#153 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#154 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.154s
#155 linkCache_getLink using $NBC_LINKCACHE +0s … 0.154s
#156 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#157 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#158 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#159 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#160 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#161 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#162 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#163 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#164 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#165 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#166 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#167 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#168 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.155s
#169 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#170 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#171 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#172 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#173 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#174 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#175 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#176 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#177 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#178 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#179 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#180 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#181 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#182 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.155s
#183 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#184 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#185 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#186 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#187 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#188 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#189 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#190 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#191 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#192 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#193 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#194 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#195 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#196 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.155s
#197 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#198 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#199 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#200 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#201 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#202 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#203 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#204 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#205 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#206 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#207 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#208 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#209 linkCache_getLink using $NBC_LINKCACHE +0s … 0.155s
#210 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.156s
#211 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#212 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#213 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#214 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#215 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#216 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#217 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#218 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#219 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#220 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#221 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#222 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#223 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#224 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.156s
#225 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#226 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#227 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#228 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#229 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#230 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#231 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#232 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#233 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#234 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#235 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#236 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#237 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#238 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.156s
#239 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#240 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#241 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#242 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#243 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#244 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#245 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#246 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#247 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#248 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#249 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#250 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#251 linkCache_getLink using $NBC_LINKCACHE +0s … 0.156s
#252 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.157s
#253 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#254 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#255 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#256 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#257 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#258 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#259 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#260 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#261 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#262 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#263 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#264 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#265 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#266 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.157s
#267 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#268 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#269 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#270 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#271 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#272 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#273 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#274 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#275 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#276 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#277 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#278 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#279 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#280 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.157s
#281 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#282 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#283 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#284 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#285 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#286 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#287 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#288 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#289 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#290 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#291 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#292 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#293 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#294 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.157s
#295 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#296 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#297 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#298 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#299 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#300 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#301 linkCache_getLink using $NBC_LINKCACHE +0s … 0.157s
#302 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#303 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#304 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#305 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#306 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#307 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#308 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.158s
#309 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#310 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#311 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#312 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#313 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#314 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#315 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#316 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#317 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#318 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#319 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#320 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#321 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#322 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.158s
#323 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#324 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#325 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#326 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#327 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#328 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#329 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#330 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#331 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#332 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#333 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#334 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#335 linkCache_getLink using $NBC_LINKCACHE +0s … 0.158s
#336 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.158s
#337 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#338 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#339 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#340 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#341 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#342 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#343 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#344 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#345 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#346 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#347 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#348 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#349 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#350 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.159s
#351 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#352 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#353 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#354 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#355 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#356 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#357 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#358 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#359 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#360 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#361 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#362 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#363 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#364 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.159s
#365 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#366 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#367 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#368 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#369 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#370 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#371 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#372 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#373 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#374 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#375 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#376 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#377 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#378 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.159s
#379 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#380 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#381 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#382 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#383 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#384 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#385 linkCache_getLink using $NBC_LINKCACHE +0s … 0.159s
#386 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#387 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#388 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#389 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#390 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#391 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#392 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.16s
#393 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#394 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#395 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#396 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#397 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#398 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#399 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#400 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#401 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#402 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#403 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#404 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#405 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#406 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#407 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.16s
#408 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#409 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#410 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#411 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#412 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#413 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#414 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#415 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#416 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#417 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#418 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#419 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#420 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#421 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#422 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.16s
#423 linkCache_getLink using $NBC_LINKCACHE +0s … 0.16s
#424 got data and put it in $dataArray +0.003s … 0.163s
#425 linkCache_getLink using $NBC_LINKCACHE +0.028s … 0.191s
#426 linkCache_getLink using $NBC_LINKCACHE +0s … 0.191s
#427 linkCache_getLink using $NBC_LINKCACHE +0s … 0.191s
#428 linkCache_getLink using $NBC_LINKCACHE +0s … 0.191s
#429 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.192s
#430 linkCache_getLink using $NBC_LINKCACHE +0s … 0.192s
#431 linkCache_getLink using $NBC_LINKCACHE +0s … 0.192s
#432 linkCache_getLink using $NBC_LINKCACHE +0s … 0.192s
#433 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.193s
#434 linkCache_getLink using $NBC_LINKCACHE +0s … 0.193s
#435 linkCache_getLink using $NBC_LINKCACHE +0s … 0.193s
#436 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.193s
#437 linkCache_getLink using $NBC_LINKCACHE +0.004s … 0.197s
#438 linkCache_getLink using $NBC_LINKCACHE +0s … 0.197s
#439 linkCache_getLink using $NBC_LINKCACHE +0s … 0.197s
#440 linkCache_getLink using $NBC_LINKCACHE +0s … 0.197s
#441 linkCache_getLink using $NBC_LINKCACHE +0.002s … 0.199s
#442 linkCache_getLink using $NBC_LINKCACHE +0s … 0.199s
#443 linkCache_getLink using $NBC_LINKCACHE +0s … 0.199s
#444 linkCache_getLink using $NBC_LINKCACHE +0s … 0.199s
#445 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.2s
#446 linkCache_getLink using $NBC_LINKCACHE +0s … 0.2s
#447 linkCache_getLink using $NBC_LINKCACHE +0s … 0.2s
#448 linkCache_getLink using $NBC_LINKCACHE +0s … 0.2s
#449 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.202s
#450 linkCache_getLink using $NBC_LINKCACHE +0s . .. 0.203s
#451 linkCache_getLink using $NBC_LINKCACHE +0s … 0.203s
#452 linkCache_getLink using $NBC_LINKCACHE +0s … 0.203s
#453 linkCache_getLink using $NBC_LINKCACHE +0.003s … 0.206s
#454 linkCache_getLink using $NBC_LINKCACHE +0s … 0.206s
#455 linkCache_getLink using $NBC_LINKCACHE +0s … 0.206s
#456 linkCache_getLink using $NBC_LINKCACHE +0s … 0.206s
#457 linkCache_getLink using $NBC_LINKCACHE +0.001s … 0.206s
#458 linkCache_getLink using $NBC_LINKCACHE +0s … 0.206s
#459 linkCache_getLink using $NBC_LINKCACHE +0s … 0.207s
#460 linkCache_getLink using $NBC_LINKCACHE +0s … 0.207s
#461 benchmarks composed for output. +0.002s … 0.209s
#462 calculated avg scores. +0s … 0.209s
#463 linkCache_getLink using $NBC_LINKCACHE +0.1s … 0.308s
#464 return log +0.003s … 0.311s
GTX 960 2GB vs.
4GB in 2019 – How Much VRAM Capacity Matters vs. GPU | GamersNexus
One of our most popular videos of yore talks about the GTX 960 4GB vs. GTX 960 2GB cards and the value of choosing one over the other. The discussion continues today, but is more focused on 3GB vs. 6GB comparisons, or 4GB vs. 8GB comparisons. Now, looking back at 2015’s GTX 960, we’re revisiting with locked frequencies to compare memory capacities. The goal is to look at both framerate and image quality to determine how well the 2GB card has aged versus how well the 4GB card has aged.
A lot of things have changed for us since our 2015 GTX 960 comparison, so these results will obviously not be directly comparable to the time. We’re using different graphics settings, different test methods, a different OS, and much different test hardware. We’ve also improved our testing accuracy significantly, and so it’s time to take all of this new hardware and knowledge and re-apply it to the GTX 960 2GB vs. 4GB debate, looking into whether there was really a “longevity” argument to be made.
Note further that this becomes a discussion of image quality in addition to performance, as higher framerates can be had by silently (but often noticeably) reducing image quality in the game. Not all games do this, although some will lower texture quality or object detail against the player’s settings, meaning that a comparison may not be truly head-to-head if changes silently happen.
For this testing, we locked the memory frequencies and GPU clocks to be identical. Because this is Bosot 2.0 and doesn’t use modern thermal-dependent GPU boosting, it’s easy to get the clocks 100% matched between two different models. The only difference becomes the memory capacity. As a further reminder, people often reference Windows Task Manager or GPU-Z for “memory consumption,” or OSDs, but these only show the memory allocated to or requested by the software, not necessarily the literal memory in use. Applications often request far more than they need, which means we can’t rely on a straight “memory utilization” figure to determine if 2GB vs. 4GB is sufficient; instead, we have to look at image quality comparisons and frametimes.
GPU Test Bench
Component
|
Courtesy of
|
|
CPU
|
Intel i7-8086K 5.0GHz
|
GamersNexus
|
GPU
|
This is what we’re testing!
|
Often the company that makes the card, but sometimes us (see article)
|
Motherboard
|
ASUS ROG Maximus X Hero
|
ASUS
|
RAM
|
Corsair Vengeance LPX 32GB 3200MHz
|
Corsair
|
PSU
|
Corsair AX1600i
|
Corsair
|
Cooler
|
NZXT Kraken X62
|
NZXT
|
SSD
|
Plextor 256-M7VC
|
GamersNexus
|
Sniper Elite 4
Sniper Elite 4 is the absolute best example to start with, and it’s because the FPS numbers completely betray what’s happening on the screen. If we look at our GPU bench chart at 1080p in Sniper Elite 4, you’ll see that the GTX 960 Strix 2GB card actually posts a 57FPS AVG, with lows well-spaced at 41FPS and 39FPS. Comparatively, the GTX 960 SSC 4GB card is within margin of error, at 58FPS AVG. Lows are also within our wider error margins for the smaller datasets of 1% lows. As a framerate, it looks like there’s no difference, and that the 4GB card might actually be “overkill,” as you could postulate that the rest of the GPU doesn’t keep-up enough for the memory capacity to matter. In reality, we need an image quality comparison.
Above: 4K, worst case. Very unrealistic but demonstrates the issues
Above: Differences don’t emerge in 1080p unless playing bigger/more complex levels for a longer period of time
All games will handle this in their own way, but Sniper Elite 4 handles VRAM limitations by just silently – although obviously – tanking texture resolution and quality to compensate for overextension on VRAM consumption. This is immediately visible, even without a side-by-side comparison. As such, the framerate results are clearly invalid, as they aren’t testing the same thing. This game doesn’t ignore VRAM limitations and so will fit the memory capacity it is allotted, thus resulting in an unequal comparison. The answer, then, is that the GTX 960 2GB card is immediately becoming limiting for us. At around 60FPS, the GTX 960 4GB is actually still fully playable today in Sniper Elite 4, even at high settings and 1080p resolution, but 960 2GB purchasers would be looking for upgrades at this point. Some of our image quality comparisons are at higher resolutions, just to further stress the VRAM and demonstrate the loss of shadow quality, texture quality, and mesh quality to accommodate the VRAM limitations.
Apex Legends
Apex Legends at 1080p positions the GTX 960 SSC 4GB at 42FPS AVG when clock-matched with the Strix 2GB card, running lows in the range of 30FPS. Note that we could improve performance with lowered settings, clearly, but the goal is more to focus on head-to-head comparisons. The 4GB card leads outside of margin of error, claiming a 10% gain.
GTA V
GTA V was released after the GTX 960s launched by just a few months, so it’s the closest-to-launch comparison. At 1080p, the GTX 960 2GB card ends up at 50FPS AVG, and is well within error margins when compared to the 960 SSC. These are about as close as you can get.
At 1440p, we see the same results: The two cards are within margin of error of each other, and so we can declare that they are functionally the same in this test; at least, that’s true with regard to performance.
GTA V image quality doesn’t show the same change Sniper Elite 4 did, which is again logical with the lack of equality in framerate performance. The two images have the same texture quality.
F1 2018
F1 2018 at 1080p positions the GTX 960 SSC 4GB card at 45FPS AVG when frequency-locked, with lows at 28FPS and 16FPS 1% and 0.1% lows. The GTX 960 Strix 2GB card did about 42FPS AVG, enabling the 4GB card a lead of 8. 2%. This difference is outside of our run-to-run error. We did have one test pass that had an excursion from the mean, but even if we eliminate this test pass, the lead of the 4GB card remains at 5.5% and is outside of error margins.
At 1440p, our existence of the stock 960 SSC and the clock-locked one helps illustrate that test results are outside of error margins, as these two devices represent different test settings that are still advantaged by extra memory. The test range is +/-0.5FPS AVG for these cards. The Strix 960 2GB card hits 29.6FPS AVG, permitting the clock-locked 960 SSC at 1442 MHz a lead of about 16% at 1440p. This is substantial and, although 1440p isn’t a particularly good experience on these cards, the important part is that it stresses VRAM and illustrates limitations. These are further illustrated with the significantly lower 1% and 0.1% lows on the 2GB card, demonstrating frametime variance and inconsistency.
Even at 1440p, F1 2018 image quality remains the same between the 2GB and 4GB devices. We drop performance from swapping in and out of video memory more aggressively, but don’t seem to have a reduction in mesh quality or texture quality.
Far Cry 5
Far Cry 5 at 1080p doesn’t illustrate differences of any major margin. We’re at 44FPS AVG for the 960 SSC 4GB variants, with the Strix 960 2GB card at 42.1FPS AVG. These are nearing error margins, although the range technically does exit them just barely.
At 1440p, the differences emerge with greater resolution. The 960 4GB cards maintain a lead of about 11%, since each frame at this rate is meaningful, and the 0.1% lows also show some gains on the 4GB card.
Far Cry 5 also doesn’t suffer an image quality reduction, which is largely illustrated by the framerate difference in performance. We’d likely see an image quality reduction accompanied with a framerate increase, which is not observed here.
SOTTR
Shadow of the Tomb Raider at 1080p places the frequency-locked 960 at 36.7FPS AVG, allowing it a lead of about 14%. Every single test pass for the 960 4GB was between 36.6 and 36.8FPS AVG, marking this benchmark as highly reliable and with minimal variance. The 960 Strix demonstrated more variance, with results between 31.7 and 33.1FPS AVG.
1440p shows the same scaling we’ve seen before, with the 4GB card pulling ahead in a measurable way, but again, we’re at a point where you wouldn’t be playing on either card. It’s still important to show the difference, just not particularly meaningful to the user.
Shadow of the Tomb Raider’s image quality also looks the same between two. Some characters randomly generate, but looking at floor tiles, we see the same texture quality and resolution. The same is true for Lara Croft, who has the same texture and mesh quality in each scene. The tree and pole behind her also have the same image quality.
Conclusion
As we stretch into scenarios of general unplayability on each device, e.g. 26FPS AVG vs. 30FPS AVG, we do start to see differences which are “significant” from a pure percentages standpoint. This makes sense, as the numbers are becoming smaller and so the delta looks wider, but the reality is that a player would likely be equally unhappy at 26FPS and 30FPS. For differences to really start showing large percent deltas between 2GB and 4GB cards (in our tested games), we have to push settings to a point where neither device would be particularly good to use, giving us an academic exercise rather than a practical comparison. The most meaningful difference was in Sniper Elite 4, although this didn’t occur in other games we tested (but it is a feature in games we didn’t test, so that’s worth considering). Sniper had image quality reductions at higher settings that became not only apparent, but painful to look at. This made for an objectively and significantly worse experience on the 2GB card, despite relatively similar framerate numbers. Once again, though, we begin entering territory where neither device is particularly playable at the settings used (but could be made playable), and so the usefulness of this comparison straddles more on the side of “interesting” rather than “practical. ”
Editorial, Testing: Steve Burke
Video: Josh Svoboda, Andrew Coleman
.3 GPixel/s vs 36.1 GPixel/s
90W vs 120W
2 vs 1
181mm vs 241mm
- GPU frequency 101MHz higher?
1127MHz vs 1026MHz - 0.42 TFLOPS higher than FLOPS?
2.31 TFLOPS vs 1.89 TFLOPS - 100MHz faster memory speed?
1753MHz vs 1653MHz - 400MHz higher effective clock speed?
7012MHz vs 6612MHz - 13.16 GTexels/s higher number of textured pixels? more memory bandwidth?
112GB/s vs 105.8GB/s - 256 more stream processors?
1024 vs 768 - 16 more texture units (TMUs)?
64 vs 48
Which comparisons are the most popular?
Gigabyte GeForce GTX 950
vs
AMD Radeon RX 550
Nvidia GeForce GTX 960
vs
AMD Radeon RX 550
Gigabyte GeForce GTX 950
vs
Nvidia GeForce GTX 1050
Nvidia GeForce GTX 960
vs
Nvidia GeForce GTX 1050
Gigabyte GeForce GTX 950
vs
Nvidia GeForce GTX 750 Ti
Nvidia GeForce GTX 960
vs
Nvidia GeForce GTX 1060
Gigabyte GeForce GTX 950
vs
Nvidia GeForce GTX 650 Ti
Nvidia GeForce GTX 960
vs
Nvidia GeForce GTX 1650
Gigabyte GeForce GTX 950
0003
Nvidia GeForce MX110
Nvidia GeForce GTX 960
vs
Nvidia GeForce GTX 750 Ti
Gigabyte GeForce GTX 950
vs
Nvidia GeForce GTX 780 Ti
Nvidia GeForce GTX 960
vs
AMD Radeon Gigabyte GeForce GTX 950
vs
AMD Radeon RX 560
Nvidia GeForce GTX 960
vs
Nvidia GeForce RTX 3050 Gigabyte
Laptop50
vs
Nvidia GeForce MX150
Nvidia GeForce GTX 960
vs
AMD Radeon RX 560
Gigabyte GeForce GTX 950
vs
MSI GeForce GTX 1660 Super Gaming X
Nvidia GeForce GTX 960
vs
Nvidia GeForce MX330
Gigabyte GeForce GTX 950
0003
8. 0 /10
1 Votes
8.3 /10
3 Votes
Games
7.0 /10
1 VOTES
8.7 /10,000 9000 VOTES
8.0 /10
1 Votes
/10
3 Votes
Tannah noise
10.0 /10
1 votes
004 3 Votes
Reliability
10.0 /10
1 VOTES
10.0 /10
3 Votes
performance
1. TCIO FOURS CP
1026MHz
1127MHZ 9000 9000 (GP ) has a higher clock speed.
2.turbo GPU
1190MHz
1178MHz
When the GPU is running below its limits, it can jump to a higher clock speed to increase performance.
3.pixel rate
39.3 GPixel/s
36.1 GPixel/s
The number of pixels that can be displayed on the screen every second.
4. flops
1.89 TFLOPS
2.31 TFLOPS
FLOPS is a measure of GPU processing power.
5.texture size
58.94 GTexels/s
72.1 GTexels/s
Number of textured pixels that can be displayed on the screen every second.
6.GPU memory speed
1653MHz
1753MHz
Memory speed is one aspect that determines memory bandwidth.
7.shading patterns
Shading units (or stream processors) are small processors in a video card that are responsible for processing various aspects of an image.
8.textured units (TMUs)
TMUs accept textured units and bind them to the geometric layout of the 3D scene. More TMUs generally means texture information is processed faster.
9 ROPs
ROPs are responsible for some of the final steps of the rendering process, such as writing the final pixel data to memory and for performing other tasks such as anti-aliasing to improve the appearance of graphics.
Memory
1.memory effective speed
6612MHz
7012MHz
The effective memory clock frequency is calculated from the memory size and data transfer rate. A higher clock speed can give better performance in games and other applications.
2.max memory bandwidth
105.8GB/s
112GB/s
This is the maximum rate at which data can be read from or stored in memory.
3.VRAM
VRAM (video RAM) is the dedicated memory of the graphics card. More VRAM usually allows you to run games at higher settings, especially for things like texture resolution.
4. memory bus width
128bit
128bit
Wider memory bus means it can carry more data per cycle. This is an important factor in memory performance, and therefore the overall performance of the graphics card.
5. GDDR memory versions
Later versions of GDDR memory offer improvements such as higher data transfer rates, which improve performance.
6. Supports memory debug code
✖Gigabyte GeForce GTX 950
✖Nvidia GeForce GTX 960
Memory debug code can detect and fix data corruption. It is used when necessary to avoid distortion, such as in scientific computing or when starting a server.
Functions
1.DirectX version
DirectX is used in games with a new version that supports better graphics.
2nd version of OpenGL
The newer version of OpenGL, the better graphics quality in games.
OpenCL version 3.
Some applications use OpenCL to use the power of the graphics processing unit (GPU) for non-graphical computing. Newer versions are more functional and better quality.
4. Supports multi-monitor technology
✔Gigabyte GeForce GTX 950
✔Nvidia GeForce GTX 960
The video card has the ability to connect multiple screens. This allows you to set up multiple monitors at the same time to create a more immersive gaming experience, such as a wider field of view.
5. GPU temperature at boot
Unknown. Help us offer a price. (Gigabyte GeForce GTX 950)
Lower boot temperature means the card generates less heat and the cooling system works better.
6.supports ray tracing
✖Gigabyte GeForce GTX 950
✖Nvidia GeForce GTX 960
Ray tracing is an advanced light rendering technique that provides more realistic lighting, shadows and reflections in games.
7.Supports 3D
✔Gigabyte GeForce GTX 950
✔Nvidia GeForce GTX 960
Allows you to view in 3D (if you have a 3D screen and glasses).
8.supports DLSS
✖Gigabyte GeForce GTX 950
✖Nvidia GeForce GTX 960
DLSS (Deep Learning Super Sampling) is an AI based scaling technology. This allows the graphics card to render games at lower resolutions and upscale them to higher resolutions with near-native visual quality and improved performance. DLSS is only available in some games.
9. PassMark result (G3D)
Unknown. Help us offer a price. (Gigabyte GeForce GTX 950)
This test measures the graphics performance of a graphics card. Source: Pass Mark.
Ports
1.has HDMI output
✔Gigabyte GeForce GTX 950
✔Nvidia GeForce GTX 960
Devices with HDMI or mini HDMI ports can stream HD video and audio to an attached display.
2.HDMI connectors
Unknown. Help us offer a price. (Nvidia GeForce GTX 960)
More HDMI connections allow you to connect multiple devices at the same time, such as game consoles and TVs.
HDMI 3.Version
HDMI 2.0
Unknown. Help us offer a price. (Nvidia GeForce GTX 960)
New versions of HDMI support higher bandwidth, resulting in higher resolutions and frame rates.
4. DisplayPort outputs
Allows connection to a display using DisplayPort.
5.DVI outputs
Allows connection to a display using DVI.
6. Mini DisplayPort 9 outputs0003
Allows you to connect to a display using Mini DisplayPort.
Price Match
Cancel
Which graphics cards are better?
Comparison of GeForce GTX 960 and GeForce GTX 950M. Which video card is better?
GeForce GTX 960 |
GeForce GTX 950M |
January, 2015 | 1.1GHz | 2GB GDDR5 |
March, 2015 | 993MHz | 4GB DDR3 |
Edelmark rating |
Edelmark rating |
General comparison
Game performance
Video card tested on: Battlefield 3, Battlefield 4, Bioshock Infinite, Crysis 2, Crysis 3, Dirt3, FarCry 3, Hitman: Absolution, Metro: Last Light, Thief, Alien: Isolation , Anno 2070, Counter-Strike: Global Offensive, Diablo III, Dirt Rally, Dragon Age: Inquisition, The Elder Scrolls V: Skyrim, FIFA 15, FIFA 16, GRID Autosport, Grand Theft Auto V, Sleeping Dogs, Tomb Raider, The Witcher 3: Wild Hunt.
GeForce GTX 960 | 6.9 out of 10 |
---|---|
GeForce GTX 950M | 5.7 out of 10 |
GeForce GTX 1050 Ti | 6.9 out of 10 |
Graphics
Tested with: T-Rex, Manhattan, Cloud Gate Factor, Sky Diver Factor, Fire Strike Factor.
GeForce GTX 960 | 8.0 out of 10 |
---|---|
GeForce GTX 950M | 5.4 out of 10 |
GeForce GTX 1050 Ti | 6. 2 out of 10 |
Computing power
Tested on: Face Detection, Ocean Surface Simulation, Particle Simulation, Video Composition, Bitcoin Mining.
GeForce GTX 960 | 6.2 out of 10 |
---|---|
GeForce GTX 950M | 5.9 out of 10 |
GeForce GTX 1050 Ti | 6.4 out of 10 |
Output per W
Tested on: Battlefield 3, Battlefield 4, Bioshock Infinite, Crysis 2, Crysis 3, Dirt3, FarCry 3, Hitman: Absolution, Metro: Last Light, Thief, Alien: Isolation, Anno 2070, Counter-Strike: Global Offensive, Diablo III, Dirt Rally, Dragon Age: Inquisition, The Elder Scrolls V: Skyrim, FIFA 15, FIFA 16, GRID Autosport, Grand Theft Auto V, Sleeping Dogs, Tomb Raider, The Witcher 3: Wild Hunt, T-Rex, Manhattan , Cloud Gate Factor, Sky Diver Factor, Fire Strike Factor, Face Detection, Ocean Surface Simulation, Particle Simulation, Video Composition, Bitcoin Mining, TDP.
GeForce GTX 960 | 7. 9 out of 10 |
---|---|
GeForce GTX 950M | 7.0 out of 10 |
GeForce GTX 1050 Ti | 7.9 out of 10 |
Noise and power
Tested using: TDP, Idle Power Consumption, Load Power Consumption, Idle Noise Level, Load Noise Level.
GeForce GTX 960 | 9.1 out of 10 |
---|---|
GeForce GTX 950M | 9.5 out of 10 |
GeForce GTX 1050 Ti | 9.5 out of 10 |
Overall graphics card rating
GeForce GTX 960 | 7.3 out of 10 |
---|---|
GeForce GTX 950M | 6.1 out of 10 |
GeForce GTX 1050 Ti | 6.9 out of 10 |
Benefits
Why is the GeForce GTX 960 better?
Significantly better PassMark score | 5.813 | vs | 1.807 | Approximately 3.2x better PassMark score of |
---|---|---|---|---|
Much higher effective memory clock speed | 7. 012 MHz | vs | 1.800 MHz | Approximately 4x the effective memory clock speed of |
Significantly better 3DMark vantage rating | 32.171 | vs | 14.227 | More than 2.2x better 3DMark vantage rating of |
Better 3DMark 11 rating | 32.987 | vs | 22.237 | Approximately 50% better 3DMark 11 score |
Better 3DMark06 rating | 10,767.5 | vs | 4.444 | Approximately 2.5x better 3DMark06 score |
Overclocked | 1.127 MHz | vs | 993 MHz | Approximately 15% higher clock speed |
Higher memory bandwidth | 112.2 GB/s | vs | 28.8 GB/s | Approximately 4x the memory bandwidth of |
Faster pixel fill rate | 36.1GPixel/s | vs | 15.89 GPixel/s | More than 2. 2x faster pixel fill rate |
Much higher memory clock speed | 1.753 MHz | vs | 900 MHz | Approximately 95% higher memory clock speed |
Better floating point performance | 2,308.1 GFLOPS | vs | 1.271 GFLOPS | More than 80% better floating point performance |
More raster operation blocks | 32 | vs | 16 | Twice as many raster operation blocks |
Faster texture processing | 72.1 GTexel/s | vs | 39.7 GTexel/s | More than 80% faster texture rendering speed |
Significantly higher frame rate crysis 3 | 36.1 fps | vs | 12.7 fps | More than 2.8x framerate crysis 3 |
Significantly higher frame rate BioShock infinite | 75.8fps | vs | 29.6 fps | More than 2. 5x the frame rate of BioShock infinite |
Better PassMark direct rating | 3.046 | vs | 1.373 | Approximately 2.2x better PassMark |
Higher frame rate in battlefield 4 | 58 | vs | 22.75 | More than 2.5x higher frame rate in battlefield 4 |
More shaders | 1.024 | vs | 640 | 384 more shader units |
More texture units | 64 | vs | 40 | 24 more texture units |
Why is the GeForce GTX 950M better?
More memory | vs | 2.048 MB | 2x more memory | |
---|---|---|---|---|
Lower power consumption | 75W | vs | 120W | Approximately 40% lower power consumption |
Comparative benchmarks (benchmarks)
Bitcoin mining
GeForce GTX 960 | 111. 95 mHash/s |
---|---|
GeForce GTX 950M | 139.03 mHash/s |
Face Recognition
GeForce GTX 960 | 69.13 mPixels/s |
---|---|
GeForce GTX 950M | 41.85 mPixels/s |
Ocean Surface Modeling
GeForce GTX 960 | 780.9 frames/s |
---|---|
GeForce GTX 950M | 372.77 frames/s |
Particle Simulation
GeForce GTX 960 | 710.39 mInteraction/s |
---|---|
GeForce GTX 950M | 450.1 mInteraction/s |
Thief
GeForce GTX 960 | 50.6 |
---|---|
GeForce GTX 950M | 19.5 |
Battlefield 4
GeForce GTX 960 | 58 |
---|---|
GeForce GTX 950M | 22.75 |
Bioshock Infinite
GeForce GTX 960 | 75. 8 |
---|---|
GeForce GTX 950M | 29.6 |
Crysis 3
GeForce GTX 960 | 36.1 |
---|---|
GeForce GTX 950M | 12.7 |
Tags:compare, GeForce GTX 950M, GeForce GTX 960
Compare NVIDIA GeForce GTX 950M vs NVIDIA GeForce GTX 960 which is better?
General information | |
Price-quality ratio The sum of all the advantages of the device divided by its price. The more%, the better the quality per unit price in comparison with all analogues. |
|
91.3%
40.1% (78.3%) better than |
51.2% |
Architecture |
|
Maxwell | Maxwell 2.0 |
Codename |
|
GM107 | GM206 |
Type |
|
For laptops | Desktop |
Release price |
|
n/a | 199 $ |
Number of shaders |
|
640 | 1024
384 (60%) better than |
Core clock |
|
914 MHz | 1127 MHz
At 213 MHz (23. 3%) better than |
Boost frequency |
|
1124 MHz | 1178 MHz
At 54 MHz (4.8%) better than |
Number of transistors |
|
1.870 million | 2.940 million |
Process |
|
28 nm | 28 nm |
Interface |
|
PCIe 3.0 x8 | PCIe 3.0 x16 |
Power Demand (TDP) Calculated thermal power shows the average heat dissipation in load operation, |
|
75W
-45 W (-37.5%) better than |
120 W |
Length |
|
n/a | 24.1 cm |
Additional power connectors |
|
n/a | 1x 6-pin |
G-SYNC 9 support0003 NVIDIA G-SYNC technology delivers a smooth gaming experience with variable refresh rates and the elimination of visual artifacts. |
|
SLI support |
|
+ | + |
3D Vision |
|
n/a | + |
GPU Boost |
|
+ | + |
GeForce Experience |
|
+ | + |
Vulkan NVIDIA’s Vulkan technology allows developers to gain low-level access to the GPU to optimize graphics commands (better than OpenGL and Direct3D APIs). |
|
n/a | + |
CUDA The CUDA architecture enables applications that are optimized for |
|
Surround |
|
n/a | + |
Adaptive Vertical Sync |
|
n/a | + |
Recommended power supply |
|
n/a | 400 Watt |
Multi-monitor support |
|
n/a | 4 |
Ansel |
|
Decred / DCR (Decred) |
|
n/a | 0. 92 Gh/s |
Zcash / ZEC (Equihash) |
|
n/a | 1 Sol/s |
Bus |
|
PCI Express 3.0 | PCI Express 3.0 |
Number of CUDA cores A large number of CUDA cores improve performance in graphics computing, |
|
640 | 1024
384 (60%) better than |
Height |
|
n/a | 11.1 cm |
HDCP |
|
n/a | + |
Maximum resolution via VGA |
|
n/a | 2048×1536 |
Audio input for HDMI |
|
n/a | internal |
GameStream |
|
+ | + |
GeForce ShadowPlay |
|
GameWorks |
|
HDMI |
|
BatteryBoost |
|
+ | no data |
VGA analog monitor support |
|
+ | no data |
DisplayPort Multimode (DP++) support |
|
+ | n/a |
Video decoder H. 264, VC1, MPEG2 1080p |
|
+ | no data |
Adaptive VSync |
|
+ | no data |
DSR |
|
+ | no data |
Video connectors |
|
No outputs | Dual Link DVI-I, HDMI 2.0, 3x DisplayPort 1.2 |
DirectX |
|
12 (11_0) | 12 (12_1) |
Floating point performance |
|
1.439 gflops | 2.413 gflops |
Optimus |
|
+ | no data |
Ethereum / ETH (DaggerHashimoto) |
|
2.5 Mh/s | 8 Mh/s |
Memory | |
Memory type |
|
DDR3 or GDDR5 | GDDR5 |
Maximum memory Large video memory allows you to run demanding games with lots of textures, |
|
4 GB | 4 GB |
Memory bus width The larger the video memory bus width, the more data is transferred to the GPU per unit of time and the better performance in demanding games. |
|
128 bit | 128 bit |
Shared memory |
|
— | — |
Memory frequency A high memory frequency has a positive effect on the speed of a video card with a large amount of data. |
|
1000 MHz
At 993 MHz (14185.7%) better than |
7 MHz |
Memory bandwidth The higher the data transfer bandwidth, the more effective amount of RAM the PC can use. |
|
32 | 112
80 (250%) better than |
Comparison of Asus gtx 960 vs gtx 950 VU with Aliexpress / Phleyd
arablionz. cc
Comparison of Asus gtx 960 vs gtx 950 VCU with Aliexpress / Phleyd
معاينة
Comparison of video cards GT 640 1gb VS GT 630 4gb!
معاينة
PCI-e dependence of video cards (comparison and analysis of PCI-e x1 vs x16)
معاينة
motherboard asus p8h61-m lx with aliexpress
معاينة
2 times cheaper! ASUS ROG Phone 3 Tencent Edition for China. What’s the catch? / COMPARISON / OVERVIEW
معاينة
Market GTX 1060 6 (18 graphics cards!)
معاينة
Cách tải và cài Driver cho máy tính bàn Asus (Download Asus Motherboard drivers for Windows)
معاينة
How To Download ASUS any model laptop driver in Official website Example ASUS X541UV
معاينة
Firmware for tablet Asus K017 (ASUS MeMO Pad 7 ME170C) on Android 5.0
معاينة
Review and opening Asus VivoBook Max X541SA (Asus X541 Series)
معاينة
Disassembling Asus X556 + replacement HDD / Disassembling laptop Asus X556U
معاينة
Asus QoS Packets — Dispatcher and Monitor QoS Traffic on Asus
Router
معاينة
HOW DID ASUS UPDATE EARS? ✔ Review of Gaming Headphones Asus Cerberus v2
معاينة
Hard Reset Asus K012 (Asus FonePad 7 FE170CG)
معاينة
Where to get the latest drivers for AMD
graphics cards
معاينة
#Asus K53 laptop upgrade with client | How to upgrade Asus K53
معاينة
192. 168.1.1 (http://router.asus.com) | ASUS Wi-Fi 9 router setup0003
معاينة
JayzTwoCents Global Card Giveaway! RTX 3080!
معاينة
Picked up AMD drivers for video cards hd 7870 and r9 270, removed blue screens of death
معاينة
Surviving on Intel UHD 630 Integrated Graphics in Core i5-10400: Waiting for New
Graphics Cards
معاينة
Draw of two Palit video cards and assembly of HYPERPC LUMEN from the first person (FPV)
معاينة
Notebook ASUS R540LJ X540LJ. Review, unpacking, testing. Review Asus R540LJ
معاينة
how to disassemble Asus X53S to clean the heatsinks from dust. How to take apart a laptop notebook Asus X53S
معاينة
ASUS X556 laptop keyboard replacement. Replacing the keyboard on a laptop ASUS X556
معاينة
A test of the two undeniably best budget graphics cards of 2020! RX570 vs RX580 with 4GB. Overclocking and optimization
معاينة
Asus RT-AC68U Disassemble and Repair / Asus RT-AC68U Router Disassemble and Repair
معاينة
Cleaning and Disassemble ASUS A52J
معاينة
Which GTX 1060 should I buy? — Market all GTX 1060 graphics cards
معاينة
GTX 750 Ti from AliExpress!!
معاينة
Player with Aliexpress
معاينة
Video card MUTANT with Aliexpress
معاينة
INTERESTING SHOPPING WITH ALIEXPRESS
معاينة
BEAUTIFUL LINGERIE WITH ALIEXPRESS
معاينة
Unboxing ASUS X541NA / Unboxing ASUS X541NA
معاينة
Overview of RAM with Aliexpress DDR2 4Gb
معاينة
Cool automation with aliexpress for a penny!
معاينة
alseye fan 120 mm 4pin pwm with aliexpress
معاينة
How to place an order for aliexpress aliexpress. com?
معاينة
CHEAP 4G ROUTER FOR VIDEO SURVEILLANCE WITH ALIEXPRESS
معاينة
Shopping with Aliexpress to be
معاينة
TOP-12 products for gel polish manicure with Aliexpress
معاينة
Car accessories for VW Caravelle T4 Car accessories with Aliexpress for volkswagen t4
معاينة
Unpacking and checking. PWM controller VIPER22A with aliexpress
معاينة
TV With Aliexpress Thomson Thomson 22 full hd
معاينة
Remote control for LG TV (3d Smart TV) from China (with Aliexpress)
معاينة
ROBOT ARTIST WITH ALIEXPRESS, WILL TEACH YOU TO DRAW!
معاينة
Beach DDR2 memory from Aliexpress # Check and my opinion
معاينة
PTZ WIFI CAMERA WITH 5X OPTICAL ZOOM WITH ALIEXPRESS FOR $50
معاينة
HOW TO APPLY ALIEXPRESS COUPON IN 2021?
معاينة
Miracle triac BT-136 600E with aliexpress review
معاينة
2N4401 NPN Bipolar Transistor — Unboxing from AliExpress
معاينة
GTX 750 Ti for 3000r with Aliexpress DRAGGING! Review, overclocking, tests
معاينة
10 COOL GOODS FOR AUDI A4 WITH ALIEXPRESS. TUNING AUDI A4 B5!
معاينة
NUMBER ONE FOR ALIEXPRESS I Legendary Portable MIFA A10
معاينة
PARKING CAMERA WITH ALIEXPRESS PTZ
معاينة
PI#DETS!!! WHAT I FOUND FOR LIFAN SMILY (LIFAN SMILY) ON ALIEXPRESS (320 330)
معاينة
Former flagship LG G3 for $100 with Aliexpress — everything works, BUT … review of ref
معاينة
15 GOODS FOR SPORTS. USEFUL DEVICES AND SIMULATORS FOR TRAINING WITH ALIEXPRESS
معاينة
DENIM FABRIC FOR WORKWEAR ON ALIEXPRESS [REVIEW-REVIEW 2021]
معاينة
✅ Great webcam! How to install and configure HD Webcam Logitech + obs / with Aliexpress
معاينة
oh those 2 gigabytes! GECID.com. Page 1
::>Video cards
>2019
> Gameplay testing of the video card NVIDIA GeForce GTX 960 2GB in 30 games: wow, those 2 gigabytes!
15-03-2019
Page 1
Page 2
One page
The GeForce GTX 960 was released in January 2015. Previously, GeForce GTX 980 and GTX 970 video cards appeared on the 28-nm Maxwell 2.0 microarchitecture, so it did not bring anything new and unusual. However, many have been able to experience the benefits of VGI global illumination, MFAA, Dynamic Super Resolution and other innovations in a $199 MSRP, 120W TDP graphics card.
Therefore, to this day it does not leave the top five most popular video accelerators among Steam users. That is, it can often be found at a flea market. And when buying a used version, at least two questions immediately arise. First: «How well does she handle current games?» After all, most of the tests fell on 2015-16, and since then a lot of new and interesting things have come out.
Second question: What are her weaknesses? Its main Achilles’ heel is video memory. Initially, the card was released in a 2 GB version with a 128-bit bus, an effective frequency of 7 GHz and a bandwidth of 112 GB / s. In the spring of the same year, 4 GB versions debuted, and in the fall, unofficial information appeared that NVIDIA and partners would gradually release 2 GB versions.
Nevertheless, both 2 and 4 GB versions can be found on the secondary market. We didn’t have a single one in our bins, but thanks to our colleagues from the Overclockers.ua project. They borrowed an EVGA GeForce GTX 9 graphics card for testing.60 SuperSC ACX 2.0+. We tested a similar version from EVGA with the same cooler and higher factory overclock.
The card is based on the NVIDIA GM206-300 GPU. It has 1024 CUDA cores, 64 texture units and 32 raster units. Clock speeds are increased by almost 14% in the factory compared to the benchmark. GDDR5 video memory with a total capacity of 2 GB operates at a reference effective speed of 7 GHz.
Cooling is entrusted to a two-slot cooler, the design of which includes a copper base, three 8 mm copper heat pipes, a two-section aluminum radiator and a pair of 92mm axial fans. In games, the GPU temperature did not reach 75 ° with a critical indicator of 95 °.
The following stand was used for testing:
- Intel Core i7-7740X
- Thermaltake Water 3. 0 Riing RGB 240
- ASUS TUF X299 MARK 1
- 2 x 8 GB DDR4-2133 G.SKILL Sniper X
- Apacer PANTHER AS330 240 GB / 960 GB
- Seagate ST2000DX001 2TB
- Seasonic Snow Silent 1050 1050W
- Thermaltake Core P3
- AOC U2879VF
An external system with AVerMedia Live Gamer 4K was used to record gameplay in Full HD resolution, i.e. without loss of performance.
A small remark: in most cases, the GTX 960 is used in simpler configurations, so the processor runs at nominal frequencies, and the memory starts in basic mode, without activating the XMP profile with overclocking.
And one more important point. After releasing the first tests of retro video cards, we thought and decided to make them even more useful for you by adding an element of comparison with a new video accelerator of similar performance. So that current owners of the GTX 960 have a guideline for future upgrades.
To do this, we have already taken out the Colorful iGame GTX 1050 Ti U-4G video card with a 2-fan cooler from our bins. Its GPU has fewer structural blocks: only 768 CUDA cores, 48 texture and 32 raster, but of the newer 14-nm Pascal microarchitecture. To even out their chances a bit, we activated the factory overclocking of the GPU. It also pleases with 4 GB of GDDR5 memory, which operates at the same effective frequency of 7 GHz with a 128-bit bus.
But fewer words and more tests. The PUBG takes up more than 2 GB of VRAM at low settings, so the system with a GTX 960 increases the load on RAM. This does not have a critical impact on speed performance: plus or minus 2-3 FPS will not make any special weather.
A similar situation occurs in Kingdom Come: Deliverance . Monitoring the GTX 1050 Ti shows that the game requires about 2. 5 GB of VRAM at high settings, so the lack of 9The 60th compensates from RAM. The gain of a newer video card was only 1-2 frames / s, which is equivalent to 4-6%.
The Evil Within 2 requires more than 2.5 GB of video memory at the medium preset, but the overall picture does not change: the GTX 1050 Ti still only pulls ahead by 1-2 FPS.
An interesting situation occurs in The Crew 2 . At medium settings, the game requires less than 2 GB of video memory, but for some reason it cannot fully load the GPU 960th. Perhaps this was the reason for the significant difference, especially in the statistics of rare events.
Far Cry 5 perfectly showed the weakness of a 2 GB video card when running actual blockbusters. The medium preset requires more than 3 GB of video memory, so the GTX 1050 Ti with fewer structural blocks, but a higher GPU frequency and a 4 GB buffer did not leave the competitor a single chance. For example, her 0.1% Low indicator is almost 2 times higher.
Therefore, if you plan to replace the GTX 960, then look towards the GTX 1060 or RX 570. Buying 1050 Ti for WoT, CS: GO or other undemanding games will be akin to replacing an awl with soap — you can only feel the difference in really heavy blockbusters.
And if you are a current or potential owner of a 2 GB GTX 960, then let’s see what it can do in the realities of early 2019. Fans of The Witcher and GTA 5 — don’t get mad, these games weren’t included in the test, but they were in the last video.
And more disappointing fans Forza Horizon 4 — the new version of FPS Monitor did not want to be built into this game. It starts up without problems — the video sequence pleases with smoothness, and the controls are responsive, but we cannot share any speed indicators.
But with World of Tanks monitoring is no longer capricious. With the ultra preset, the game requires more than 2 GB of video memory, and with a high preset, we just fit into the limit. You can move quickly and hit even on the LT, and you can only deal damage with the permission of the VBR. But there are no questions about the system itself.
War Thunder can be played comfortably with the Cinema profile. In the process, the 0.1% Low indicator dropped to 20 FPS several times, but this did not affect the gameplay itself. The rest is quiet and smooth.
From ARK : Survival Evolved burns for many people for various reasons, but the game is still popular, and we could not bypass it. Already with an average preset, it requires more than 2 GB of video memory. Perhaps this is the reason for the resulting friezes. You can get rid of them by reducing the render scale, but the picture will be soapy, or by more subtle selection of settings. If you know exactly which ones, then share in the comments.
Nvidia GeForce GTX 950 review and test: a ticket to the middle class
Table of contents
- Introduction
- Specifications
- Review Palit GeForce GTX 950 StormX Dual
- Appearance and dimensions
- PCB
- Cooling system
- Test bench
- Instrumentation and Test Method
- Play tests
- Cooling System Potential Study
- Details
- Electricity consumption level
- Test results
- Company Of Heroes II
- Metro Last Light
- Sleeping Dogs
- Sniper Elite III
- Thief (2014)
- Tomb Raider (2013)
- Total War: Rome II
- Far Cry III
- Crysis 3
- Battlefield 4
- Grand Theft Auto V
- The Witcher 3: Wild Hunt
- Average number of frames
- Conclusion
Introduction
Video cards in the $150-200 price range are extremely popular these days. The dollar is rising, purchasing power is falling. But does it make sense to change a two-three-year-old model for a new one? The issue is serious and complex. Sell an existing one and add for an upgrade? It’s possible, but the cost is intimidating. And yet, if you take a chance, what to choose from?
However, progress does not stand still, there are suitable solutions for such users. So, today Nvidia announced another affordable video card worth $160 — GeForce GTX 950.
It is based on the well-known GM206 graphics core, which was further truncated and left with only 768 CUDA execution cores. Otherwise, it copies the twin video card — GeForce GTX 960. Although, according to the technical data, GPU Boost is set to slightly higher frequencies. And so that in heavy modes the novelty does not approach the opponent, the memory frequency was set as 1650 MHz (instead of 1750 MHz). For dessert, we will get video cards ready for further overclocking: the PWM controller does not change, the recognition by utilities is excellent, the BIOS can be easily modified to increase the TDP level. Good prospects open up for $160.
Only one fact is confusing — the GeForce GTX 750 Ti is too close in price to the new product, perhaps Nvidia will revise its pricing policy and reduce the price of the first-born Maxwell. In the meantime, I’ll tell you more about the GeForce GTX 950. The company developed this video card specifically for MOBA games (Dota 2, League of Legends and others). To do this, engineers and programmers concentrated on solving a number of specific problems. According to Nvidia, the team was able to reduce the Input Lag (response time) between player actions and manipulators by 35ms. From my point of view, this was mostly due to an increase in the performance of the video card itself. The second leverage is the reduction of pre-rendered frames. Theoretically, this should lead to jagged transitions, but if the performance does not fall below 60 fps, then this specific thing is not visible.
It turns out that all solutions have been reduced to increasing productivity, which, in principle, is not bad at all. We do not promise a direct comparison of the GeForce GTX 650 and GTX 950, but we tried to add a three-year-old model to the list of gaming video cards. Perhaps it’s time to start reviewing new items using the Palit GeForce GTX 950 StormX Dual as an example.
recommendations
In addition, Nvidia continues to develop the GeForce Experience utility. In the near future, a new feature will appear in it, which allows you to invite a friend and show him what is happening to you in the game. And you can join a friend’s game and use the voice chat features. Unfortunately, we did not receive the utility itself, but I am sure that the innovations will be useful to MOBA players. Obviously, instead of group chats and Skype calls, everything will be integrated into a single program.
Specifications
Name |
Radeon R7 370 |
GeForce GTX 750 Ti |
GeForce GTX 950 |
GeForce GTX 960 |
Codename |
Pitcairn |
GM107 |
GM206 |
GM206 |
Version |
GCN 1. 0 |
Maxwell 1.x |
Maxwell 2.x |
Maxwell 2.x |
Process technology, nm |
28 |
28 |
28 |
28 |
Core size/cores, mm 2 |
212 |
148 |
227 |
227 |
Number of transistors, million |
2800 |
1870 |
2940 |
2940 |
Core frequency, MHz |
— |
1020 |
1024 |
1126 |
Core clock (Turbo), MHz |
975 |
1085 |
1188 |
1178 |
Number of shaders (PS), pcs. |
1024 |
640 |
768 |
1024 |
Number of texture units (TMU), pcs. |
64 |
40 |
48 |
64 |
Number of ROPs, pcs. |
32 |
16 |
32 |
32 |
Maximum fill rate, Gpix/s |
31 |
16.3 |
32.8 |
36 |
Maximum texture fetch rate, Gtex/s |
64 |
40.8 |
49.2 |
72. 1 |
Memory type |
GDDR5 |
GDDR5 |
GDDR5 |
GDDR5 |
Effective memory frequency, MHz |
1400 |
1350 |
1650 |
1750 |
Memory, GB |
2 |
2 |
2 |
2 |
Memory bus, bit |
256 |
128 |
128 |
128 |
Memory bandwidth, GB/s |
179 |
86.4 |
105. 6 |
112.2 |
Power, connectors Pin |
6 |
— |
6 |
6 |
Power consumption (2D / 3D), Watt |
-/110 |
-/60 |
-/90 |
-/120 |
CrossFire/Sli |
V |
— |
V |
V |
Announcement price, $ |
150 |
150 |
160 |
200 |
Replacement model |
Radeon R7 265 |
GeForce GTX 650 Ti |
GeForce GTX 750 Ti |
GeForce GTX 760 |
Review Palit GeForce GTX 950 StormX Dual
Appearance and dimensions
Model |
A, mm |
b, mm |
c, mm |
D, mm |
A1, mm |
b1, mm |
C1, mm |
Palit GeForce GTX 950 StormX Dual |
208 |
98 |
35 |
75 |
215 |
101 |
39 |
A — length of the printed circuit board, excluding the cooling system and the bracket for video output ports.
B PCB width, excluding PCI-E pins and cooling system.
C — height from the horizontal plane of the printed circuit board to the level of the upper surface of the cooling system.
D – diameter of the fan/s along the outer radius.
A1 – length of the printed circuit board, including the cooling system (if it extends beyond the printed circuit board) to the bracket for video output ports.
B1 – width of the printed circuit board, excluding PCI-E pins, but including the measurement of the cooling system (if it extends beyond the printed circuit board).
1 — height, taking into account the back plate (if any) / radiator mounting screws to the level of the upper surface of the cooling system. If it is lower than the height of the back plate of the video output ports, then the height is measured to the top point of the bar.
GeForce GTX 950 graphics cards will borrow the circuit board and cooling of GeForce GTX 960 is a fact. After all, there is no point in making a special PCB and changing something for manufacturers. Therefore, many GeForce GTX 960 reviews automatically answer some questions.
But keep in mind that the power consumption of the novelty is reduced relative to the GeForce GTX 960, so if the cooling system migrates from the older model, it will be great. I’ve also noticed that some manufacturers couldn’t forgo the extra savings by removing $1 heatpipes from their heatsinks.
As for video outputs, here we are waiting for a standard set of ports: two DVI, one each HDMI and DisplayPort.
PCB
Palit’s
PCBs have always been based on in-house developments. If only because there is no reference design for the GeForce GTX 950.
So the company took the GTX 960 PCB as a base and simplified it a bit. The GPU power phase got under the knife. Instead of four, only three were left.
It’s easy to calculate that the 120W Palit version has four phases, while the reference model GeForce GTX 950 (90W) has three. In total, according to the calculations of Palit engineers, one phase provides 30 watts. In overclocking, the video card consumes up to 150 watts, at standard frequencies 100 watts, and there is still a margin.
Another thing is that there is no heatsink on the VRM, not at all. It is cooled by the oncoming air flow. Despite the fact that this does not lead to overheating in a closed case, I would be afraid to leave it without proper cooling and overclocking. It is also sad that the holes for the radiator are still provided. It is possible that there will be video cards with it in retail sales.
GPU Phase Controller — NCP81174. The PWM controller is common, supported by third-party utilities and quite simple. The maximum voltage set via BIOS is 1.21-1.23 V. Normally, the GPU is powered by a voltage of 1.13 V. To further increase it, you need a voltmod with a variable resistor.
Four chips manufactured by Samsung, giving a total of 2 GB of memory. They are rated up to 1750 MHz, but operate at 1650 MHz. We all know how good memory controllers are at Nvidia, so its average overclock on modern video cards often reaches 2 GHz.
And two more unused memory sites — a reserve for the future. I can’t help but think that sooner or later (with an adequate response from AMD) Nvidia may release a video card with a bus width of 196 bits. So far, the GeForce GTX 950 and GTX 960 are running at 128 bits.
GPU GM206 is used in two versions. The first is for the GeForce GTX 960 video card with 1024 CUDA cores. In the novelty, their number has been reduced to 768 pieces. GPU area is 227mm 2 , which is even more than the competing Radeon R7 370 (212 mm 2 ).
The nominal frequencies of the video card are 1064 MHz (with GPU Boost up to 1240 MHz) for the GPU and 1650 MHz for the memory. The graphics core contains 48 texture units and 32 bitmap operations units.
Cooling system
For Palit GeForce GTX 950 StormX Dual, a simple cooling scheme has been chosen, consisting of an elementary radiator without heat pipes with a pair of 75 mm fans. The dimensions of the cooling system are almost the same as the dimensions of the printed circuit board.
The shroud can be easily removed without even unscrewing the screws from the heatsink. Therefore, cleaning is convenient. Both fans are able to stop in idle and partial loads.
The radiator looks like a 2010s alien. It’s a piece of aluminum with dozens of ribs.
The design is elegant and simple, but it should have been given more attention. After all, such a miracle will have to dissipate almost 80 watts of heat from a small surface.
From the side it looks like a toy, because the height of the ribs is only 6-7 mm. I think I know the answer to the question of how he manages to cool the GPU.
Two 75mm progressive blade fans designed to deliver maximum air volume at reduced speeds. True, in addition to the GPU, they need to manage to deliver life-giving flows to the VRM zone, which does without a radiator at all.