RetroFed Forum
Your home away from modern life.
Search Categories Forum list Register Log in
About RetroFed
RetroFed

Welcome to the nostalgia-filled piefed instance of yesteryear.

Open Registration with Application questionnaire.

If you have a question or comment you can post in !meta@retrofed.com or message @DosDude@retrofed.com or @Die4Ever@retrofed.com

In case of downtime and/or emergency, we will post updates on @DosDude@mastodon.social

Some rules we try to uphold:

  • Be civil. Bigotry is not welcome. This includes (but is not limited to): transphobia, queerphobia, racism, ageism and ableism. We do not promote hate.
  • Communities need to be Retro or Retro-adjacent.
  • Please don't upload pornographic content. (use an external image host for that)
74 registered users
Administrators: DosDude, Die4Ever
Visit retrofed.com
Game++. Part 2.2: Types of optimization
Post Reply RetroFed Forum Forum Index » Game Development
AuthorMessage
CodyIT programming.dev CodiUnicorn@programming.dev
Joined: 2024-09-30
Quote

Link: https://pvs-studio.com/en/blog/posts/cpp/1422/
7   Original
Artisian lemmy.world Artisian@lemmy.world
Joined: 2023-06-20
#2 · Quote Reply

(links no good for me)
1
CGTRocketX programming.dev CGTRocketX@programming.dev
Joined: 2026-10-22
#3 · Quote Reply

The "stable 30 beats 60 that drops to 20" point is the one I wish more people internalized early. Frame-time graphs tell you far more than an average FPS counter ever will.

Also agree on the shifting hotspot thing: fix the worst offender and the next one was hiding right behind it. In my experience stray allocations on the main thread are the most common source of those uneven frames.

Curious whether the later parts cover setting a frame budget per system up front, or whether the book treats it as purely a profile-then-fix loop?
1
Post Reply
Back to top
Powered by PieFed · PieBB frontend · All times are Europe/Amsterdam