openclaw - 💡(How to fix) Fix Per-request startup pipeline takes 90-130s (core-plugin-tools + system-prompt + stream-setup) [2 comments, 3 participants]

TL;DR

Implement caching for plugin tool definitions and system prompts, and consider connection pooling for the remote model to reduce the per-request cost.

Guidance

• Investigate the core-plugin-tools and system-prompt components to determine why caching is not being applied across requests, and implement a caching mechanism to store the results of expensive operations.
• Review the stream-setup component to explore options for connection pooling or keep-alive mechanisms to reduce the time spent establishing a connection to the remote model.
• Analyze the event loop utilization to identify opportunities for optimizing I/O-bound stages and preventing blockage.
• Consider implementing a queue or worker thread to offload expensive operations and prevent event loop blockage.

Example

No code snippet is provided as the issue does not contain sufficient information about the implementation details.

Notes

The provided information suggests that the issue is related to the performance of specific components, but the root cause may be complex and require further investigation. The suggested guidance points are intended to help identify and address potential bottlenecks.

Recommendation

Apply workaround: Implement caching and connection pooling mechanisms to reduce the per-request cost and prevent event loop blockage, as the issue is likely caused by the lack of caching and inefficient connection establishment.