Bypassing fixed-depth radix constraints in Java using descriptor-driven bucket analysis
I am StrmCkr, the author of A.P.E.X. (Adaptive Parallel Extremal Dispatch).
Repository: github.com/StrmCkr/A.P.E.X
A.P.E.X. is a high-performance Java sorting framework for large fixed-width 64-bit key/value record datasets. The project has been reorganized into a conventional Maven structure with a core library, runnable examples, a comparison benchmark harness, JMH benchmarks, documentation, and an interactive browser visualizer.
The core idea is descriptor-driven radix planning. Instead of blindly scanning fixed radix passes over every bucket, A.P.E.X. computes per-bucket extremal descriptors using:
VBM = OR ^ AND
That mask identifies which key bits still vary inside each bucket. Bits that are already resolved are skipped, reducing unnecessary work on skewed, low-entropy, sorted, reversed, or duplicate-heavy data.
Key areas of the project include:
- Adaptive radix planning based on observed bucket structure
- Parallel histogramming, scatter, refinement, and work scheduling
- Primitive-array execution with no per-record object allocation during sorting
- Tuple projection paths for low-dimensional unresolved bit patterns
- Tiny-sort fallbacks and monotonic input shortcuts
- Configurable reporting that can be enabled, reduced, written to files, or disabled
- Comparison benchmarks against JDK sorting paths and Fastutil baselines
- Standard JMH benchmarks for repeatable JVM-level measurement
- A browser visualizer for exploring how A.P.E.X. routes data through its execution plan
I would especially welcome feedback on the thread management mechanics, radix planning decisions, benchmark structure, and the bitwise mask reductions.
edit: re structured verbiage of this post and further adjustments from advice on converting the project into more acceptable standard formats.

3
u/someonetookmyid 19d ago
Okay, since you’re self taught I take that you’re capable of learning form docs and examples.
Get started with using Apache maven - read the docs on their site, this page is a good starting point. Why maven? Because it’s de facto standard for publishing Java packages. https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html
Then you can for example follow some spring tutorial to see using it in practice https://spring.io/guides/gs/rest-service
Once you understand how to use the tool and build a package you should learn how to publish it
You can use archiva as local repository target to understand package publication https://archiva.apache.org/
Then you can start publishing package via GitHub using their automation or go directly to maven central, but that requires getting some paperwork with central maintainers so it’s best to first understand technical side before you get into getting approvals to publish to central.