satellite/orders: decrease FlushBatchSize default to 1000
The previous default FlushBatchSize of 10000 was causing major slow down in select and insert statements on bucket_bandwidth_rollups. We saw on the saltlake satellite that a FlushBatchSize of 1000 helped reduce contention and query latency. Change-Id: Ib95e73482219bc5aedc11925b1849fa5999774ba
This commit is contained in:
parent
932039ebdf
commit
c290e5ac9a
@ -34,7 +34,7 @@ var (
|
||||
type Config struct {
|
||||
EncryptionKeys EncryptionKeys `help:"encryption keys to encrypt info in orders" default:""`
|
||||
Expiration time.Duration `help:"how long until an order expires" default:"48h"` // 2 days
|
||||
FlushBatchSize int `help:"how many items in the rollups write cache before they are flushed to the database" devDefault:"20" releaseDefault:"10000"`
|
||||
FlushBatchSize int `help:"how many items in the rollups write cache before they are flushed to the database" devDefault:"20" releaseDefault:"1000"`
|
||||
FlushInterval time.Duration `help:"how often to flush the rollups write cache to the database" devDefault:"30s" releaseDefault:"1m"`
|
||||
NodeStatusLogging bool `hidden:"true" help:"deprecated, log the offline/disqualification status of nodes" default:"false"`
|
||||
OrdersSemaphoreSize int `help:"how many concurrent orders to process at once. zero is unlimited" default:"2"`
|
||||
|
2
scripts/testdata/satellite-config.yaml.lock
vendored
2
scripts/testdata/satellite-config.yaml.lock
vendored
@ -416,7 +416,7 @@ identity.key-path: /root/.local/share/storj/identity/satellite/identity.key
|
||||
# orders.expiration: 48h0m0s
|
||||
|
||||
# how many items in the rollups write cache before they are flushed to the database
|
||||
# orders.flush-batch-size: 10000
|
||||
# orders.flush-batch-size: 1000
|
||||
|
||||
# how often to flush the rollups write cache to the database
|
||||
# orders.flush-interval: 1m0s
|
||||
|
Loading…
Reference in New Issue
Block a user