Networking and Storage Performance

We have recently started devoting a separate section to analyze the storage and networking credentials of the units under review. On the storage side, one option would be repetition of our strenuous SSD review tests on the drive(s) in the PC. Fortunately, to avoid that overkill, PCMark 8 has a storage bench where certain common workloads such as loading games and document processing are replayed on the target drive. Results are presented in two forms, one being a benchmark number and the other, a bandwidth figure. We ran the PCMark 8 storage bench on selected PCs and the results are presented below.

Futuremark PCMark 8 Storage Bench - Score

Futuremark PCMark 8 Storage Bench - Bandwidth

The OCZ Vector drive we used in our setup has been EOL-ed by OCZ, but there are plenty of similarly performing drives with similar costs in the market.

On the networking side, we restricted ourselves to the evaluation of the WLAN component. Our standard test router is the Netgear R7000 Nighthawk configured with both 2.4 GHz and 5 GHz networks. The router is placed approximately 20 ft. away, separated by a drywall (as in a typical US building). A wired client (Zotac ID89-Plus) is connected to the R7000 and serves as one endpoint for iPerf evaluation. The PC under test is made to connect to either the 5 GHz (preferred) or 2.4 GHz SSID and iPerf tests are conducted for both TCP and UDP transfers. It is ensured that the PC under test is the only wireless client for the Netgear R7000. We evaluate total throughput for up to 32 simultaneous TCP connections using iPerf and present the highest number in the graph below.

Wi-Fi TCP Throughput

In the UDP case, we try to transfer data at the highest rate possible for which we get less than 1% packet loss.

Wi-Fi UDP Throughput (< 1% Packet Loss)

The numbers are similar to what we obtained for other systems with the Intel AC-3160 WiFi 802.11ac PCIe WLAN card. The external antenna helps in provideing better performance.

Gaming Benchmarks HTPC Credentials
Comments Locked

88 Comments

View All Comments

  • KateH - Monday, September 28, 2015 - link

    I would be very curious to hear more about the GPU rebranding situation... why would a 1280-shader GM204 on an MXM card be a 970m in a laptop but a 960 non-M in a SFF? Why would Nvidia/Zotac go to the trouble of editing the VGA BIOS and drivers to make this GM204 show up as a 960 when there are already loads of MXM 970m's that are functionally identical to this aside from re-badging? The OEM GPU re-branding situation is ridiculous; Zotac/Nvidia have created a doubly confusing situation where this card could be easily confused for either a significantly-slower GM107-based GTX 960m (that's itself a rebadged 860m) or a slightly-slower GM206 GTX 960 that has the potentially-important HEVC decode that's actually not present in this "960".
  • KateH - Monday, September 28, 2015 - link

    And while I'm on a rant, re-badging between generations is ridiculous too- but I know by now that's a losing battle that's only getting worse. FFS.
  • mapesdhs - Monday, September 28, 2015 - link

    A lot of that going on by all sides, but it's hard to discuss without enraging rival armies of haters and fanboys. We'd be a lot better off if nobody did it. What really bugs me is the massive performance overlap of newer lesser models vs. older models. The naming system allows one to infer that a newer card will have a particular level of basic performance, but the reality is often very different. I benchmarked a 650 Ti recently, was amazed to find it often failed to beat an old GTX 460.
  • lmcd - Tuesday, September 29, 2015 - link

    I mean the 650 Ti should be like 2/3 the power consumption at most, no?
  • KateH - Tuesday, September 29, 2015 - link

    Yeah, something like that. ~100-120W for a 650Ti vs ~150-170W for a 460. The 660 is in the same power envelope as the 460 and should outperform it by a fair margin
  • rtho782 - Tuesday, September 29, 2015 - link

    You're perfectly right. Having a separate mobile product stack made sense when mobile gpus were way behind desktop ones, now they use the same silicon, less so.

    I think we should have the same product names and tiers for both, perhaps use the "m" suffix in cases where the clockspeed is much lower in the laptop variant.
  • KateH - Tuesday, September 29, 2015 - link

    I kinda wonder if it's not time to do away with the "M" suffix for GPUs altogether and move towards segmentation based on power, like what Intel has done with their K/S/H/Y/U suffixes. Low-power MXM/onboard GPUs are by no means strictly in the realm of notebooks anymore- AIO and SFF computers are using them more and more. And looking at AMD/NV's product stacks, "desktop" GPUs cover ~15W-250W (with all but the top-end being under ~150W) and "mobile" GPUs cover ~15W-125W- that's a whole lot of overlap.
  • ruthan - Tuesday, September 29, 2015 - link

    Better than Macmin, but otherwise is better build own, even if MXM is not possible to use by us second category people..
  • adithyay328 - Thursday, October 1, 2015 - link

    Those specs actually almost give my mid tower desktop a run for it's money-almost.
  • aj654987 - Friday, October 2, 2015 - link

    Well, for the alienware alpha with the 860m and the T series processors (Haswell 35W), the CPU's are almost all GPU limited, even the i3's. So there is room for a higher powered GPU.

    With going broadwell, the lowest desktop CPU is 65 watts so far, which is probably too high for that small case, so their only choice is a 15 watt mobile chip.

Log in

Don't have an account? Sign up now