Gigabyte F2A85X-UP4 Review – Are PowIRStages Needed with Trinity?
by Ian Cutress on December 14, 2012 12:00 PM EST- Posted in
- Motherboards
- Gigabyte
- FM2
- A85X
Rightmark Audio Analyzer 6.2.5
In part due to reader requests, we are pleased to include Rightmark Audio Analyzer results in our benchmark suite. The premise behind Rightmark:AA is to test the input and output of the audio system to determine noise levels, range, harmonic distortion, stereo crosstalk and so forth. Rightmark:AA should indicate how well the sound system is built and isolated from electrical interference (either internally or externally). For this test we connect the Line Out to the Line In using a short six inch 3.5mm to 3.5mm high-quality jack, turn the OS volume to 100%, and run the Rightmark default test suite at 48 kHz, 96 kHz and 192 kHz. We look specifically at the Dynamic Range of the audio codec used on board, as well as the Total Harmonic Distortion + Noise.
The ALC892 shows that the dynamic range offered (and constructed) in the ASRock product is superior to that of the other FM2/A85X models.
USB 3.0 Backup
For this benchmark, we run CrystalDiskMark to determine the ideal sequential read and write speeds for the USB port using our 240 GB OCZ Vertex3 SSD with a SATA 6 Gbps to USB 3.0 converter. Then we transfer a set size of files from the SSD to the USB drive using DiskBench, which monitors the time taken to transfer. The files transferred are a 1.52 GB set of 2867 files across 320 folders – 95% of these files are small typical website files, and the rest (90% of the size) are the videos used in the WinRAR test.
Despite the commanding lead of the MSI FM2 board (related to a BIOS setting that also interferes with Turbo modes), the Gigabyte performs middle of the pack with respect to the other FM2 motherboards on USB 2.0.
Consistency seems key on USB 3.0, with the Chipset ports coming second in all tests. The Etron controller on board has additional latency to contend with, but even with this the peak speeds (and overall usage test) fall by the wayside in comparison to the Chipset implementation.
DPC Latency
Deferred Procedure Call latency is a way in which Windows handles interrupt servicing. In order to wait for a processor to acknowledge the request, the system will queue all interrupt requests by priority. Critical interrupts will be handled as soon as possible, whereas lesser priority requests, such as audio, will be further down the line. So if the audio device requires data, it will have to wait until the request is processed before the buffer is filled. If the device drivers of higher priority components in a system are poorly implemented, this can cause delays in request scheduling and process time, resulting in an empty audio buffer – this leads to characteristic audible pauses, pops and clicks. Having a bigger buffer and correctly implemented system drivers obviously helps in this regard. The DPC latency checker measures how much time is processing DPCs from driver invocation – the lower the value will result in better audio transfer at smaller buffer sizes. Results are measured in microseconds and taken as the peak latency while cycling through a series of short HD videos - less than 500 microseconds usually gets the green light, but the lower the better.
The Gigabyte F2A85X-UP4 stays under the 200 microsecond mark we normally consider a great result. Although it should be pointed out that there are still problems with the hardware monitor part of the EasyTune6 software, which as a result will make the DPC Latency spike up to 1000+ microseconds. For ideal usage under audio recording conditions, ET6 should be turned off.
Facebook
Twitter
RSS
25 Comments
View All Comments
ssj3gohan - Friday, December 14, 2012 - link
It's funny that you should ask, because you're totally right: inside is a miniscule bit of silicon with a - by modern standards - very old-fashioned package. But the reason it's so small is simply legacy and second (and third, and fourth) suppliers. Many companies make these (and have tens of millions in stock laying around, the date code on the SIO chip on one of my july '12 boards reads second week of 2010!) and they are mostly interchangeable between mfgrs. If one runs out of stock or asks a fraction of a cent more, they can shop around at the next corner for a better deal without having to respin the board.And also: on any motherboard there is a ridiculous amount of space. ATX boards rarely have better than 40% fill factor, you can fit at least twice as much stuff on there. There is no need to use smaller chips.
The reason not to ditch these chips at all is because it allows for any sort of high-voltage power/interface stage to be delegated to this cheap external chip. It's a huge pain to build 3.3 or even 5V buffers into a mostly 1.05V chip (i.e. chipsets), especially if they also need to have proper ESD protection circuitry. That's stuff that takes up a lot of expensive silicon area. Just having one chip that interfaces everything high voltage hugely simplifies the design of a motherboard. Note that it's not just legacy parallel/serial port connections, but also LEDs, fan control, measuring voltages and even power conversion interfacing that these chips can do.
klmccaughey - Sunday, December 30, 2012 - link
Yup, exactly. They probably have a lot of that silicon not standard transistors / circuitry, but more for voltage and power regulation. It's a bit like a 1/4 inch bolt - industry standard and no need to change it.ssj3gohan - Friday, December 14, 2012 - link
Haha, I see you responded to the complaints of a couple of people on power consumption (among which I have also had my say in the comments of one of your earlier reviews), but your response is not entirely satisfactory IMO.You say that it's the relationship between the numbers that we should look at to get an idea of which is more efficient than the other, but the relationship is not linear and not indicative of what a consumer will get! I build extremely efficient computers (5.4-15W idle, typically) and these absolute differences in power consumption still carry over to low power computers as well: employing a 10W more power hungry motherboard in a 15W computer means my efficiency goes down the drain, whereas on a 150W idle dual-graphics monster PC it doesn't matter one bit. What people need to know is the individual power draw (or losses) of components, not a number that is obfuscated by many, many other uncharacterized components with little or no links to information on their share of the power consumption pie - or influence on power consumption on this particular part!
Second, I know from my experience with these boards that these power consumption numbers mean not a damned thing without the context of which BIOS/EFI settings you used, as well as how well you installed current drivers and such things. Or even what services are running at the time of measurement. One faulty setting can absolutely ruin power consumption, it's a sad fact of life.
We, as readers, have absolutely no way of comparing your findings to anyone else, probably not even to your own other reviews. The only way to have robust power consumption figures is to have DC measurements of isolated system components, with known settings (e.g. 'stock bios F1, no modifications, running windows 8 fully idle, no active background services') and verified use states (i.e. 'system running in ACPI C2'). It's a lot to ask all at once, but waving away the extreme nonorthogonality of your measurements is not the direction I want to see the increasingly important segment of power consumption to go.
Parhel - Friday, December 14, 2012 - link
How is power consumption becoming "increasingly important" for ATX desktop motherboards? I'm not seeing it.klmccaughey - Sunday, December 30, 2012 - link
It is important for always on devices. If you are anything like me you have a lot of computer equipment about the house. I had the guy come round to do an Electricity provider switch-over and he did a few measurements and calculation for me. The computer power added up to a hell of a lot more than I expected.Energy prices are rising world-wide and there is a big push on in many sectors to get power consumption down and stop wasting so much. Initially I was a bit sceptical, but the more oil/gas goes up each year the more I am taking it seriously.
If this is to be used as an always on media server or Raid board, I would actually be checking to make sure it isn't a power hog.
ggathagan - Friday, December 14, 2012 - link
As you clearly understand, it IS a lot to ask all at once.The granularity you desire in this particular area of motherboard testing is well outside of the scope of these reviews, especially when factoring in all of the variables that you mention.
There are time limitations, both on the part of the reviewer, as well as the part of the manufacturer.
If you feel this particular arena of testing is so important, might I suggest starting your own site and performing reviews that focus on the details of power consumption you consider to be important?
Or perhaps you could ask an existing review site if they would be interested in beginning a partnership that would allow you to produce a review addendum that covers these details on the boards that they've reviewed.
I would think that power efficiency would be of particular interest to sites that focus on HTPC systems or sites that focus on low noise systems.
Just as Anandtech has branched out over the years with regard to the areas of technology it covers, I can also see reviewing various products with this sort of focus in mind.
This is especially true as the desire to reduce the size of systems tends to run into limitations due to power consumption and, by extension, heat production.
ssj3gohan - Friday, December 14, 2012 - link
I kind of do already have a site on these subjects, although I don't do reviews, rather I push on the extremes of PC power consumption: http://bit.ly/Of2jrHOn the face of it, I don't actually ask for that much extra testing, I mostly ask for reviewers (in general) to publish materials that show that they understand power consumption completely and have done the things that need to be done to get consistent, comparable results. This basically means understanding power states, measuring power consumption at true steady-state and verifying that all power saving methods are operating as they should. Only then can you get truly comparable power consumption results.
The bit that is really hard to do is to completely isolate motherboard DC power consumption and losses. I don't expect this to happen anytime soon, but at least the DC power measurement can be done. That alone would be a big, big improvement.
Even for ATX boards, power consumption is an issue for enough people and is something that has a place in a proper in-depth review. But these power consumption measurements should really mean something, and what I am seeing right now is measurements that can probably go either way depending on what the reviewer did - which is a black box to me.
Tech-Curious - Friday, December 14, 2012 - link
Fascinating blog -- and amazing work on those custom builds of yours.That said, I think you're more concerned about power efficiency than ... uh, anyone else in the world. And you're probably more knowledgeable about computer power consumption than most anyone who visits this site, including the people who write reviews for it.
None of which is to say that Anandtech (and similar hardware-review sites) couldn't or shouldn't try to improve their power measurements, but we must acknowledge that the audience for Anand's reviews isn't primarily concerned with power measurements. Power consumption matters, but it isn't the meat and potatoes of the meal here; it's more like a side salad.
klmccaughey - Sunday, December 30, 2012 - link
Pwned ;)popej - Friday, December 14, 2012 - link
Your results for THD+N look bad. Most probably are limited by input quality. Audio input on motherboard usually isn't used for anything more demanding then simple microphone, so its quality isn't important for manufacturer. Would be more interesting to measure output only, using good reference audio card or USB adapter.Result dependency on frequency isn't right either. Probably something is wrong in configuration, maybe drivers do poor resampling of audio signal.