You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Anyone experiencing GLM performance with the new quota? #14011
I re-started my GLM account with their hourly and weekly quota. I havent even used GLM5 yet and my weekly quota reached 52% in 6 hours of usage and I am wondering if anyone else is experiencing the same. I actually spent most the 6 hours waiting for the model to respond since its slow as hell.
Here is a example of how slow GLM (44 minutes to change 12 files by removing the path aliases):
Path Alias Removal Complete! ✅
All 8 tasks completed successfully:
Configuration Changes:
✅ Removed baseUrl and paths from tsconfig.json
✅ Changed moduleResolution from "NodeNext" to "node"
✅ Removed @agentS and @core moduleNameMapper from jest.config.cjs
✅ Removed unused @interfaces and @types moduleNameMapper entries
Import Conversions:
✅ src/index.ts: 13 imports converted
✅ src/dashboard/: 18 imports (4 files)
✅ src/interfaces/: 5 imports (2 files)
✅ src/agents/: 36 imports (6 files)
Verification:
✅ No path aliases remain in src/
✅ Typecheck: PASS with 0 errors
✅ Tests: 6/6 modified tests pass
✅ Documentation: Cleaned path alias reference
Key Fixes:
Added explicit type annotation for Express app (dashboard/server.ts)
Fixed import in implementation plan documentation
Commits Created: 9
All changes are committed and ready for push
▣ Build · glm-4.7 · 44m 14s
These issues discuss similar concerns with GLM performance, quota consumption, and account balance problems. Please review them to see if your issue is related.
Activity
github-actions commentedon Feb 17, 2026
This issue might be a duplicate of existing issues. Please check:
These issues discuss similar concerns with GLM performance, quota consumption, and account balance problems. Please review them to see if your issue is related.
github-actions commentedon Apr 19, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.