Skip to content

Commit

Permalink
update thread docs
Browse files Browse the repository at this point in the history
  • Loading branch information
@capjamesg
capjamesg committed Oct 18, 2024
1 parent cb0e073 commit 52d285a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -890,7 +890,7 @@ In development, the goal should be making the query engine as fast as possible.

## Deployment considerations

JameSQL should work when used in multiple threads. Thread locks are implemented for both read and write operations, to ensure consistency.
Progress is being made on making JameSQL thread safe, but there are still some issues to work out. It is recommended that you run JameSQL in a single-threaded environment.

It is recommended that you cache responses from JameSQL. While it takes < 1ms to process many JameSQL queries, reading a set of results from a cache will be faster.

Expand Down

0 comments on commit 52d285a

Please sign in to comment.