Sunday, November 23, 2014

IT News Head Lines (AnandTech) 11/24/2014

AnandTech



HGST Deskstar NAS 4 TB Review
The increasing affordability of SSDs has put a strain on the traditional market for hard drive vendors. However, new opportunities have opened up, thanks to the rapid growth in the SMB / SOHO / consumer NAS market. Every hard drive vendor now has a lineup to target this market. Today, we will be looking at HGST's offering in the desktop NAS space, the HGST Deskstar NAS


Read More ...




Cooler Master V1200 Platinum Power Supply Review
Cooler Master is one of the oldest and most reputable companies that offer advanced cooling and power solutions. If you are a PC techie, chances are you've owned at least one of their products in the past. Today we are going to look at their current flagship PSU, the V1200 Platinum, and see how it fares in today's demanding market.


Read More ...




AMD Announces Carrizo and Carrizo-L, Next Gen APUs for H1 2015
Today AMD is announcing the long anticipated upgrade to Kaveri, codenamed Carrizo. Carrizo is the natural successor to Kaveri, featuring x86 ‘Excavator’ cores alongside a Radeon-class GPU and promising an increase in performance all around.  The second part of today’s announcement is for Carrizo-L, an SoC pairing “Puma+” (upgraded Beema) cores also with AMD’s R-series GCN GPUs and a FCH into a single package.  Both Carrizo and Carrizo-L will feature ARM Trustzone, giving potential hardware-based built-in security when used by developers.


The Excavator cores are an architectural improvement over Steamroller, but are fundamentally based on the original Bulldozer concept. Excavator will be AMD’s fourth iteration of the concept, following Bulldozer, Piledriver and Steamroller. This new generation of APUs are still set to be built on the 28nm Super High Performance process at Global Foundries, delaying AMD’s shift to 20nm, but AMD are still claiming that the new GPU in Carrizo is their best yet, giving better performance and efficiency than before.

Given AMD's discrete GPU lineup, the GPU for Carrizo could be based on AMD's latest GCN 1.2 architecture, which was first introduced in the desktop Tonga part earlier this year. GCN 1.2's lossless delta color compression algorithms help improve the performance in memory bandwidth limited scenarios, such as in APUs. This could result in a bigger-than-expected jump in performance, although we will wait until we can test to find out how much it helps.

The Carrizo platform will be fully HSA 1.0 compliant, compared to Kaveri which only had ‘HSA Features’, as AMD puts it in their latest mobility roadmap update:


The push from AMD into HSA compliant APUs was well documented back at the launch of Kaveri earlier this year. This enabled the CPU and GPU components of the silicon, while under OpenCL 2.0 mode, to have access to the main block of system DRAM with zero-time copy functions, offering the potential for large classes of applications especially those in the prosumer and industry space to be accelerated by having instant access to the parallelization afforded by the GCN GPU. One of the big drawbacks of being an earlier adopter to HSA, as we noted at the time, was that software developers required time to bring their code to market, as well as AMD having to go out and teach the developers how to cater for HSA topology.

Both Carrizo and Carrizo-L on the mobile side will be targeted at the same power bands as Kaveri and Beema, although the socket will be new. The use of FP4 BGA also indicates that a single socket will cater for both the Excavator and Puma+ based APUs and would be interchangeable. A video by AMD’s VP/GM for Computing and Graphics, John Byrne, states that Carrizo and Carrizo-L are currently being tested internally ready for a 1H 2015 release, along with support for DirectX 12, OpenCL 2.0, Mantle and Freesync.


One of the big features that AMD is pushing with Carrizo is energy efficiency, with it being a keystone of the message. Because AMD have been on the same process node for a short while, they have to essentially follow the Maxwell example, by providing more performance for less power without the advantage of shrinking resistors. We were provided with an energy efficiency roadmap as well, showing the different methods AMD is using to achieve this:


One example of the efficiency improvement was provided by AMD’s Voltage Adaptive Operation. Rather than compensate for voltage variations which wastes energy, this technology takes the average operating voltage and detects when the voltage increases beyond a smaller margin. To compensate for this increase, the CPU speed is reduced until the voltage drops below the threshold and then the CPU speed is moved back up.


The changes in speed are designed to be so minute that it does not affect overall performance, however it might only take an errant voltage delivery component to consistently make the voltage go above that threshold, causing erratic slowdown that might be statistically significant. It will be interesting to see how AMD implements the latest version of this feature.


The 2015 desktop roadmap remains unpublished so far. AMD’s perception of a mobile-focused strategy would tend to suggest that the mobile comes first, with desktop following behind, although at this point it is unclear. A number of AMD’s marketing materials with this launch gave examples of the use of Carrizo and HSA for the prosumer, indicating that a desktop version should be announced in due course.

As of yet there was no discussion on the APUs to be launched, the speeds or the capabilities. All the roadmap tells us is 'up to four cores' (Excavator for Carrizo, Puma+ for Carrizo-L), some GCN compute units and 10-45W overall. There is no mention of DDR4 support, although the timeframe might be relevant for AMD to make the jump. Given the launch is still at least two quarters away, I would expect better details in due course. That timeframe fits in nicely around or just after Computex, perhaps indicating more details then.

Source: AMD


Read More ...




AMD Announces Upcoming Samsung FreeSync Displays
Today at AMD's Future of Compute event in Singapore, AMD announced partnerships with several companies. One of the more noteworthy announcements is that Samsung will be making FreeSync enabled displays that should be available in March 2015. The displays consist of the 23.6" and 28" UD590, and there will be 23.6", 28", and 31.5" variants of the UE850. These are all UHD (4K) displays, and Samsung has stated their intention to support Adaptive-Sync (and thereby FreeSync) on all of their UHD displays in the future.

FreeSync is AMD's alternative to NVIDIA's G-SYNC, with a few key differences. The biggest difference is that AMD proposed an extension to DisplayPort called Adaptive-Sync, and the VESA group accepted this extension as an amendment to the DisplayPort 1.2a specifications. Adaptive-Sync is thus an open standard that FreeSync leverages to enable variable refresh rates. As far as system requirements for FreeSync, other than a display that supports DisplayPort Adaptive-Sync, you need a supported AMD GPU with a DisplayPort connection and a driver from AMD with FreeSync support.

FreeSync is also royalty free, which should help manufacturers in controlling costs on FreeSync capable displays. There are other costs to creating a display that can support Adaptive-Sync, naturally, so we wouldn't expect price parity with existing LCDs in the near term. On the FreeSync FAQ, AMD notes that the manufacturing and validation requirements to support variable refresh rates without visual artifacts are higher than traditional LCDs, and thus cost-sensitive markets will likely hold off on adopting the standard for now. Over time, however, if Adaptive-Sync catches on then economies of scale come into play and we could see widespread adoption.

Being an open standard does have its drawbacks. NVIDIA was able to partner up with companies and develop G-SYNC and deploy it about a year ago, and there are now 4K 60Hz G-SYNC displays (Acer's XB280HK) and QHD 144Hz G-SYNC display (ASUS' ROG Swift PG278Q) that have been shipping for several months. In many ways G-SYNC showed the viability of adaptive refresh rates, but regardless of who gets credit the technology is quite exciting. If Adaptive-Sync does gain traction, as an open standard there's nothing to stop NVIDIA from supporting the technology and altering G-SYNC to work with Adaptive-Sync displays, but we'll have to wait and see on that front.

Pricing for the Samsung displays has not been announced, though the existing UD590 models tend to cost around $600 for the 28" version. I'd expect the Adaptive-Sync enabled monitors to have at least a moderate price premium, but we'll see when they become available some time around March 2015.


Read More ...




Intel Haswell-EP Xeon 14 Core Review: E5-2695 V3 and E5-2697 V3
Moving up the Xeon product stack, the larger and more complicated the die, the lower the yield. Intel sells its 14-18 core Xeons from a top end design that weighs in at over six billion transistors, and we have had two of the 14C models in for review: the E5-2695 V3 (2.3 GHz, 3.3 GHz turbo) and E5-2697 V3 (2.6 GHz, 3.6 GHz turbo).


Read More ...




Benchmarked - Assassin's Creed: Unity
The fifth game in the Assassin's Creed series (depending on how you want to count), Assassin's Creed: Unity is perhaps one of the most demanding games to ever hit the PC. It has also had a rather bumpy start, though some of that may be due to people expecting their system to handle the game without turning down a few of the graphics options. Can your GPU handle Unity, or does it need a few judicious upgrades first – or maybe just a couple more patches to the game – that's what we're here to find out.


Read More ...




Encryption and Storage Performance in Android 5.0 Lollipop
As alluded to in our Nexus 6 review, our normal storage performance benchmark was no longer giving valid results as of Android 5.0. While Androbench was not a perfect benchmark by any stretch of the imagination, it was a reasonably accurate test of basic storage performance. However, with the Nexus 5 on Android’s developer preview, we saw anywhere between 2-10x improvement to Androbench’s storage performance results with no real basis in reality. It seems that this is because the way that the benchmark was written relied upon another function for timing, which has changed with Android 5.0.

While we haven’t talked too much about AndEBench, it has a fully functional storage test that we can compare to our Androbench results. While we’re unsure of the 256K sequential and random read results, it seems that the results are equivalent to Androbench on Android 4.4 when a 1.7x scaling factor is applied. However, AndEBench results should be trustworthy as we saw no difference in results when updating devices from 4.4 to 5.0. In addition, the benchmark itself uses low level operations that shouldn’t be affected by updates to Android.

Androbench Results - Valid vs. Faultty
Nexus 5 Androbench Results on 4.4 KitKat Nexus 5 Androbench Results on 5.0 Lollipop
Random Read 10.06 MB/s 27.70 MB/s
Random Write 0.75 MB/s 13.09 MB/s
Sequential Read 76.29 MB/s 182.78 MB/s
Sequential Write 15.00 MB/s 47.10 MB/s

As you can see, the results show a degree of improvement that is well beyond what could realistically be accomplished with any sort of software optimizations. The results for the random write test are the most notable, with a result that suggests the performance is over 17x faster on Android Lollipop, which could not be the case. This required further investigation, and  it's one of the reasons why we were hesitant to post any storage benchmarks in the Nexus 6 review.

The other factor affecting the results of the benchmarks on the Nexus 6 specifically is Android Lollipop's Full Disk Encryption (FDE). Android has actually had this ability since Android 3.0 Honeycomb, but Lollipop is the first time it's being enabled by default on new devices. When FDE is enabled, all writes to disk have the information encrypted before it's committed, and all reads have the information decrypted before they're returned to the process. The key to decrypt is protected by the lockscreen password, which means that the data should be safe from anyone who takes possession of your device. However, unlike SSDs, which often have native encryption, eMMC has no such standard. In addition, most SoCs don't have the type of fixed-function blocks necessary to enable FDE with little to no performance penalty.

As a result, we've observed significant performance penalties caused by the use of FDE on the Nexus 6. Motorola was kind enough to reach out and provide a build with FDE disabled so we could compare performance, and we've put the results in the graphs below. For reference, the Nexus 5 (Lollipop) numbers are run using Andebench, while the original values are read out from Androbench on Android 4.4. The Nexus 5 is also running without FDE enabled, as it will not enable itself by default when updating to Lollipop via an OTA update.

Internal NAND - Random Read

Internal NAND - Random Write

Internal NAND - Sequential Read

As you can see, there's a very significant performance penalty that comes with enabling FDE, with a 62.9% drop in random read performance, a 50.5% drop in random write performance, and a staggering 80.7% drop in sequential read performance. This has serious negative implications for device performance in any situation where applications are reading or writing to disk. Google's move to enable FDE by default also may not be very helpful with real world security without a change in user behaviour, as much of the security comes from the use of a passcode. This poses a problem, because the users that don't use a passcode doesn't really benefit from FDE, but they're still subject to the penalties.

When the Nexus 6 review was published, I commented that there were performance issues that weren't present on the Nexus 5 running Android Lollipop. Many users commented that the FDE may have been to blame. Like I mentioned earlier, Motorola provided us with a build of Android with FDE disabled. Unfortunately, I haven't noticed any improvements to many of the areas where there are significant frame rate issues such as Messenger and Calendar. I speculated in the Nexus 6 review that the performance issues may simply be the result of insufficient GPU performance or memory bandwidth to drive the QHD display.

To me, the move to enable FDE by default in Lollipop seems like a reactionary move to combat the perception that Android is insecure or more prone to attack than iOS, even if that perception may not actually be accurate. While it's always good to improve the security of your platform, the current solution results in an unacceptable hit to performance. I hope Google will either reconsider their decision to enable FDE by default, or implement it in a way that doesn't have as significant of an impact on performance.


Read More ...




Quick Note: Google Chromebooks Now Coming with 1TB of Google Drive Space
1TB freebie lasts for two years

Read More ...




Xiaomi Aims to be #1 Smartphone OEM Within 10 Years, Apple Urges Caution
“It is easy to say, it is more difficult to do" -- Bruce Sewell, Apple general counsel and senior vice president of legal and government affairs

Read More ...




Quick Note: GM Teases Next Generation Chevrolet Volt
GM offers a glimpse at the front of the second generation Volt

Read More ...




FTC Announces Crackdown on Computer Speedup/Tech Support Scams
"Finally Fast PC" better watch out

Read More ...




Quick Note: Samsung's Request to Dismiss Microsoft Lawsuit is Rejected
Court orders that breach of contract suit must go on

Read More ...




Top Obama Admin DOJ Official to Apple, Google: Encryption Will Lead to Dead Kids
Agency feels it's best to give up freedoms, privacy to "keep the kids safe", Apple and Google say "yea, right"

Read More ...




Amazon Offers "The Washington Post" Free for Six Months to Kindle Fire Owners
Amazon will offer an additional six months of service for just $1

Read More ...






Available Tags:Cooler Master , AMD , Samsung , Intel , Xeon , Android , Google , Google , Smartphone , Apple , GM , Chevrolet , Microsoft , Amazon , Kindle

No comments: