What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	9317
title	Optimize DOM hot path DeltaUpdates to reduce GC pressure
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Feb 26, 2026, 11:00 PM
updatedAt	Feb 26, 2026, 11:02 PM
githubUrl	https://github.com/neomjs/neo/issues/9317
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Feb 26, 2026, 11:02 PM

Optimize DOM hot path DeltaUpdates to reduce GC pressure

Closed v12.0.0/archive-v12-0-0-chunk-4 enhancementai

tobiu commented on Feb 26, 2026, 11:00 PM

This ticket covers a set of optimizations in the hot path of DOM updates (src/main/DeltaUpdates.mjs and src/main/render/DomApiRenderer.mjs).

The main thread can process batches of 600+ deltas at a time. The previous implementations relied on Array.from().find() for NodeLists and Object.entries().forEach() for object iteration, which creates significant garbage collection (GC) pressure due to intermediate array allocations and closure creation.

Changes:

Replaced Array.from(childNodes).find(...) with standard for loops in DeltaUpdates.mjs (getFragmentNodes, removeNode, updateVtext).
Replaced Object.entries(delta).forEach(...) with for...in loops in DeltaUpdates.updateNode and DomApiRenderer.createDomTree for attributes and styles.
Removed a duplicate getFragmentNodes method from DeltaUpdates.mjs.

These changes should yield a measurable reduction in memory allocations and frame drops during intense update phases.

tobiu Feb 26, 2026, 11:01 PM

Input from Gemini 3.1 Pro:

✦ The optimizations have been successfully implemented and pushed to the dev branch.

Replaced all instances of Array.from().find() with for loops in DeltaUpdates.mjs to eliminate array allocations.

Replaced Object.entries().forEach() with for...in loops in updateNode and DomApiRenderer.createDomTree to avoid temporary arrays and closures.

Removed the duplicate getFragmentNodes method in DeltaUpdates.mjs.

These changes should significantly reduce GC pressure in the main thread during heavy DOM update operations. Closing this ticket.