Now some people say joke or processes are obsolete.

Some even say quad core processes are obsolete.

I think both of these opinions are wrong.

I mean, we've just seen the Athlon 3000 Drea hit the market, and considering it has just to cause on four threads, it can still put up a pretty good fight.

Plus, it's priced well, which definitely helps.

Having said that, though, a two core CPU without hyper threading will probably struggle in 2019.

Aside from modern Athlon, chips only have made some incredible strides when it comes to CP use in the last few years.

But there have certainly been some questionable releases along the way, not the Intel were completely innocent.

One particularly interesting period from AM These long history, though, is the whole triple call process of situation, something that until don't have and probably don't want, bragging rights, too.

Take this, for example.

It's called the Phoenix to X 37 10.

It's cocked a 2.6 gigahertz, is supported by the Old AM three platform and has three cause.

It's one of many three court AMG processes and shares the same backstory as the rest.

It started life as a court core, but one core didn't work right.

So am D, just disabled, said Core on dhe solder.

Anyway, it's sort of a faulty X 4955 10 years ago, it was okay if you couldn't afford the quad core, this 1 may have been an attractive alternative.

But as we fast approach 2020 this 2.6 gigahertz strike or is likely as fast as a snail on a Segway, which is actually faster than a snail without a method of motorized transport.

So that joke doesn't really make sense.

But let's all have a nice laugh as we watch this thing attempt to run some games.

I've paid it with my hot and power hungry Vegas 64 which should ensure the CPU reaches its maximum potential.

So let's see what it can do for the gaming tests.

I decided to start with counterstrike global offensive.

Now this is a CPU intensive game, but despite this, we were able to run it with at least 60 frames per second orbit with the settings turned down too low now because I've paired the CPU with My Vegas 64 which will know, is capable of running pretty much everything out there with 60 frames per second.

We're not being held back by the graphics card in any regard.

It's still a very nice GPU, albeit quite power hungry on the FINA MME.

On the other hand, well, we'll certainly struggle.

In a lot of instances, though, I have to admit, it initially started off better here.

Then I anticipated when you first fire up the game, there will be a few moments of slow down, perhaps as the assets load things like that.

But after that, well, it's an okay experience.

There's not too much leg and stutter, though.

A few drops may occur here and there, and we're off to a better start than I thought, so that can only be a good thing.

Now the Vegas 64 is perfectly capable of running crisis.

This 2000 and seven classic Theo GPC Melter, as it were 60 frames per second should be the result here.

But because of the feeling, we are experiencing around 30 with some heavy dips now.

All of the game play was captured externally, using a secondary laptop with on I five on a GTX 10 60 inside, so there's no worries about hindering the performance here by recording with internal capture software such as relive or O.

B s, everything is done externally with an external capture box.

What you see here is exactly what you'll get when using the FINA X three on dhe a Vegas 64 Crisis looks fantastic at high even today, but the frame drops are quite off putting, and it will probably ruin your overall gaming experience here now.

Battlefield five.

Well, it was an interesting one.

We must have been playing through a fairly dark level.

Of course, we weren't the game just jammed.

I fired the game up and we sat looking at the screen for what is a rough estimation of half an hour before the game just closed.

Now Battlefield five is a very CPU intensive game.

So CPU intensive, in fact, that it simply refused to work on the Phoenix three here, which is really no surprise.

Now, dirt rally, too, seems to just operate in a world of its own.

It doesn't care what cbu you're using most of the time, as long as you've got a good graphics card then don't really too will run Absolutely fine.

You can see here we're getting 70 frames per second on the 1% on 10.1%.

Lows are also very respectable.

There were no heavy frame drops, dips, stutters, anything like that to speak off, especially during this time trial test.

And the overall experience was a very good one.

I paid £10 for this process.

A £20 for the motherboard it sits on and then another £15 for the memory.

If you're in a race with other players, but for him, right, maybe a little lower, but over.

We're going to have a great experience with dirt ready to on this triple core Feedem chip from late last decade.

Now, as we went, looking for me means Chief Miss Mistress, Miss Chief in Kingdom Come Deliverance.

Well, we certainly were in for a treat as faras.

The frame rate was concerned.

30 f p.

S was the average or 31 I should say.

Which was quite surprising, though, where there were certainly a few stutters.

But I was very surprised that this game, which is notably CPU intensive, was actually running on this chip.

What I will say is that the intro movie, which seems to be very harsh on a process that took quite a long time to load a couple of minutes, as opposed to a few seconds with newer processes.

So that's something to bear in mind, though, after skipping past that everything works as it should be in game menus operate fine.

Thegame itself runs okay, but the frame dips are probably going to put you off now.

I couldn't really in this video without trying Red Dead redemption to.

This is probably the newest game on today's list, a very modern title indeed, and a very, very demanding one.

Now the Vegas 64.

When paid with any new process, sir, any new half decent processes such as an eye five or rise in three or five, for example, Well, it will do just fine, But with the Ffynnon triple core here, the game wouldn't even start.

I was sort of expecting this.

I threw this title in here as sort of a gamble.

I wasn't expecting much at all, and unfortunately, this time it didn't pay off.

In fact, it didn't pay off in such a high regard that even jammed my PC to the point of not working for a good 10 minutes.

Furthermore, the laptop I'm using to record this footage froze as well.

I don't know how that's even possible.

The performance of this machine should have no effect on the performance of the laptop.

So for them both to freeze, well, something went catastrophically wrong somewhere down the line.

So just to give you an idea quickly of the CPU performance on its own I ran Cinna bench are 20 which I've bean gradually updating with other processes to give you a decent comparison.

Now this one came absolutely bottom of the pile.

It took about 25 minutes to complete the test.

I went outside, made a few calls, and when I came back it really hadn't moved.

Much as you can see the results trying to hide at the bottom of the page here so you don't see it.

I think it's so disappointed in itself.

It's tryingto shy away.

So the outer worlds yeah, around with an average of around 40 frames per second.

But we were seeing a few drops, and when I say a few, I mean a lot about nine and three, with the 1% and 10.1% lows, which was certainly noticeable.

Now this will very depending on the area you're in.

Some areas of the game will run fine.

You'll probably see an average of around the same and the 1% employment Settlers will be ever so slightly higher.

But it does mean that you won't see as many stutters here.

However, during the opening level, there were certainly a few problems.

That's why I tend to benchmark this area because it can be amongst the most problematic.

You would think other busy areas would cause more issues, but this one in particular seems to wreak havoc on older hardware.

So I said at the start that the reason these were soldiers triple cause was because the fourth corps wasn't working quite right.

And that isn't actually the case in 100% off situation.

See, on some, the fourth corps is just disabled for no real reason, and it can even be unlocked with some chips and motherboards.

So I jumped into my BIOS and decided to give it a go.

But unfortunately, when it came to loading windows the whole system froze.

And so this is not a compatible CPU.

Or at least it didn't work for May.

I also tried it on another, more powerful I am three board that I didn't know I had until I got to about this point in the video.

And even then, well, no such luck.

So it's just luck of the draw.

Some see BYU's do have this unlocking potential, and some will have to be used as triple core chips.

But in this day and age on, looking that extra corps probably isn't going to help you too much in a lot of newer titles.

Anyway, you'll probably still see quite a few stutters and frame drops.

I do hope you've enjoyed this video anyway.

I've wanted to take a look back at triple core processes for a while.

If you did enjoy this lever like on it, leave a dislike if you didn't subscribe to the channel.

If you haven't done so already, let me know if you still have a triple core CPU in your system.

Maybe you still use it on a daily basis.

Maybe it's your go to gaming CPU.

I don't know.

Maybe you do, but yeah, let me know in the comments below, and hopefully I'll see all of you in the next video.