Benchmark RX 570 vs. RX 5700 XT vs. GTX 1660 Super, Ryzen 2600 OC, 3600MHz RAM

At the end of last year, I was researching GPUs like a madman, trying to find the best option for price and performance and maybe also have some headroom for a future CPU upgrade. My starting point was a Ryzen 5 2600, 16 GB of 3000 MHz CL15 RAM and an AMD RX 570 with 8 GB of VRAM. A very good performance per buck machine in the summer of 2019 for 1080p gaming. It was purpose-built to be cheap with an upgrade path in the near future. However, my inner hardware enthusiast didn’t want to be content. It also didn’t help that the two games I was playing at that time performed rather poorly (which was the games fault, but you take every excuse you can get to buy new stuff).

Putting that aside, I have data of three graphics cards to compare, tested in four games at three different in-game settings – plus a custom one for two games that I used for playing. In addition to that, I have a bit of CPU overclocking as a result of troubleshooting and a RAM upgrade from a 3000 MHz CL15 kit to a 3600 MHz CL17 kit – which is running at 3400 MHz. More wasn’t possible with this motherboard and CPU. This post isn’t about the CPU overclocking though. I did that to see if the 5700 XT was limited by the R5 2600 and would perform better with a faster CPU. Well no surprise there, but as it turned out, the numbers I found were not caused by the CPU. More on that later.

Read More »

Far Cry 5 Coop Review

The Far Cry series has been going on for several years now without changing too much of the core game mechanics since the first Far Cry I have played – which was Far Cry 3. What’s new in FC5 is a coop mode that lets you play the main campaign with a buddy. Far Cry 3 had some form of coop as well, but it worked differently by presenting a story unrelated to the game’s single player campaign. I’m not sure how version 4 handled multiplayer, but to my knowledge Far Cry 5 is the first Far Cry to support coop gameplay. It has a few quirks though, which unfortunately still doesn’t make it a 100% coop enabled game. We nevertheless decided to give it a spin and here are my thoughts about the game, its story and gameplay and how the coop experience was.

Read More »

Spring @ConfigurationProperty a Bean or not?

Semi-recently (“semi” because procrastination kept me from writing, so it’s more like two months ago, but blog posts have to start with “recently” when you try to explain yourself why you are writing what you are writing – but I’m getting sidetracked here, so let’s move on) I was wondering whether Java classes annotated with Spring’s @ConfigurationProperty should be declared as a bean, e.g. with @Component. I didn’t find a definitive answer, but I found three ways on how to do it – typical Spring, I guess.

Here’s a quick setup:

My configuration class.

package com.thecodeslinger.configpropsdemo;

import lombok.Data;
import org.springframework.boot.context.properties.ConfigurationProperties; 

@Data 
@ConfigurationProperties(prefix = "demo")
public class Configuration {

    private String elegy;
}

My main application:

package com.thecodeslinger.configpropsdemo;

import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;

import javax.annotation.PostConstruct;

@SpringBootApplication
public class ConfigPropsDemoApplication {

   @Autowired
   private Configuration configuration;

   @PostConstruct
   public void postConstruct() {
      System.out.println(configuration.getElegy());
   }

   public static void main(String[] args) {
      SpringApplication.run(ConfigPropsDemoApplication.class, args);
   }
}

And finally, my properties file:

demo.elegy=R.I.P. Kobe

It’s not an elegant setup, but that’s not the point. It does the job for now.

If you run the application in this state, Spring will greet you with an error message.

APPLICATION FAILED TO START

Description:
Field configuration in com.thecodeslinger.configpropsdemo.ConfigPropsDemoApplication required a bean of type 'com.thecodeslinger.configpropsdemo.Configuration' that could not be found.
The injection point has the following annotations:
- @org.springframework.beans.factory.annotation.Autowired(required=true)
Action:
Consider defining a bean of type 'com.thecodeslinger.configpropsdemo.Configuration' in your configuration.

It obviously cannot find the configuration bean.

Option #1: Slap @Component to it.

package com.thecodeslinger.configpropsdemo;

import lombok.Data;
import org.springframework.boot.context.properties.ConfigurationProperties;
import org.springframework.stereotype.Component;

@Data
@Component
@ConfigurationProperties(prefix = "demo")
public class Configuration {

    private String elegy;
}

Option #2: Use the @EnableConfigurationProperties annotation.

import org.springframework.boot.context.properties.EnableConfigurationProperties;

@SpringBootApplication
@EnableConfigurationProperties(Configuration.class)
public class ConfigPropsDemoApplication {

Option #3: Use @ConfigurationPropertiesScan to explicitly name the packages to scan for.

import org.springframework.boot.context.properties.ConfigurationPropertiesScan;

@SpringBootApplication
@ConfigurationPropertiesScan({"com.thecodeslinger.configpropsdemo"})
public class ConfigPropsDemoApplication {

All three options achieve what you’re aiming for, a running application.

:: Spring Boot :: (v2.2.4.RELEASE)
2020-02-03 19:57:43.562 INFO 4612 --- [ main] c.t.c.ConfigPropsDemoApplication : Starting ConfigPropsDemoApplication on DESKTOP-C0O3OKC with PID 4612 (D:\OneDrive\Code\Java\config-props-demo\target\classes started by lober in D:\OneDrive\Code\Java\config-props-demo)
2020-02-03 19:57:43.562 INFO 4612 --- [ main] c.t.c.ConfigPropsDemoApplication : No active profile set, falling back to default profiles: default
R.I.P. Kobe
2020-02-03 19:57:43.921 INFO 4612 --- [ main] c.t.c.ConfigPropsDemoApplication : Started ConfigPropsDemoApplication in 0.573 seconds (JVM running for 1.083)

So, is there any benefit of one over the other? The Spring documentation has the following to say:

Sometimes, classes annotated with @ConfigurationProperties might not be suitable for scanning, for example, if you’re developing your own auto-configuration or you want to enable them conditionally. In these cases, specify the list of types to process using the @EnableConfigurationProperties annotation. This can be done on any @Configuration class, as shown in the following example:

I’m not using a @Configuration class in my example, but if you were, you could leverage that to load your configuration classes based on @Profile annotations. Although @Component works too, it’s not mentioned in that part of the Spring documentation (“Type-safe Configuration Properties”).

For myself, I might go with @EnableConfigurationProperties and if it makes sense, even have dedicated @Configuration classes linked to @Profile. For little samples like this one it’s obviously overkill. In a remotely useful application, the additional overhead may be worth it for structural and documentational reasons.

Ghost Recon: Wildlands – Coop Review

It was a dark night. Rain was pouring relentlessly from the heavens as a helicopter made its way across the border to Bolivia, going unnoticed against the black clouds. Any of the chopper’s noises were suppressed by the droning rain and constant thunder in the sky. Its destination was a remote location, a secret safe house where an equally secret meeting will be held. The helicopter’s passengers were a group of well-trained covert operatives and their handler. These were the kind of people you only call upon in dire need, when circumstances don’t allow anything other than an elite group of soldiers that can get any job done regardless of difficulty or danger. And all that without ever being noticed. They are effectively ghosts and haunt whomever they have been unleashed on. This time around their target is El Sueño, the biggest and most ruthless drug lord in Bolivia.

And this is where you as the player come in. The story is nothing particularly spectacular, but it provides a good enough canvas for an entertaining open world action game that justifies why you do what you do. I’ve played this game all the way to end in coop mode and this my review of the roughly 75 hours it took.

Read More »

AMD Radeon RX 5700 XT Stuttering at 1080p

Quick note before I go into any details: I did not find a solution for this problem, unfortunately. I’ll be explaining what happened and show frame time graphs as proof.

So, with that out of the way, let’s get into it. I’m certainly not the only one with this issue. If you employ the search engine of your liking you will find many threads covering that topic (like here and here and here and here and so on). Some managed to get it working, some did not. I’m obviously in the latter category.

What happens? From what I found in my research it seems like the RX 5700 XT GPU aggressively tries to save energy if it is not fully utilized. If you run MSI’s Afterburner or any other monitoring software, then you’ll see the GPU load and frequency being all over the place. In general, this is a good thing – if it does not affect perceived performance. And this is where it fell apart for me.

Read More »

Wolfenstein: Youngblood – Coop Review

Wolfenstein Youngblood follows in the same footsteps as its three predecessors that sucessfully revived the series in 2009. Having liked Wolfenstein, The New Order and The New Colossus I thought that sharing that kind of game with a friend in Coop would be even better. This is the first installement in this series that allows you to do that and I’m a big fan of Coop gameplay. And by Coop I mean playing the regular campaign with a fellow gamer, not some unrelated multiplayer map or basic PvP action. I want to experience the story with somebody, have a ton of fun and discuss the game while playing it.

Read More »

Ryzen Master not Resetting to “Auto” Control Mode

Recently I set out to figure out how much clock speed I can squeeze out of my Zen+ based Ryzen 5 2600. To make life easier I figured I use Ryzen Master so I can change the settings while I’m in Windows so I don’t have to reboot every time I increase the clock speed. This has worked nicely until the point where I figured the viable maximum was. The next step was to dial those numbers "into hardware", meaning setting the options in the BIOS so that Ryzen Master is not required any more. And this is where my issues started to appear.

The Error

First, here’s a screenshot of the message Ryzen Master was giving me. After that I’ll explain what had happened.

In order to set the CPU multiplier you have to change from automatic to manual mode in Ryzen Master. I wanted to reset all options to their defaults after setting the overclock in the BIOS, but I always kept getting the message that Ryzen Master wants to restart Windows because the setting was changed to "Manual" – which it wasn’t, but more on that later. So I did as it asked multiple times with the same outcome every time. Effectively, I was doing a boot loop manually.

So, how did I get there?

The Journey

In brief:

  • Find a stable overclock in Windows using Ryzen Master.
  • Reboot to BIOS and set the overclock closer to the hardware.
  • Reboot to Windows and reset everything in Ryzen Master.
  • Manual "Boot Loop" a few times.
  • Notice CPU always at 4GHz, no more Cool’n’Quiet operation mode.
  • Undo overclock in BIOS.
  • Still see overclock in Windows.
  • Uninstalling Ryzen Master.
  • Still see overclock in Windows.
  • Ryzen Master still not resetting.
  • Manual "Boot Loop" a few more times.
  • Getting pissed and searching the Internet – apparantly I was not alone.
  • More reboots and tests with BIOS settings.

The Fix

It was the frickin’ BIOS! Ryzen Master was not to blame.

I have an ASRock B450 Gaming mITX mainboard with the latest non-Matisse (Ryzen 3000) BIOS. It is not recommended to upgrade unless a Ryzen 3000 is installed. There’s a weird bug in the BIOS that still applies the overclock even if the setting is set to "Auto by AMD CBS" (or something like that). There were two things that helped:

  1. Load BIOS defaults.
  2. Enable manual control and set the correct CPU base frequency at 3400MHz.

When applying the overclock with 4000MHz it effectly ran at 4GHz every time, even in idle. When setting 3400MHz it properly clocked down and also boosted as a R5 2600 should. The same setting only with a different clock value produced a different behavior. And unless the BIOS defaults are loaded the "Auto" mode doesn’t do what you expect – if you’ve set an overclock previously.

Curiously enough, booting Fedora Linux from an USB stick did properly scale the CPU frequency based on the load, even with the overclock applied. Apparently only Windows or AMD’s drivers didn’t manage to do that. Booting a Linux helped me to rule out Ryzen Master as the root of the always applied overclock although the BIOS setting was set to the default Auto mode.

The takeaways:

  • Don’t overclock on this mainboard.
    • The OC options for the CPU are laughable at best. No way to set the multiplier per core.
  • Next time buy a higher-end mainboard for overclocking (ITX is expensive though…).