Code for Game Developers - Optimization

This week I discuss some reasons you should care about optimization and some common fallacies regarding optimization.

[NeilRoy]

Very nice topic! I just started working on optimizing my own 3D game I have been puttering around with. I managed to change one line of code and greatly increased my speed. I was executing this line of code for every object rendered when I only had to do it once before I drew the entire scene! Then when I done frustum culling it sped up almost TOO much and I know of many more methods to speed it up more. The way I explained it to my wife is that the faster I can get it to run, the more details I can add into the scene and make it look even nicer. Plus the faster it runs, the lower end computer it can run on, and if it is something you plan to sell, that increases your market.

I will point out that you shouldn't worry TOO much about optimizing early on in your development, but you SHOULDN'T ignore it totally either or you could end up totally redesigning certain code (as I learned the hard way).

[TehGM]

I've found an article on gamedev some time ago, but I was too lazy. Now I finally got some will into maths for me to check your videos, and even though this is just the first video of yours I've watched, you get a sub. Seems it'll be worthy.

[indoxperia]

i always happy if someone making tutorial videos about game optimization. Thank you for making this channel. Sorry for my english

[ermanilol]

Really happy I found your channel, looking forward to watching the rest of the playlist!

[aprowolf]

really looking forward for the next lesson :) i learned much from this video

[diverseprogrammer]

You're my like my manual and the best teacher (not saying that teachers are bad, I like 'em too but I learn more from you and Youtube.)

[CatzHoek]

I wonder if it would be an optimization to your channel if you would instantly follow up with the first part of the series if you just released such a quick introductory. ;)

[xeridea]

Saying CPUs aren't getting faster is an outright lie. While clockspeed improvements are marginal, code execution is massively improved. Branch prediction, larger caches, multithreading, new instructions, etc. For example, AMDs Ryzen was a massive leap over Bulldozer, yet it's single threaded speed is going to be more than double with Zen 4 vs Zen 1. It has been about 5 years, and this isn't nearly as fast as clockspeed used to go up, it is disingenuous to say speed hasn't improved, and saying so is more of a meaningless buzzphrase than actual fact.
This isn't to downplay importance of optimizing, just pointing out the flaws in a statement that many people just throw out their, without actually knowing what they are talking about.