Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Avoid Python GIL in write_to, sorting, Levenshtein #105

Closed
ashvardanian opened this issue Feb 29, 2024 · 1 comment
Closed

Avoid Python GIL in write_to, sorting, Levenshtein #105

ashvardanian opened this issue Feb 29, 2024 · 1 comment
Assignees
@ashvardanian
Labels
good first issue Good for newcomers performance Performance related discussion or suggestion python released

Comments

@ashvardanian
Copy link
Owner

Saving to disk is an IO-intensive operation. Sorting and string alignments are also quite expensive. Unlocking the GIL we can allow multi-threaded Python scripts to perform such operations concurrently, not hurting each other.
@ashvardanian ashvardanian added good first issue Good for newcomers performance Performance related discussion or suggestion python labels Feb 29, 2024
@ashvardanian ashvardanian self-assigned this Mar 17, 2024
ashvardanian pushed a commit that referenced this issue Mar 18, 2024
@semantic-release-bot
Build: Released 3.6.8 [skip ci]
6b5ea62 
## [3.6.8](v3.6.7...v3.6.8) (2024-03-18)

### Fix

* Asset naming ([eb591e9](eb591e9))
* NULL-terminating path ([7c910bf](7c910bf))

### Improve

* Unlock GIL in `Str.write_to` ([0d4af91](0d4af91)), closes [#105](#105)
@ashvardanian
Copy link
Owner Author

🎉 This issue has been resolved in version 3.6.8 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ashvardanian ashvardanian

Labels
good first issue Good for newcomers performance Performance related discussion or suggestion python released
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ashvardanian