NVIDIA’s Response Thus Far and Testing Configuration
As the saying goes, there are no secrets in Taiwan and NVIDIA has already been on the phone calling press to let them know that they are going to make some adjustments on pricing of the current GeForce product stack to counter the changes AMD is announcing today. The first price drops are actually on the low end of the stack though – the GeForce GTX 650 Ti Boost 1GB and 2GB models get some moderate price drops starting this week to fall to $129 and $149 MSRP respectively. Obviously targeted at the Radeon R7 260X, the GTX 650 Ti Boost will be the fighter in NVIDIA’s corner during our benchmark results today.
We haven’t yet heard how NVIDIA plans to adjust the pricing on the GTX 660 (the R9 270X competition) or the GTX 770 (the R9 280X competition), or even if they will do so at all. Our benchmarks here today will likely help determine if NVIDIA is as far behind the performance per dollar curve as we think they might be.
Testing Configuration – Why you won’t see Radeon HD 7970/7870/7790 here
Based on the amount of data we present in our collection graphs and benchmark results, I tend to lower the number of cards we put into each comparison. To that point, you will not see the Radeon HD 7970 GHz Edition, Radeon HD 7870 GHz Edition or the Radeon HD 7790 in the majority of our graphs. Why? Simply put, there is very little reason to include them as the performance is identical. I clearly showcased how the R9 280X was the same GPU and same design as the HD 7970 GHz Edition and where the minor differences in clock speeds and memory speeds were. For example:
The results of the Radeon HD 7970 GHz Edition and the Radeon R9 280X are basically identical, well within the margin of error for testing accuracy. The R9 280X, R9 270X and R7 260X are basically rebranding and repositioning of existing product; I’m fine with that (as you should be) and it’s the price drops that should be most interesting. But including duplicate data is time consuming and confusing for the visual presentation of data.
That being decided, what ARE the comparison we are going to be showing you today? The new Radeon R9 280X is going to have an MSRP of $299 for reference models putting it squarely between the GeForce GTX 770 2GB ($399) and the GeForce GTX 760 2GB ($249) cards from NVIDIA.
The Radeon R9 270X will be shipping at $199 and gives us a direct competitor from NVIDIA at the $199 price point, the GeForce GTX 660 2GB. The Radeon R7 260X, with an MSRP of $139 is in a very crowded space, but with the recently announced NVIDIA price drops it will be going against the GeForce GTX 650 Ti Boost 2GB model to match the frame buffer size of AMD’s new card.
So on the following pages you’ll see three sets of graphs:
- Radeon R9 280X 3GB
- GeForce GTX 770 2GB
- GeForce GTX 760 2GB
- Radeon R9 270X 2GB
- GeForce GTX 760 2GB
- GeForce GTX 660 2GB
- Radeon R7 260X 2GB
- GeForce GTX 650 Ti Boost 2GB
We tested the R9 280X and the R9 270X at both 1920×1080 and 2560×1440 resolutions while the R7 260X was limited to 1920×1080 only. Eyefinity and Surround resolution testing (5760×1080) and 4K testing (3840×2160) is going to wait just a bit longer as we await duplicate cards for CrossFire testing. And the fact that nothing has changed in the world of Eyefinity + CrossFire at this point since our last story factors in as well.
If you are new to our Frame Rating style of graphics card testing you should definitely read the entire explanation of how we test below. Our style is quite different than the majority of review sites you’ll see online and I think we offer a unique and completely view of end user performance and experiences. If you are already familiar with Frame Rating here on PC Perspective, then go ahead and jump to the first page of results!
The specifications for our testing system haven't changed much.
|Test System Setup|
|CPU||Intel Core i7-3960X Sandy Bridge-E|
|Motherboard||ASUS P9X79 Deluxe|
|Memory||Corsair Dominator DDR3-1600 16GB|
|Hard Drive||OCZ Agility 4 256GB SSD|
AMD Radeon R9 280X 3GB
AMD Radeon R9 270X 2GB
AMD Radeon R7 260X 2GB
NVIDIA GeForce GTX 770 2GB
NVIDIA GeForce GTX 760 2GB
NVIDIA GeForce GTX 650 Ti Boost 2GB
AMD: 13.11 V1 (Beta)
NVIDIA: 331.40 (Beta)
|Power Supply||Corsair AX1200i|
|Operating System||Windows 8 Pro x64|
- NVIDIA GeForce GTX 770 2GB – $399 (Newegg.com)
- AMD Radeon R9 280X 3GB – $299 (Newegg.com)
- NVIDIA GeForce GTX 760 2GB – $249 (Newegg.com)
- AMD Radeon R9 270X 2GB – $199 (Newegg.com)
- NVIDIA GeForce GTX 660 2GB – $189 (Newegg.com)
- NVIDIA GeForce GTX 650 Ti Boost 2GB – $149 (Newegg.com)
- AMD Radeon R7 260X 2GB – $139 (Newegg.com)
Frame Rating: Our Testing Process
If you aren't familiar with it, you should probably do a little research into our testing methodology as it is quite different than others you may see online. Rather than using FRAPS to measure frame rates or frame times, we are using an secondary PC to capture the output from the tested graphics card directly and then use post processing on the resulting video to determine frame rates, frame times, frame variance and much more.
This amount of data can be pretty confusing if you attempting to read it without proper background, but I strongly believe that the results we present paint a much more thorough picture of performance than other options. So please, read up on the full discussion about our Frame Rating methods before moving forward!!
While there are literally dozens of file created for each “run” of benchmarks, there are several resulting graphs that FCAT produces, as well as several more that we are generating with additional code of our own.
If you don't need the example graphs and explanations below, you can jump straight to the benchmark results now!!
The PCPER FRAPS File
While the graphs above are produced by the default version of the scripts from NVIDIA, I have modified and added to them in a few ways to produce additional data for our readers. The first file shows a sub-set of the data from the RUN file above, the average frame rate over time as defined by FRAPS, though we are combining all of the GPUs we are comparing into a single graph. This will basically emulate the data we have been showing you for the past several years.
The PCPER Observed FPS File
This graph takes a different subset of data points and plots them similarly to the FRAPS file above, but this time we are look at the “observed” average frame rates, shown previously as the blue bars in the RUN file above. This takes out the dropped and runts frames, giving you the performance metrics that actually matter – how many frames are being shown to the gamer to improve the animation sequences.
As you’ll see in our full results on the coming pages, seeing a big difference between the FRAPS FPS graphic and the Observed FPS will indicate cases where it is likely the gamer is not getting the full benefit of the hardware investment in their PC.
The PLOT File
The primary file that is generated from the extracted data is a plot of calculated frame times including runts. The numbers here represent the amount of time that frames appear on the screen for the user, a “thinner” line across the time span represents frame times that are consistent and thus should produce the smoothest animation to the gamer. A “wider” line or one with a lot of peaks and valleys indicates a lot more variance and is likely caused by a lot of runts being displayed.
The RUN File
While the two graphs above show combined results for a set of cards being compared, the RUN file will show you the results from a single card on that particular result. It is in this graph that you can see interesting data about runts, drops, average frame rate and the actual frame rate of your gaming experience.
For tests that show no runts or drops, the data is pretty clean. This is the standard frame rate per second over a span of time graph that has become the standard for performance evaluation on graphics cards.
A test that does have runts and drops will look much different. The black bar labeled FRAPS indicates the average frame rate over time that traditional testing would show if you counted the drops and runts in the equation – as FRAPS FPS measurement does. Any area in red is a dropped frame – the wider the amount of red you see, the more colored bars from our overlay were missing in the captured video file, indicating the gamer never saw those frames in any form.
The wide yellow area is the representation of runts, the thin bands of color in our captured video, that we have determined do not add to the animation of the image on the screen. The larger the area of yellow the more often those runts are appearing.
Finally, the blue line is the measured FPS over each second after removing the runts and drops. We are going to be calling this metric the “observed frame rate” as it measures the actual speed of the animation that the gamer experiences.
The PERcentile File
Scott introduced the idea of frame time percentiles months ago but now that we have some different data using direct capture as opposed to FRAPS, the results might be even more telling. In this case, FCAT is showing percentiles not by frame time but instead by instantaneous FPS. This will tell you the minimum frame rate that will appear on the screen at any given percent of time during our benchmark run. The 50th percentile should be very close to the average total frame rate of the benchmark but as we creep closer to the 100% we see how the frame rate will be affected.
The closer this line is to being perfectly flat the better as that would mean we are running at a constant frame rate the entire time. A steep decline on the right hand side tells us that frame times are varying more and more frequently and might indicate potential stutter in the animation.
The PCPER Frame Time Variance File
Of all the data we are presenting, this is probably the one that needs the most discussion. In an attempt to create a new metric for gaming and graphics performance, I wanted to try to find a way to define stutter based on the data sets we had collected. As I mentioned earlier, we can define a single stutter as a variance level between t_game and t_display. This variance can be introduced in t_game, t_display, or on both levels. Since we can currently only reliably test the t_display rate, how can we create a definition of stutter that makes sense and that can be applied across multiple games and platforms?
We define a single frame variance as the difference between the current frame time and the previous frame time – how consistent the two frames presented to the gamer. However, as I found in my testing plotting the value of this frame variance is nearly a perfect match to the data presented by the minimum FPS (PER) file created by FCAT. To be more specific, stutter is only perceived when there is a break from the previous animation frame rates.
Our current running theory for a stutter evaluation is this: find the current frame time variance by comparing the current frame time to the running average of the frame times of the previous 20 frames. Then, by sorting these frame times and plotting them in a percentile form we can get an interesting look at potential stutter. Comparing the frame times to a running average rather than just to the previous frame should prevent potential problems from legitimate performance peaks or valleys found when moving from a highly compute intensive scene to a lower one.
While we are still trying to figure out if this is the best way to visualize stutter in a game, we have seen enough evidence in our game play testing and by comparing the above graphic to other data generated through our Frame rating system to be reasonably confident in our assertions. So much in fact that I am going to going this data the PCPER ISU, which beer fans will appreciate the acronym of International Stutter Units.
To compare these results you want to see a line that is as close the 0ms mark as possible indicating very little frame rate variance when compared to a running average of previous frames. There will be some inevitable incline as we reach the 90+ percentile but that is expected with any game play sequence that varies from scene to scene. What we do not want to see is a sharper line up that would indicate higher frame variance (ISU) and could be an indication that the game sees microstuttering and hitching problems.