openclaw - 💡(How to fix) Fix [BLOCKER] OpenClaw 4.22 to 4.26 significantly slower - regression bug [9 comments, 8 participants]

TL;DR

Downgrade to OpenClaw 4.22 or investigate optimizations for the larger bundled files and config schema in version 4.26 to mitigate the performance regression.

Guidance

• Investigate the impact of the 37% increase in the main channel file size on parsing times and consider optimizations to reduce this overhead.
• Review the plugin config schema and explore ways to reduce its size or improve validation efficiency, given the 140x increase in size.
• Analyze the effects of the removed reaction-related files and the restructured accounts module on the event processing path and API resolution, potentially identifying bottlenecks.
• Consider temporarily using OpenClaw 4.22 until a fix or optimization for 4.26 is available, given the significant performance regression.

Example

No specific code snippet can be provided without further details on the implementation, but optimizing file sizes and config validation could involve techniques like code splitting, lazy loading, or more efficient data structures.

Notes

The root cause analysis suggests a significant change in file structure and event processing between versions 4.22 and 4.26, which likely contributes to the performance issue. However, without access to the specific codebase or more detailed performance metrics, it's challenging to provide a precise fix.

Recommendation

Apply workaround: Given the blocker nature of this issue and the significant performance regression, downgrading to OpenClaw 4.22 might be the most immediate solution to restore usability, while the development team investigates and optimizes version 4.26.