perf: element event batch triggering

[wang1212]

🤔 This is a ...

• New feature
• Bug fix
• Site / Document optimization
• TypeScript definition update
• Refactoring
• Performance improvement
• Code style optimization
• Test Case
• Branch merge
• Other (about what?)

🔗 Related issue link

#2001

💡 Background and solution

Problem Description:

In the current implementation, it is necessary to traverse the list of elements in the scene graph multiple times, which has an impact on performance, and the superposition effect of different events exacerbates the performance problem.

This pattern of traversing elements and triggering events is a bit like the early web standard MutationEvent, which has been deprecated and replaced by MutationObserve. It can be seen that this is an anti-pattern.

see https://developer.chrome.com/blog/mutation-events-deprecation

In addition, the performance problem of this implementation is obvious, so G uses the reuse mechanism of event objects to improve performance, but this approach has been proven to be insignificant. At the same time, we also conducted a simple test:

see facebook/react#18216

Solution:

The processing of internal element events is changed to batch triggering.

• Create a list of elements only once
• Events are only triggered on canvas instance (root element) only once
• Event objects are no longer shared

Impact:

• ElementEvent.BOUNDS_CHANGED (internal)

📝 Changelog

Language	Changelog
🇺🇸 English	perf: element event batch triggering
🇨🇳 Chinese	perf: 批处理元素事件

☑️ Self Check before Merge

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• TypeScript definition is updated/provided or not needed
• Changelog is provided or not needed

[changeset-bot]

🦋 Changeset detected

Latest commit: bb9d351

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 47 packages

Name	Type
@antv/g-plugin-canvaskit-renderer	Minor
@antv/g-plugin-canvas-renderer	Minor
@antv/g-plugin-device-renderer	Minor
@antv/g-plugin-html-renderer	Minor
@antv/g-plugin-image-loader	Minor
@antv/g-plugin-svg-renderer	Minor
@antv/g-plugin-a11y	Minor
@antv/g-plugin-yoga	Minor
@antv/g-lite	Minor
@antv/g-canvaskit	Patch
@antv/g-canvas	Patch
@antv/g-mobile-canvas	Patch
@antv/g-plugin-canvas-picker	Patch
@antv/g-mobile-webgl	Patch
@antv/g-plugin-3d	Patch
@antv/g-webgl	Patch
@antv/g-webgpu	Patch
@antv/g-mobile-svg	Patch
@antv/g-plugin-svg-picker	Patch
@antv/g-plugin-zdog-svg-renderer	Patch
@antv/g-svg	Patch
@antv/g-camera-api	Patch
@antv/g-components	Patch
@antv/g-dom-mutation-observer-api	Patch
@antv/g-gesture	Patch
@antv/g-image-exporter	Patch
@antv/g-lottie-player	Patch
@antv/g-mobile-canvas-element	Patch
@antv/g-pattern	Patch
@antv/g-plugin-annotation	Patch
@antv/g-plugin-box2d	Patch
@antv/g-plugin-canvas-path-generator	Patch
@antv/g-plugin-control	Patch
@antv/g-plugin-css-select	Patch
@antv/g-plugin-dom-interaction	Patch
@antv/g-plugin-dragndrop	Patch
@antv/g-plugin-gesture	Patch
@antv/g-plugin-matterjs	Patch
@antv/g-plugin-mobile-interaction	Patch
@antv/g-plugin-physx	Patch
@antv/g-plugin-rough-canvas-renderer	Patch
@antv/g-plugin-rough-svg-renderer	Patch
@antv/g-plugin-zdog-canvas-renderer	Patch
@antv/g-web-animations-api	Patch
@antv/g-web-components	Patch
@antv/g	Patch
@antv/react-g	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[wang1212]

/gemini review

[gemini-code-assist]

Code Review

This pull request introduces a significant performance improvement by refactoring the element event triggering mechanism to a batched approach, similar to MutationObserver. The changes are well-implemented across the core services and plugins. The addition of new benchmarks is also a great way to validate the performance gains. I've found a few minor issues in the new test files that could be addressed to improve code quality.