> For the complete documentation index, see [llms.txt](https://postica.gitbook.io/binding-system-3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://postica.gitbook.io/binding-system-3/project-tools/performance/performance-mode.md). # Performance Mode A leaner bind UI, for inspectors with hundreds of bindings. This one is about the **editor**, not the game. It changes nothing in a build. A bind row draws more than a field: connecting lines between the toggle and its fields, a live value preview, realtime debug updates, drop zones for rebinding, an animation on proxy bindings. On an Inspector with a handful of bindings that is free. On one with three hundred it is not. Performance Mode drops all of it. ## Turning it on **Project Settings ▸ Binding System ▸ Configuration ▸ General Settings ▸ Performance Mode**, marked **Editor Only**.

Performance Mode and its automatic threshold

## What it drops

Dropped	Why
The connecting lines between the bind toggle and its fields	Decorative.
The live value preview	The per-binding toggle stops having an effect.
Realtime debug updates	Live Debug still works, it just refreshes on repaint.
The rebind drop zones	Drag and drop onto a row is off.
The bind proxy animation	Decorative.

Nothing that affects what a binding **does** changes. This is purely what the Inspector draws. ## Automatic **Auto Enable Above** turns Performance Mode on by itself for an Inspector holding at least that many proxy bindings, and off again when it drops well below. The disengage point sits about a third under the engage point, so a count hovering at the boundary cannot make inspectors rebuild repeatedly. Set it to 0 to never engage automatically. The hint under the field states the current rule in words, for example *Enabled automatically at 60 bindings, disabled again at or below 40*. While the manual toggle is on, the threshold field is disabled and says so, since it would be redundant. {% hint style="info" %} The decision is made **before any row is built**, so an Inspector never ends up with half its fields decorated and half not. {% endhint %} ## Open inspectors keep their look Changing the setting does not restyle inspectors that are already drawn. They keep their current look until they are rebuilt, which happens when you reselect the object. The settings page says so where it matters. ## Performance Mode and the Visualization panel They overlap, and it is worth knowing which to reach for.

	Performance Mode	Visualization panel
Granularity	All or nothing	Per feature
Automatic	Yes, above a threshold	No
Best for	"This Inspector is unusable"	"I never use this one thing"

If only one feature is costing you, turn that one off in [Visualization](/binding-system-3/reference/settings.md#visualization) and leave the rest. Two of its options are worth calling out for this: **Source Replacement**, which costs extra work when the UI is built, and **Methods** in the bind path menu, which is the single biggest factor in how long the menu takes to open on a large type. ## If the editor is still slow

Symptom	What to do
The bind path menu takes a long time to open	Lower Max Bind Path Depth to 2, and turn off Methods in Visualization.
The Inspector repaints constantly	Turn off Realtime Debug, and check that no binding has Live Debug left on.
Selecting an object is slow	Performance Mode, and look at how many proxy bindings the object holds. The Proxy Bindings list makes that visible.
The project takes a long time to import	That is the dependency database. See Bindings Dependencies.