Skip to content

Commit

Permalink
Remove sync-log=false from how to run sysbench (pingcap#3532)
Browse files Browse the repository at this point in the history
Co-authored-by: ti-srebot <66930949+ti-srebot@users.noreply.github.com>
  • Loading branch information
Joyinqin and ti-srebot authored Aug 4, 2020
1 parent 2a7276b commit 383bd65
Showing 1 changed file with 0 additions and 6 deletions.
6 changes: 0 additions & 6 deletions benchmark/benchmark-tidb-using-sysbench.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,8 +59,6 @@ enabled = true

Higher log level also means better performance for TiKV.

As TiKV is deployed in clusters, the Raft algorithm can guarantee that data is written into most of the nodes. Therefore, except the scenarios where data safety is extremely important, `sync-log` can be disabled in raftstore.

There are 2 Column Families (Default CF and Write CF) on TiKV cluster which are mainly used to store different types of data. For the Sysbench test, the Column Family that is used to import data has a constant proportion among TiDB clusters:

Default CF : Write CF = 4 : 1
Expand All @@ -69,8 +67,6 @@ Configuring the block cache of RocksDB on TiKV should be based on the machine’

```toml
log-level = "error"
[raftstore]
sync-log = false
[rocksdb.defaultcf]
block-cache-size = "24GB"
[rocksdb.writecf]
Expand All @@ -81,8 +77,6 @@ For TiDB 3.0 or later versions, you can also use the shared block cache to confi

```toml
log-level = "error"
[raftstore]
sync-log = false
[storage.block-cache]
capacity = "30GB"
```
Expand Down

0 comments on commit 383bd65

Please sign in to comment.