Skip to content

Commit

Permalink
add threading docs
Browse files Browse the repository at this point in the history
  • Loading branch information
capjamesg committed Oct 18, 2024
1 parent 1cb3b23 commit df1d416
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
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 is not thread safe. This is because non-atomic mutations are made to record `_score` values during query computation. This may be fixed in a future release, although there are no immediate plans to do so.
JameSQL should work when used in multiple threads. Thread locks are implemented for both read and write operations, to ensure consistency.

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 df1d416

Please sign in to comment.