-
Notifications
You must be signed in to change notification settings - Fork 4.1k
storage: investigate larger default range sizes #39717
Copy link
Copy link
Closed
Labels
C-investigationFurther steps needed to qualify. C-label will change.Further steps needed to qualify. C-label will change.
Description
#16954 was a major blocker in being able to increase the default range size from 64 MiB (another potential problem is #22348). Since #16954 has been closed, we can experiment with larger default range sizes.
I ran tpcc on a 3 node cluster with 16 vCPUs, 2500 warehouses, and an average range size of 500 MiB and a max range size of 1 GiB and nothing seemed to blow up.
There were a couple of latency spikes during the ramp-up period of tpcc, but I think they were caused by the destruction of old replicas when the initial splits were merged from setting up the workload (not too sure about this).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C-investigationFurther steps needed to qualify. C-label will change.Further steps needed to qualify. C-label will change.
