How to benchmark PlanetSide 2

PlanetSide 2 historically lacks any form of benchmark. Most players rely on anecdotal framerate, provided by in-game FPS counter, which can be enabled by pressing Alt + F or typing /fps in chat.

The benchmarking method that I’m about to describe is still far from perfect, but it’s a big step in the right direction.

FRAPS

FRAPS is a free video capture and benchmarking program. Some of its video recording functionality is locked behind a paywall, but it doesn’t matter for our purposes. We’re going to use FRAPS to collect PlanetSide 2 performance information while you’re playing, notably Average FPS and Frame Time. You can learn about both statistics in this excellent article.

Let’s get started:

(1) Download and install FRAPS.

(2) Launch FRAPS and set it up like this:

(3) Log into PlanetSide 2.

(4) Start benchmarking by pressing the FRAPS benchmarking key, F11 by default.  You will notice that FPS counter in the corner disappears.

(5) FRAPS will record Frame Times – how much time it took your PC to render each individual frame.

(6) When benchmarking is over, the FPS counter will appear again. You can also manually end benchmarking by pressing F11 again. FRAPS will put recorded Frame Times in a file in the FRAPS benchmarking folder.

To actually analyze the recorded Frame Times, you’re gonna need another program.

FRAFS Bench Viewer

Download and install FRAFS Bench Viewer.

Whenever you launch it, it will automatically open your FRAPS Benchmarking Folder. To analyze a recorded benchmark, simply drag and drop the corresponding “frametimes” file on Bench Viewer’s window.

Vertical spikes on the graph represent frames that take abnormally long to render. In-game lags and framerate drops will be shown on this graph as long sequences of frames with long Frame Time. 

It’s important to visually analyze Frame Time data, because framerate drops, lags and stuttering will not have a considerable effect on Average FPS, yet there will be a noticeable impact on gaming experience.

Keep in mind that in PlanetSide 2, you will get Frame Time lags whenever you use a terminal or go through a loading screen, and it’s just a part of normal gameplay. Single Frame Time lags can appear even with good hardware, and are imperceptible to human eye. You only should be worried if you see a whole block of spikes:

At the top left, there’s a table with useful statistics:

Avg. time refers to overall average Frame Time. It is used to calculate your Average FPS to the right.

1% time refers to average Frame Time of 1% of worst frames. In other words, during this benchmark, the 99% of frames took less than 1% time to render. You can treat it as your meaningful “minimum FPS”, that more or less ignores the occasional imperceptible frame skip.

PlanetSide 2 benchmarking problem

As mentioned, PlanetSide 2 will invariably experience framerate drops whenever you interact with a terminal or go through a loading screen, which often happens whenever you die or use a teleporter. Opening the map or other menus is likely to lower the framerate as well. 

This is a problem, because it will pollute your benchmarking results. There are several ways around this.

Short Benchmarking

This method gives you the most clean results, but they will vary from test to test. The basic idea is to go for short benchmarking time, around 1-5 minutes, and avoid:

  • Dying
  • Interacting with terminals or teleporters
  • Opening your map

The easiest way to facilitate that would be to equip Stalker Cloaking and stay crouched and cloaked throughout the whole benchmark.

Find a battle that looks like it’s gonna last longer than for your intended benchmarking time. A large slug fest on open ground between bases would be ideal. Make sure to remember or write down the approximate number of players in that area, e.g. 24-48 vs 24-48.

Watch the battle, but do not actually participate. 

The problem with this method is that your framerate will change depending on how much action is going on screen. This method works well if you want to “stress test” your system, and figure out if there are any problems with skipped frames and stutter

Extended Benchmarking

With this method, you remove any time constraints from FRAPS benchmarking, and simply enable it in the background whenever you play. Ideally, you want to accumulate a few hours of data. It will be polluted by loading terminals and interface interactions, but if you go for a really large sample size, and assuming you play roughly the same every day, this benchmark can potentially give you more accurate Average FPS as an overall performance indicator. Just keep in mind that your actual in-combat FPS is likely to be different from that Average FPS.

Benchmarking + Video Recording

This one is my favorite. 

If you usually play with Shadowplay or ReLive enabled, simply enable recording at the same time as you start benchmarking, and end them together as well. 

This way you will get an FPS timeline, accompanied by a video, which will tell you how much action was going on screen during this or that FPS, and what happened when you were getting framerate stutter.

  • If it happens while you’re interacting with a terminal, then it’s not a problem. 
  • But if you see stutter during combat, it’s an indication that you need to lower settings or upgrade your hardware.

Closing

Obviously, your performance will vary a lot depending on how much action is going on screen. Benchmarking over extended periods of time will help reduce the variance somewhat, but we all know how much PlanetSide 2 changes from day to day. But it’s still better than trying to infer meaningful information from in-game FPS counter.

Benchmarking this way will allow you to perform more meaningful analysis if you decide to overclock or upgrade your hardware, or compare the performance cost of different graphics settings on your PC specifically. 

Current situation with Intel CPUs

Update 06/2018: this article is no longer relevant, since cheap Intel motherboards have been available for good few months now.

Anyone looking to buy or upgrade their CPU in the nearest future will face an interesting choice.

Early in 2017, Intel released 7th generation of CPUs, such as Core i5 7600k that I’m using. They use Kaby Lake architecture and are usually slotted in motherboards with 200-series chipset, such as Z270.

By the way, “k” at the end of the CPU name indicates it can be overclocked by multiplier, which is how CPUs are usually overclocked. Only motherboards with “Z” in their chipset name can overclock Intel CPUs by multiplier. You can read more about it here.

And just recently Intel released 8th generation of CPUs, such as i5 8600k. They use Coffee Lake architecture and require a motherboard with the new 300-series chipset, such as Z370.

Normally, you’d want to go with the newer generation without a second thought, but the problem is that Coffee Lake CPUs got a ton of hype, which led to stock shortage and significant price increases in both Coffee Lake CPUs and 300-series motherboards.

The hype is well deserved. Tom’s Hardware confirms Intel’s claims to i7 8700k being “company’s best gaming processor ever”. Coffee Lake is the first generation in years to give consumer-grade Intel CPUs more cores, though otherwise it’s not very different from Kaby Lake.

For example, the i3 7350k had 2 cores, while i3 8350k has 4 cores. These two CPUs are supposed to have the same price, but for the moment newer CPU is nearly twice as expensive. Eventually, the price will drop, but that can take months. 

Both Kaby Lake and Coffee Lake use the same LGA1151 socket, but Intel decided to be a dick, and made Coffee Lake CPUs incompatible with 200-series chipsets.

So it doesn’t make sense to get Z270 motherboard with something like i3 7350k, and hope to upgrade it to Coffee Lake later, or whatever comes after Coffee Lake. If you get a Kaby Lake CPU right now, you will have to replace the motherboard later as well. 

So if you’re looking to buy or upgrade your CPU, it might make sense to wait a few months and wait until Coffee Lake CPU price drops. This would be more cost efficient.

Let’s compare a few of the noteworthy CPUs:

  • i3 7350k: 2 cores, 4 threads (Hyper Threading)
  • i5 7600k: 4 cores, 4 threads, + Intel Turbo Boost 2.0
  • i3 8350k: 4 cores, 4 threads

All of these CPUs can run the same amount of threads, though obviously having a whole core for each thread is more effective.

Intel Turbo Boost lets the CPU automatically increase multiplier, as long as it can avoid overheating. It’s basically an automatic overclock. However, if you’re getting a “k” version, obviously you’re going to overclock manually, so you don’t really care about Turbo Boost.

The point that I’ve been leading up to: when prices drop to where they should be, i3 8350k will be a good deal cheaper than i5 7600k, while offering basically the same performance.

It will also let you use a Z370 motherboard, which is less likely to become the dead end that Z270 became, and there’s a good chance that you will be able to simply swap the CPU when time comes, saving some money on replacing the motherboard as well.

Four cores should be enough to run vast majority of modern and upcoming games at good settings. Even if more new games will be optimized for multi-threading, the Intel’s excellent per-core performance and overclock should carry you quite far. 

If you’re anxious to upgrade right now, but don’t want to overpay for Coffee Lake – there is another option.

You can get a used Z270 motherboard + i5 7600k or even i7 7700k CPU. 

Modern electronic components are usually quite durable, and since they were released only this year, they shouldn’t have been subjected to too much wear and tear. 

Meanwhile, the Coffee Lake pretty much made them obsolete, which should significantly reduce their price point, even past the price reduction that used components usually get.

As always when getting used parts, there is a considerable risk of being tricked into buying broken or otherwise inoperable hardware. Never get used hardware unless the seller can offer a full suit of documents, including warranty, and only if you get to personally test that hardware.