GPU-first gradient boosted decision trees. Fastest-growing tree.
See the code
GPU-first gradient boosted decision trees.
Falcataria moluccana — the falcata — is one of the fastest-growing trees on earth. This one grows them faster too.
Falcata is a CUDA-native GBDT library: a leaf-wise learner whose training loop was rebuilt around batched, level-parallel GPU kernels rather than one split at a time.
feature_fraction < 1, only the
sampled columns are materialized and gathered for histogram construction.
The win scales with the excluded fraction: ~3.4× end-to-end training at
feature_fraction = 0.1 on wide, low-cardinality data, tapering to ~1.1×
at 0.6.__cuda_array_interface__ inputs are
ingested without a host round-trip.quant_mode=stochastic is the speed end:
gradients packed into 4 bins with seeded stochastic rounding (unbiased in
expectation). quant_mode=fixedpoint is the near-lossless end: deterministic
rounding, with an internal outlier-robust gradient scale so rare huge
gradients don't crush the quantization range. Bin counts default to 4 and 64
respectively; override with quant_bins (any value in [2, 65534] —
training refuses counts whose histogram sums could overflow at your row
count). Both modes are bit-reproducible — not just run to run, but across GPU
models and host machines: the same seed trains the bit-identical model on
any CUDA device (verified sm_89 vs sm_120); quant_mode=none is
full precision.cuda_plan=auto) instead of from a pile of
environment variables — every decision guaranteed bit-identical, and
individually overridable for experiments.Booster.predict() transparently runs on
cuML's Forest Inference Library when available (see below); CuPy arrays stay
on the device end to end.Every optimization above must be bit-identical to the reference path, and that is enforced mechanically rather than trusted. A regression-gate suite runs on every commit against a real GPU: a 38-cell lattice of (config × data-shape) training cells fingerprinted by model md5, plan-flip equality cells that prove each planner decision changes nothing, validity assertions, metric floors, and a perf gate against a rolling baseline. A nightly tier adds a config × shape fuzzer with CPU-parity checks plus full-scale gates on real datasets.
import falcata as flc
ds = flc.Dataset(X_train, label=y_train, params={"device_type": "cuda"})
model = flc.train(
{
"objective": "regression",
"device_type": "cuda",
"num_leaves": 255,
"quant_mode": "stochastic", # none | stochastic | fixedpoint
"cuda_precision": "fp32", # fp64 (default) | fp32
"cuda_plan": "auto", # the planner picks the kernels
},
ds,
num_boost_round=1000,
)
With cuML installed (pip install cuml-cu12), Booster.predict() on a
CUDA-trained model transparently runs on NVIDIA's Forest Inference Library —
no API change. 2-D numpy input returns numpy; CuPy (or any
__cuda_array_interface__ array) stays on the device end to end. Converted
FIL models are cached per iteration slice and invalidated automatically when
the booster changes.
preds = model.predict(X_test) # numpy in -> numpy out, FIL under the hood
preds = model.predict(cupy_X) # device in -> device out, no host round-trip
FALCATA_FIL=0 disables the FIL path; without cuML installed, predict
silently falls back to the regular CPU predictor.FALCATA_FIL_PRECISION=single (default) evaluates thresholds in fp32 —
~0.01% of rows near a split threshold can route differently than the exact
predictor; double restores exact routing (~1e-13), native uses the
model's own precision.device_type=cuda.pip install falcata
On Linux x86_64 this installs a prebuilt wheel — no compilation, no CUDA toolkit needed — with native GPU code for sm_60 through sm_120 (P100, GTX 10xx, V100, T4, A100, RTX 30xx/40xx, H100, B100/B200, RTX 50xx). A GPU outside that list fails fast with a message pointing at the source build below.
Everywhere else (and with pip install --no-binary falcata falcata), pip
builds from source, which needs the CUDA toolkit (>= 11.0), CMake >= 3.28,
a C++17 compiler and Python >= 3.10. Nothing else:
the source distribution vendors every dependency, so no git clone and no
submodule dance.
The build detects the GPU(s) in the machine and compiles only for those (15–20 minutes on typical hardware). When no GPU is visible at build time — docker build stages, CPU-only CI — it instead targets every architecture the toolkit supports (sm_60 upward on CUDA 11/12, sm_75 upward on CUDA 13+, plus PTX for the newest so future cards still run), which takes several times longer. To build for a card other than the one present, or to pick one explicitly:
# RTX 5090 = 120, RTX 4090 = 89, A100 = 80, T4 = 75
pip install falcata --config-settings=cmake.define.CMAKE_CUDA_ARCHITECTURES=89
No GPU? There is a CPU build, though it is not what this library is for:
pip install falcata --config-settings=cmake.define.USE_CUDA=OFF
Multi-GPU training additionally needs NCCL and its headers — on
Debian/Ubuntu sudo apt-get install libnccl2 libnccl-dev, or
conda install -c conda-forge nccl. BUILD_WITH_SHARED_NCCL links
libnccl.so instead of the static archive, which avoids nvlink failures
against some static NCCL builds on newer architectures:
pip install falcata \
--config-settings=cmake.define.USE_NCCL=ON \
--config-settings=cmake.define.BUILD_WITH_SHARED_NCCL=ON
With USE_NCCL=ON but no NCCL headers on the include path, configuration
fails with Could NOT find NCCL (missing: NCCL_INCLUDE_DIR).
git clone https://github.com/MechaFauna-ai/Falcata.git
cd Falcata
git submodule update --init --recursive
sh build-python.sh install --cuda
Windows. CUDA builds and runs on Windows too (single-GPU). Use the Ninja
generator from an x64 Native Tools Command Prompt for VS (so nvcc finds
cl.exe), then install against the compiled DLL:
cmake -B build -S . -G Ninja -DUSE_CUDA=ON -DCMAKE_BUILD_TYPE=Release
cmake --build build -j
sh ./build-python.sh install --precompile
See docs/Installation-Guide.rst for the details —
notably, use Ninja (not the VS generator), and if nvcc rejects your MSVC as an
"unsupported Microsoft Visual Studio version" add
-DCMAKE_CUDA_FLAGS=-allow-unsupported-compiler.
Falcata installs under its own name only, so it coexists with stock LightGBM in
one environment; import lightgbm keeps resolving to LightGBM.
Falcata began as a fork of LightGBM and deliberately stays interoperable at the data boundaries:
.dataset) interchange in both directions.quant_mode,
cuda_precision, cuda_plan) are new names that upstream simply ignores.LGBM_* C API names remain as aliases for FLC_*. The
Python package is import falcata only — code written against
import lightgbm needs its import changed, nothing else.See docs/design/format-compatibility.md.
See CONTRIBUTING.md. Human and AI contributors are welcome on the same terms.
MIT — see LICENSE and NOTICE. Falcata derives from LightGBM (copyright Microsoft Corporation and the LightGBM developers, MIT); that copyright is retained. Falcata is not affiliated with, endorsed by, or supported by Microsoft or the LightGBM maintainers.
Falcata builds on the algorithms described in:
(top 30 of 336)
C++
47.5%
Python
23.8%
Cuda
14.8%
R
8.0%
C
2.8%
Shell
1.4%
GPU-first gradient boosted decision trees. Fastest-growing tree.
See the code
GPU-first gradient boosted decision trees.
Falcataria moluccana — the falcata — is one of the fastest-growing trees on earth. This one grows them faster too.
Falcata is a CUDA-native GBDT library: a leaf-wise learner whose training loop was rebuilt around batched, level-parallel GPU kernels rather than one split at a time.
feature_fraction < 1, only the
sampled columns are materialized and gathered for histogram construction.
The win scales with the excluded fraction: ~3.4× end-to-end training at
feature_fraction = 0.1 on wide, low-cardinality data, tapering to ~1.1×
at 0.6.__cuda_array_interface__ inputs are
ingested without a host round-trip.quant_mode=stochastic is the speed end:
gradients packed into 4 bins with seeded stochastic rounding (unbiased in
expectation). quant_mode=fixedpoint is the near-lossless end: deterministic
rounding, with an internal outlier-robust gradient scale so rare huge
gradients don't crush the quantization range. Bin counts default to 4 and 64
respectively; override with quant_bins (any value in [2, 65534] —
training refuses counts whose histogram sums could overflow at your row
count). Both modes are bit-reproducible — not just run to run, but across GPU
models and host machines: the same seed trains the bit-identical model on
any CUDA device (verified sm_89 vs sm_120); quant_mode=none is
full precision.cuda_plan=auto) instead of from a pile of
environment variables — every decision guaranteed bit-identical, and
individually overridable for experiments.Booster.predict() transparently runs on
cuML's Forest Inference Library when available (see below); CuPy arrays stay
on the device end to end.Every optimization above must be bit-identical to the reference path, and that is enforced mechanically rather than trusted. A regression-gate suite runs on every commit against a real GPU: a 38-cell lattice of (config × data-shape) training cells fingerprinted by model md5, plan-flip equality cells that prove each planner decision changes nothing, validity assertions, metric floors, and a perf gate against a rolling baseline. A nightly tier adds a config × shape fuzzer with CPU-parity checks plus full-scale gates on real datasets.
import falcata as flc
ds = flc.Dataset(X_train, label=y_train, params={"device_type": "cuda"})
model = flc.train(
{
"objective": "regression",
"device_type": "cuda",
"num_leaves": 255,
"quant_mode": "stochastic", # none | stochastic | fixedpoint
"cuda_precision": "fp32", # fp64 (default) | fp32
"cuda_plan": "auto", # the planner picks the kernels
},
ds,
num_boost_round=1000,
)
With cuML installed (pip install cuml-cu12), Booster.predict() on a
CUDA-trained model transparently runs on NVIDIA's Forest Inference Library —
no API change. 2-D numpy input returns numpy; CuPy (or any
__cuda_array_interface__ array) stays on the device end to end. Converted
FIL models are cached per iteration slice and invalidated automatically when
the booster changes.
preds = model.predict(X_test) # numpy in -> numpy out, FIL under the hood
preds = model.predict(cupy_X) # device in -> device out, no host round-trip
FALCATA_FIL=0 disables the FIL path; without cuML installed, predict
silently falls back to the regular CPU predictor.FALCATA_FIL_PRECISION=single (default) evaluates thresholds in fp32 —
~0.01% of rows near a split threshold can route differently than the exact
predictor; double restores exact routing (~1e-13), native uses the
model's own precision.device_type=cuda.pip install falcata
On Linux x86_64 this installs a prebuilt wheel — no compilation, no CUDA toolkit needed — with native GPU code for sm_60 through sm_120 (P100, GTX 10xx, V100, T4, A100, RTX 30xx/40xx, H100, B100/B200, RTX 50xx). A GPU outside that list fails fast with a message pointing at the source build below.
Everywhere else (and with pip install --no-binary falcata falcata), pip
builds from source, which needs the CUDA toolkit (>= 11.0), CMake >= 3.28,
a C++17 compiler and Python >= 3.10. Nothing else:
the source distribution vendors every dependency, so no git clone and no
submodule dance.
The build detects the GPU(s) in the machine and compiles only for those (15–20 minutes on typical hardware). When no GPU is visible at build time — docker build stages, CPU-only CI — it instead targets every architecture the toolkit supports (sm_60 upward on CUDA 11/12, sm_75 upward on CUDA 13+, plus PTX for the newest so future cards still run), which takes several times longer. To build for a card other than the one present, or to pick one explicitly:
# RTX 5090 = 120, RTX 4090 = 89, A100 = 80, T4 = 75
pip install falcata --config-settings=cmake.define.CMAKE_CUDA_ARCHITECTURES=89
No GPU? There is a CPU build, though it is not what this library is for:
pip install falcata --config-settings=cmake.define.USE_CUDA=OFF
Multi-GPU training additionally needs NCCL and its headers — on
Debian/Ubuntu sudo apt-get install libnccl2 libnccl-dev, or
conda install -c conda-forge nccl. BUILD_WITH_SHARED_NCCL links
libnccl.so instead of the static archive, which avoids nvlink failures
against some static NCCL builds on newer architectures:
pip install falcata \
--config-settings=cmake.define.USE_NCCL=ON \
--config-settings=cmake.define.BUILD_WITH_SHARED_NCCL=ON
With USE_NCCL=ON but no NCCL headers on the include path, configuration
fails with Could NOT find NCCL (missing: NCCL_INCLUDE_DIR).
git clone https://github.com/MechaFauna-ai/Falcata.git
cd Falcata
git submodule update --init --recursive
sh build-python.sh install --cuda
Windows. CUDA builds and runs on Windows too (single-GPU). Use the Ninja
generator from an x64 Native Tools Command Prompt for VS (so nvcc finds
cl.exe), then install against the compiled DLL:
cmake -B build -S . -G Ninja -DUSE_CUDA=ON -DCMAKE_BUILD_TYPE=Release
cmake --build build -j
sh ./build-python.sh install --precompile
See docs/Installation-Guide.rst for the details —
notably, use Ninja (not the VS generator), and if nvcc rejects your MSVC as an
"unsupported Microsoft Visual Studio version" add
-DCMAKE_CUDA_FLAGS=-allow-unsupported-compiler.
Falcata installs under its own name only, so it coexists with stock LightGBM in
one environment; import lightgbm keeps resolving to LightGBM.
Falcata began as a fork of LightGBM and deliberately stays interoperable at the data boundaries:
.dataset) interchange in both directions.quant_mode,
cuda_precision, cuda_plan) are new names that upstream simply ignores.LGBM_* C API names remain as aliases for FLC_*. The
Python package is import falcata only — code written against
import lightgbm needs its import changed, nothing else.See docs/design/format-compatibility.md.
See CONTRIBUTING.md. Human and AI contributors are welcome on the same terms.
MIT — see LICENSE and NOTICE. Falcata derives from LightGBM (copyright Microsoft Corporation and the LightGBM developers, MIT); that copyright is retained. Falcata is not affiliated with, endorsed by, or supported by Microsoft or the LightGBM maintainers.
Falcata builds on the algorithms described in:
(top 30 of 336)
C++
47.5%
Python
23.8%
Cuda
14.8%
R
8.0%
C
2.8%
Shell
1.4%