Optimization: Amdahl’s law

All my recent life/game-changing realizations, brought me to a formula my lead engineer had told me about. It gave me a foreseeable pedestal to achieve, marking the beginning of my long journey to a polished smooth running game. it’s called,

Amdahl’s law or Amdahl’s argument…
It is a formula which gives the theoretical speedup in latency of the execution of a task, at a fixed workload that can be expected of a system whose resources are improved. In other words, it is a formula used to find the maximum improvement possible by just improving a particular part of a system. 

For me it meant, “make the common case fast“. Which meant finding the highest performance hits in the game and fixing them first. Those changes would make the highest performance impact to the game.

And not to my supersize my lead engineer was right all along. The Symbol A in our game dipped our Frame Rate to 40s from 60s. The Game would look considerably chuggy whenever the screen filled up with Symbol As. Just fixing that improved the overall quality of the game.

I used my “Saving Grace Method” to fix that symbol. https://shahbazsekhon.com/optimization-custom-profiler/


Once everything was done, the game was running a high 60 fps. When symbol As filled up the screen, the fps ran a high 50s. And the chuggy-ness wasn’t so noticeable. Only after achieving such an improvement, I went on to improve the overall fps next.