-
Notifications
You must be signed in to change notification settings - Fork 2.8k
perf: Refine the Model Manager code #3099
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here's a review of the code with suggestions for improvements:
Potential Issues
SQL Injection: Using
exec_sqldirectly can lead to SQL injection if not properly sanitized.Concurrency Handling: The current use of locking might be inefficient. For better performance, consider using Python's
asynciolibrary or a database-specific connection pool that supports concurrent transactions.Code Complexity: The function
embedding_by_documentlacks proper error handling and logging. Consider adding exception handling and log statements.Unused Code Block: The final block inside
update_statuswill always run because the lock is acquired but never released if an error occurs within the loop. This could lead to resource leaks.Optimization Suggestions
Parameter Validation: Before building the query, validate
params_dictto ensure it only contains necessary fields.Batch Processing: If multiple documents need embedding at once, consider processing them in batches to reduce overhead.
Database Connection Pooling: Use a connection pool from libraries like SQLAlchemy or Django ORM to manage database connections more efficiently.
Locks: For high concurrency scenarios, consider implementing optimistic locks instead of pessimistic (locking). SQLite does not support this directly, so you may need to switch to PostgreSQL or another database that supports it.
Error Handling: Implement robust error handling to manage exceptions during document embedding tasks and log errors to improve troubleshooting.
Logging: Add comprehensive logging to track the flow and status of document embeddings, which helps in debugging and monitoring.
This version simplifies the logic for embedding documents by breaking down the task into smaller asynchronous functions. It uses a transaction-safe approach with
async_db_queryto safely execute queries. Make sure to adjust settings likebatch_size,prompt_template, and other parameters based on your specific requirements and environment.