Overview

It's not enough for an application to simply run — low memory consumption and fast performance matter too, and geajs has considerable headroom here if you know how to use it.

This chapter is distinct from Plugin Optimization, and the two are meant to be read together rather than as duplicates of each other:

• Plugin Optimization covers what the compiler does on your behalf — how it decides which optimization tier a Component or Store qualifies for, and what static conditions (file structure, class shape) unlock each tier.
• Memory & Performance (this chapter) covers what you do — how to write code that stays eligible for those tiers, how to verify that memory is actually being released when it should be, and how to track down a leak once you suspect one.

In short: 02 explains the machine, 05 explains the craft of operating it.

Questions Addressed in This Category

• How do you confirm that a missing dispose() call is actually leaking memory, rather than just suspecting it?
• What does a Store- or Component-related leak look like in browser DevTools, specifically?

info

This chapter assumes the lifecycle and mixin composition patterns covered in How to write Mixin Functions and the identity pitfalls covered in Proxy and Raw Instance Identity — both come up directly when debugging leaks.