Skip to content
0:00 / 0:00

#physicsengine#parallelization#spinlocks

Dennis Gustafsson – Parallelizing the physics solver – BSC 2025

Better Software Conference

32K subscribers • 7 videos on Hallway

YouTube
  • Recommended by 4 people: 2 on Hacker News, 1 on Lobsters and 1 in engineering communities.
  • Presented by Dennis Gustafsson, creator of Teardown

Advanced. Deep dive for people who know the field.

77K views1 year ago4 recommendations

Game developmentSystems programmingGame programmingConcurrency and parallelismPerformance and optimization

Dennis Gustafsson explains how he parallelized the real-time physics solver for his game engine using custom synchronization techniques.

Dennis Gustafsson's talk at BSC 2025 about parallelizing the physics solver in for an upcoming game. Dennis' links: - voxagon.se/ - x.com/voxagonlabs/ - teardowngame.com/ BSC links: - BetterSoftwareConference.com/ - x.com/BetterSoftwareC - twitch.tv/BetterSoftwareConference/ Chapters: Talk Q&A

Why it's here

4 people recommend this

What people say. Recommended as an insightful look into optimizing and parallelizing a real-time physics engine using spinlocks.

u/Better_Pirate_7823in r/gameenginedevs • Recommends

Parallelizing the physics solver by Dennis Gustafsson (Teardown) (2025)

aminomon Lobsters • Recommends

Parallelizing the physics solver

fasterikon Hacker News • Recommends

On “Spinning around: Please don't – Common problems with spin locks”

As always: use standard libraries, profile, then write your own if the data indicates it's necessary. The following is an interesting talk where the author used a spinlock to speed up a real-time physics solver significantly. Dennis Gustafsson – Parallelizing the physics solver – BSC 2025 link to this video

Hikikomorion Hacker News • Recommends

On “The unlikely story of Teardown Multiplayer”

Not about multiplayer but still interesting. Dennis Gustafsson – Parallelizing the physics solver – BSC 2025 link to this video

levodelellison Hacker News • Mentions

On “Futurelock: A subtle risk in async Rust”

From my understanding this talk describes how he implemented a solution for a similar problem link to this video I'm saying if you're not writing multi-threaded code everyday, use a library. It can use atomics/locks but you shouldn't use it directly. If the library is designed well it'd be impossible to deadlock.