Now this is an AMG Feedem two x 4965 Black edition process ER, In November of this year, it will be 10 years old.

And for a CPU approaching a decade in age, it's still fetches a fairly decent price on the used market.

This one was included with the purchase of a Seuss AM three motherboard Bando I found on eBay and compared with eight gigs of DDR three memory.

Initially, I wasn't sure if it worked or not.

So I decided to slap it into a test rig and take a quick look at the performance off this thing in 2019 before putting together a cheap gaming machine using these components later this week.

So, as I say for now, it certainly will be a quick look.

First things first, and after determining that it did indeed work just fine, I fired up Sin a Bench ar 15 to get an idea of both the multi and single core performance with scores of 3 40 88 respectively.

It will still give a couple of aim these lower end FX series chips a run for their money.

But, as you can imagine, full short of even the cheapest entry level rise in three C p use.

That's not really a sensible or fair comparison to make, though, as I'm sure you'll agree, I'm happy to report that it does okay at handling Editing in Premiere Pro Sisi 2015.

No rendering a 32nd 60 f ps 10 80 p clip took around 50 seconds, which isn't great, but I was still able to navigate the program, make cuts and play my project preview back at full resolution reasonably well before dinner because of this 125.

What process that were really going toe work here.

When it comes to modern games, though.

Well, this is where the old architectural lets us down most.

In yesterday's video, some of you were asking me to add and benchmark apex legends, so I thought I'd give that a try here, and unfortunately I had no luck in getting it to work.

It was a similar story in far Cry five, whereby the game wouldn't even launch due to a quote UN supported process, sir, but let's not get bogged down with what CPU can't run whatever game because there's plenty this CP you can still play, albeit not always very well.

Bear in mind for this video, the process of wasn't stock speeds There will be overcooking it when I put my AM three based build together so the story might change a little here, A 10 80 p medium.

The average frame rate to recorded by frappes was 44 with 1% lows and 10.1% lows of 23 16 respectively.

There were certainly moments of quite noticeable lag, with particularly intense scenes lowering offering rite to the high twenties.

It wasn't a totally unplayable experience by any means, and the CPU never maxed out, so to speak, at 100% usage.

But dropping the settings here would probably do the performance of favor.

The reason I stuck with Medium for now was because it was suggested by the game.

And yet, considering this freedom is approaching its 10th birthday, how happily say, put up a pretty good fight fortnight at 10 a teepee with the high settings.

So our Stevie you reach max usage quite frequently, unlike the aforementioned battlefield five.

Most of the stuttering occurred shortly after the initial jump to begin the battle.

But when we were firmly on the ground, things settled down a bit.

There were certainly still some hitching that typically occurred at pivotal moments, causing the untimely end of my player.

But you'll see playable frame rates most of the time, especially in more open and empty areas.

Interestingly, just cause for performed very well, though this game seems to rely more on a decent graphics card as opposed to a process.

Er, at least from what I've observed, so sustaining at least 60 F.

P.

S a 10 80 p medium with any forms of anti A sing off shouldn't be too problematic.

And it certainly wasn't during this opening section of the Games initial level.

This result was actually quite surprising.

Shadow of the Tomb Raider, though.

Well, I decided to run the in game benchmark here, but my attempt to do so was met with an initial lengthy wait.

I mean really lengthy at least two and 1/2 minutes of loading screens before anything happened.

When something did eventually happen, I experienced a strange statuary effect that only occurred once out of my three benchmark runs.

The reason I used this run in the footage was because I wanted to point out that this might happen if you're using one of these feedem CB use or it might know when it did occur.

The frame rate, as you can see in the top left corner, wasn't too bad, varying wildly, depending on the end game level.

But the 965 was running at 100% usage all of the time before this benchmark around just refused to load the final segment.

I'm going to leave it there for now.

But as I said before, I will be putting together an AM three based build based on this process are very soon.

So I'll be testing a larger library of titles then as well.

We're seeing what we can do in terms of a stable over cook.

For now, though, well, it seems as though this thing is a mixed bag of unpredictable results, but I hope you can join me in the next one where we'll be testing it under different circumstances.

So there we have it.

If you enjoy this video lever like on it, leave a dislike.

If you didn't let me know if you still use this process in your system, Subscribe to the channel if you haven't done so already and hopefully I'll see all of you in the next one.