Browse Source

cs: clarify where 24 comes from in maxMsgSizeBytes (wal.go)

pull/4186/head
Anton Kaliaev 5 years ago
parent
commit
43aed989ac
1 changed files with 4 additions and 1 deletions
  1. +4
    -1
      consensus/wal.go

+ 4
- 1
consensus/wal.go View File

@ -20,7 +20,10 @@ import (
const (
// amino overhead + time.Time + max consensus msg size
// TODO: Can we clarify better where 24 comes from precisely?
//
// q: where 24 bytes are coming from?
// a: cdc.MustMarshalBinaryBare(empty consensus part msg) = 14 bytes. +10
// bytes just in case amino will require more space in the future.
maxMsgSizeBytes = maxMsgSize + 24
// how often the WAL should be sync'd during period sync'ing


Loading…
Cancel
Save