tursodatabase / tursodatabase/libsql-js
consider moving the deserialization code from the main thread to the workers
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 335
- Forks
- 48
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 3
Description
in here, https://github.com/tursodatabase/libsql-js/blob/1df5a35989c93ba9000a7facdf6dd726d73c702f/src/statement.rs, we're blocking the JS main thread for deserializing the native values, ideally we could make it happen on worker threads to free some cycles from the JS thread to do something else.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with src/statement.rs at the deserialization path described in the issue, and trace how native values are converted before reaching the JavaScript API. Determine the worker-thread boundary and verify that deserialization no longer blocks the JS main thread while preserving the existing better-sqlite3-compatible behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rust
- Domain
- backend, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100