alihan/rqlite-distributed-sql
1
0
Fork 0
mirror of https://github.com/rqlite/rqlite.git synced 2022-10-30 02:37:32 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update PERFORMANCE.md

Browse Source
This commit is contained in:
Philip O'Toole
2022-10-20 18:40:06 -04:00
committed by GitHub
parent 03d3159dc1
commit 970ae46ec4
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
DOC/PERFORMANCE.md
View File

@@ -24,7 +24,7 @@ The more SQLite statements you can include in a single request to a rqlite node,
By using the [bulk API](https://github.com/rqlite/rqlite/blob/master/DOC/BULK.md), transactions, or both, throughput will increase significantly, often by 2 orders of magnitude. This speed-up is due to the way Raft and SQLite work. So for high throughput, execute as many operations as possible within a single transaction.
## Queued Writes
If you can tolerate a small risk of some data loss in the event that a node crashes, you could consider using the [Queued Writes API](https://github.com/rqlite/rqlite/blob/master/DOC/QUEUED_WRITES.md).
If you can tolerate a small risk of some data loss in the event that a node crashes, you could consider using the [Queued Writes API](https://github.com/rqlite/rqlite/blob/master/DOC/QUEUED_WRITES.md). Using Queued Writes can easily give you orders of magnitude improvement in perfomance.
## Use more powerful hardware
Obviously running rqlite on better disks, better networks, or both, will improve performance.