aljaz/turso
1
0
Fork 0
mirror of https://github.com/aljazceru/turso.git synced 2026-01-07 02:04:21 +01:00
Code Issues Packages Projects Releases Wiki Activity
8,835 Commits 1 Branch 0 Tags
703cb4a70f87ad44f0a4a2ca11b0caef773c443f
Commit Graph

6 Commits

Author SHA1 Message Date
Pekka Enberg
a5f1bdbc9d Merge 'perf/throughput/turso: Don't interleave concurrent transactions in on…' from Pekka Enberg 
…e connection
With BEGIN CONCURRENT, we cannot use the same connection all the time
because there's no way for the transaction manager to know which
transaction belongs to what "session" -- they're all individual
statements executed in the context of the one connection.
Fixes #3093

Reviewed-by: Jussi Saurio <jussi.saurio@gmail.com>

Closes #3094
 2025-09-14 11:33:20 +03:00
Pekka Enberg
6e9ba4c561 perf/throughput/turso: Don't interleave concurrent transactions in one connection 
With BEGIN CONCURRENT, we cannot use the same connection all the time
because there's no way for the transaction manager to know which
transaction belongs to what "session" -- they're all individual
statements executed in the context of the one connection.

Fixes #3093
 2025-09-14 10:52:56 +03:00
Pekka Enberg
98af9386e2 perf/throughput/turso: Don't execute futures serially 
Looping through the futures means we're essentially executing them
serially.
 2025-09-14 10:07:21 +03:00
Pekka Enberg
0fad30a30d perf/throughput/turso: Async transactions with concurrent mode 
With `BEGIN CONCURRENT`, we should also take advantage of async
transaction processing to maximize concurrency.
 2025-09-13 13:25:16 +03:00
Pekka Enberg
8dc2e738a4 core/throughput: Add per transaction think time support 2025-09-13 13:02:43 +03:00
Pekka Enberg
964dd0cd43 perf: Add simple throughput benchmark 
This adds a simple throughput benchmark for rusqlite and Turso, allowing
to compare the two, but also MVCC and SQLite transactions.
 2025-09-12 07:35:57 +03:00