perf: concurrent quota refresh for all accounts#354
Closed
Mag1cFall wants to merge 1 commit intolbjlaq:mainfrom
Closed
perf: concurrent quota refresh for all accounts#354Mag1cFall wants to merge 1 commit intolbjlaq:mainfrom
Mag1cFall wants to merge 1 commit intolbjlaq:mainfrom
Conversation
Owner
|
感谢您的贡献!🎉 此 PR 的更改已被手动集成到 v3.3.16 版本中。 相关更新已包含在以下文件中:
再次感谢您对 Antigravity Tools 项目的支持! Thank you for your contribution! 🎉 The changes from this PR have been manually integrated into v3.3.16. The updates are documented in:
Thank you again for your support of the Antigravity Tools project! |
Owner
|
已集成到 v3.3.16,关闭此 PR。 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Refactored
refresh_all_quotascommand from sequential to concurrent execution usingfutures::future::join_all.futures::future::join_allto spawn concurrent async tasksSafety Analysis
The original code had a comment:
// 串行处理以确保持久化安全 (SQLite)This comment is legacy/outdated. Current storage implementation:
Each account is stored in a separate JSON file (
{account_id}.json), not SQLite. Concurrent writes to different files are completely safe - no race conditions or data corruption possible.