aboutsummaryrefslogtreecommitdiff
path: root/batch_benchmark_test.go
diff options
context:
space:
mode:
authorXiang Li <xiangli.cs@gmail.com>2015-11-04 15:12:18 -0800
committerXiang Li <xiangli.cs@gmail.com>2015-11-06 09:39:17 -0800
commite67705ed6348675b7bae405ebeb37bb69b53a96d (patch)
tree896094dfe1466aa5a017424ee19a434dbf9f35cb /batch_benchmark_test.go
parentMerge pull request #428 from lukechampine/patch-1 (diff)
downloaddedo-e67705ed6348675b7bae405ebeb37bb69b53a96d.tar.gz
dedo-e67705ed6348675b7bae405ebeb37bb69b53a96d.tar.xz
do not grow dbsize agressively
Only grow the database size when the high watermark increases. We also grows the database size a little bit aggressively to save a few ftruncates. I have tested this on various environments. The performance impact is ignorable with 16MB over allocation. Without over allocation, the performance might decrease 100% when each Tx.Commit needs a new page on a very slow disk (seek time dominates the total write).
Diffstat (limited to 'batch_benchmark_test.go')
0 files changed, 0 insertions, 0 deletions