Skip to content

Commit

Permalink
Remove regionized leveldb 32x32 and 64x64
Browse files Browse the repository at this point in the history
these produce such small file sizes on average that the DB logs would probably take up a significant fraction of the world's footprint.
My gut instinct is that 128 will probably be the sweet spot, as on average it should sit well below the threshold for level 3 compactions, and most worlds would likely fit into a single DB.
256 is probably not worthwhile, but might be worth trying.
  • Loading branch information
dktapps committed Dec 21, 2024
1 parent 6abc40b commit 8027c27
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/world/format/io/WorldProviderManager.php
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ public function __construct(){

//any arbitrary size is supported, but powers of 2 are best
//these are the most likely to be useful
foreach([32, 64, 128, 256] as $regionLength){
foreach([128, 256] as $regionLength){
$this->addProvider(new WritableWorldProviderManagerEntry(
fn(string $path) => RegionizedLevelDB::isValid($path, $regionLength),
fn(string $path, \Logger $logger) => new RegionizedLevelDB($path, $logger, $regionLength),
Expand Down

0 comments on commit 8027c27

Please sign in to comment.