Josh Goldberg 10/9/2017

How lazily instantiated classes reduced my game engines' reset times by half

Read Original

The article details a performance optimization in a custom JavaScript game engine. The author's 'ObjectMakr' module originally instantiated hundreds of dynamic class objects at startup, causing slow reset times. By shifting to lazy instantiation—only creating classes when they are actually needed—reset time was cut from ~700ms to ~300ms, with class creation time dropping from 400ms to 1ms. The piece concludes with lessons on minimizing unused work and the trade-offs of building an engine from scratch.

How lazily instantiated classes reduced my game engines' reset times by half

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
The Beautiful Web
Jens Oliver Meiert 2 votes
2
Container queries are rad AF!
Chris Ferdinandi 2 votes
3
Quoting Thariq Shihipar
Simon Willison 2 votes
4
Wagon’s algorithm in Python
John D. Cook 1 votes
6
Top picks — 2026 January
Paweł Grzybek 1 votes
7
In Praise of –dry-run
Henrik Warne 1 votes
9
Vibe coding your first iOS app
William Denniss 1 votes