-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Storage 2017-03-27, Storage 2017-04-17
Especially for workloads with updates that grow records. For example I ran a wtperf workload with the following configuration (requires changes for WT-2366):
conn_config="cache_size=2GB,checkpoint=(wait=60)" table_config="type=file,leaf_page_max=32k,leaf_value_max=128k,split_pct=90" # The values are starting small, insert a lot so our database grows larger than # cache quickly. icount=20000000 report_interval=5 run_time=3000 populate_threads=1 # Continue inserting new records. threads=((count=1,inserts=1,throttle=1000),(count=4,update=1,update_delta=100)) # Start with small values and let them grow slowly to large values. value_sz=20 value_sz_max=65536
After the test has run for half an hour the database ends up with an unbalanced distribution of record counts per leaf page (picture to follow).