EVGA’s booth was among the few hardware exhibitors carrying new product at PAX West. The company’s DG-7 series is finally nearing completion, now going on a year of press coverage, and has one final round of showings prior to a November launch. With that final round, EVGA has begun showing white and white/black two-tone versions of the high-end DG-77. The tooling is the same, it’s just a matter of color preference.
The DG-77 was on show again at PAX West, now in white, and included some semi-finalized specifications for November launch. The DG-77 should likely include four fans – we’re not sure on sizes, but probably 120mm – with support for 280mm front radiators (potentially up to 360mm, unconfirmed) and 240mm top radiators. A single rear exhaust port is also available at 120mm, and likely will be populated stock. The case market is competitive enough right now to demand a $100-$130 price range on the enclosure, but EVGA hasn’t finalized pricing just yet.
Going hands-on at PAX West 2017, we stopped by Logitech’s booth to get more technical details on the Logitech G613 wireless keyboard, G603 wireless mouse, and some follow-up information on the PowerPlay mat and G903/G703 mice. The latter set of information will go live in our pending-publication review. The former is up for discussion today.
Both devices leverage the same wireless hardware used in the G900 mouse, which we previously reviewed and found to perform equivalently or superior to high-end wired mice. The myth of “wireless is always slower” was immolated by that product series, mummified and entombed alongside other black magic gamer peripheral mythology. The G613 is the first high-performance wireless keyboard that we’re aware of, levying Logitech’s Romer G switches (which feel similar to o-ring damped browns) and two modes of wireless connectivity. These include Bluetooth and Logitech’s now-standard high-performance wireless setup, dubbed “Lightspeed.” Interestingly, these two systems can be used asynchronously to create an ad-hoc KVM, switching to wireless for the high-performance machine (e.g. gaming box), then Bluetooth for the accompanying streaming box or compression machine. This, we think, is the most marketable feature of the G613, and so happens to also exist on the new G603.
Ask GN serves as a consistent format in our video series, now 57 episodes strong. We are still filming at a pace of roughly one Ask GN episode every 1-2 weeks, so if you’ve got questions, be sure to submit them in the YT comments section.
This week’s episode gives a brief break from the deeper overclocking, undervolting, and benchmarking topics of late. We briefly visit Pascal temperature response observations, a user’s chipped GPU (and our own tech battle scars), and talk monitor overclocking. The article referenced during the monitor OC section can be found here.
This is just a quick PSA.
We shot an off-the-cuff video about software misreporting Vega’s frequency, to the extent that a “1980MHz overclock” is possible under the misreported conditions. The entire point of the video was to bring awareness to a bug in either software or drivers – not to point blame at AMD – explicitly to ensure consumers understand that the numbers may be inaccurate. Some reviews even cited overclocks of “1980MHz,” but overlooked the fact that scaling ceases around the threshold where the reporting bugs out.
Following the initial rumors stemming from an Overclockers.co.uk post about Vega price soon changing, multiple AIB partners reached out to GamersNexus – and vice versa – to discuss the truth of the content. The post by Gibbo of Overclockers suggested that launch rebates and MDF would be expiring from AMD for Vega, which would drive pricing upward as retailers scramble to make a profit on the new GPU. Launch pricing of Vega 64 was supposed to be $500, but quickly shot to $600 USD in the wake of immediate inventory selling out. This is also why the packs exist – it enables AMD to “lower” the pricing of Vega by making return on other components.
In speaking with different sources from different companies that work with AMD, GamersNexus learned that “Gibbo is right” regarding the AMD rebate expiry and subsequent price jump. AMD purportedly provided the top retailers and etailers with a $499 price on Vega 64, coupling sale of the card with a rebate to reduce spend by retailers, and therefore use leverage to force the lower price. The $100 rebate from AMD is already expiring, hence the price jump by retailers who need return. Rebates were included as a means to encourage retailers to try to sell at the lower $499 price. With those expiring, leverage is gone and retailers/etailers return to their own price structure, as margins are exceptionally low on this product.
Tearing open the RX Vega 56 card revealed more of what we expected: A Vega Frontier Edition card, which is the same as Vega 64, which is the same as Vega 56. It seems as if AMD took the same PCB & VRM run and increased volume to apply to all these cards, thereby ensuring MOQ is met and theoretically lowering cost for all devices combined. That said, the price also increases in unnecessary ways for the likes of Vega 56, which has one of the most overkill VRMs a card of its ilk possibly could -- especially given the native current and power constraints enforced by BIOS. That said, we're working on power tables mods to bypass these constraints, despite the alleged Secure Boot compliance by AMD.
We posted a tear-down of the card earlier today, though it is much the same as the Vega: Frontier Edition -- and by "much the same," we mean "exactly the same." Though, to be fair, V56 does lack the TR6 & TR5 screws of FE.
Here's the tear-down:
Storing multiple terabytes of video content monthly is, obviously, a drive-intensive business -- particularly when using RAID for local editing scratch disks, a NAS for internal server access, and web remote backup. Rather than buy more drives and build a data library that is both impossible to manage and impossible to search, we decided to use our disks smarter and begin compressing broll as it falls into disuse. Deletion is the final step, at some point, but the compression is small enough as to be a non-concern right now. We're able to compress our broll anywhere from 50-86%, depending on what kind of content is contained therein, and do so with nearly 0 perceptible impact to content quality. All that's required is a processor with a lot of threads, as that's what we wrote our compression script to use, and some extra power each month.
Threadripper saw use recently in a temporary compression rig for us, as we wanted to try the CPU out in a real-world use case for our day-to-day operations. The effort can be seen below:
Computers have come a long way since their inception. Some of the first computers (built by the military) used electromagnets to calculate torpedo trajectories. Since then, computers have become almost incomprehensibly more powerful and accessible to the point at which the concept of virtual reality headsets aren’t even science fiction.
In gaming PCs, these power increases have often been used to ensure higher FPS, faster game mechanics, and more immersive graphics settings. Despite this, the computational power in modern PCs can be used for a variety of applications. Many uses such as design, communication, servers, etc. are well known, but one lesser known use is contributing to distributed computation programs such as BOINC and Folding@Home.
BOINC (Berkeley Open Infrastructure for Network Computing) and Folding@home (also sometimes referred to as FAH and F@H) are research programs that utilize distributed computing to provide researchers large amounts of computational power without the need of supercomputers. BOINC allows for users to support a variety of programs (including searching for extraterrestrial life, simulating molecular simulations, predicting the climate, etc.). In contrast, Folding@home is run by Stanford and is a singular program that simulates protein folding.
First we’ll discuss what distributed computing is (and its relation to traditional supercomputers), then we’ll cover some noteable projects we’re fond of.
Visiting AMD during the Threadripper announcement event gave us access to a live LN2-overclocking demonstration, where one of the early Threadripper CPUs hit 5.2GHz on LN2 and scored north of 4000 points in Cinebench. Overclocking was performed on two systems, one using an internal engineering sample motherboard and the other using an early ASRock board. LN2 pots will be made available by Der8auer and KINGPIN, though the LN2 pots used by AMD were custom-made for the task, given that the socket is completely new.
This episode of Ask GN (#56) revisits the topic of AMD's Temperature Control (TCTL) offset on Ryzen CPUs, aiming to help demystify why the company has elected to implement the feature on its consumer-grade CPUs. The topic was resurrected with thanks to Threadripper's imminent launch, just hours away, as the new TR CPUs also include a 27C TCTL offset. Alongside this, we talk Threadripper CPU die layout diagrams and our use of dry erase marker (yes, really), sensationalism and clickbait on YouTube, Peltier coolers, Ivy Bridge, and more.
For a separate update on what's going on behind the scenes, our Patreon backers may be happy to hear that we've just posted an update on the Patreon page. The update discusses major impending changes to our CPU testing procedure, as Threadripper's launch will be the last major CPU we cover for a little while. Well, a few weeks, at least. That'll give us some time to rework our testing for next year, as our methods tend to remain in place for about a year at a time.
We moderate comments on a ~24~48 hour cycle. There will be some delay after submitting a comment.