Repository navigation
Fix region boundary snapping (Fixes #7) and add worker pool for parallel voxelization - #9
Closed
deloskiytbackup wants to merge 1 commit into
Closed
deloskiytbackup wants to merge 1 commit into
deloskiytbackup wants to merge 1 commit into
Conversation
…or parallel voxelization
Teddy563
added a commit
that referenced
this pull request
Oct 27, 2026
Owner
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of Changes
MAX_REGION_RADIUS = 22_000blocks (~22 km) inEarthRegions.EarthRegions.at()returnsnullinstead of snapping abruptly to a neighboring country grid cell at 25 km).mod/,mod-26.2/, andmod-26.3/.VoxelWorkerandVoxelPool(service/src/voxel-pool.mjsandservice/src/voxel-worker.mjs) usingnode:worker_threads.voxelizeArea) off the main HTTP event loop, scaling across CPU cores and zero-copy transferringvox.buffer.cfg.voxelWorkers), automatic thread scaling based on available CPUs, task queuing, auto-respawn, and graceful fallback to synchronous execution if worker threads are unavailable.service/test/voxel-pool.test.mjs. All 41 service tests pass.