openclaw - 💡(How to fix) Fix TUI startup extremely slow: model-resolution 11-16s per message + event loop blocked for 5-16 minutes [2 comments, 3 participants]

TL;DR

Investigate caching model capability probing results to reduce the model-resolution stage time and potentially alleviate event loop blocking.

Guidance

• Verify if the model-resolution stage is indeed performing model capability probing on every request by checking the code or documentation related to the xiaomi/mimo-v2.5-pro model.
• Check if there are any existing caching mechanisms for model capability probing results that can be leveraged or enabled.
• Analyze the correlation between the model-resolution stage and event loop blocking to determine if they are related issues.
• Consider collecting additional logs or metrics to better understand the event loop blocking issue and its potential causes.

Notes

The provided information suggests that the model-resolution stage is a significant contributor to the slow TUI startup time, but the root cause of the event loop blocking issue is still unclear. Further investigation and logging may be necessary to determine the best course of action.

Recommendation

Apply workaround: Investigate and implement caching for model capability probing results, as this may help reduce the model-resolution stage time and potentially alleviate event loop blocking.