Papers › MABSplit: Faster Forest Training Using Multi-Armed Bandits

MABSplit: Faster Forest Training Using Multi-Armed Bandits

14 Dec 2022arXiv:2212.07473archive 2025-07-28

Mo Tiwari, Ryan Kang, Je-Yong Lee, Sebastian Thrun, Chris Piech, Ilan Shomorony, Martin Jinye Zhang

Random forests are some of the most widely used machine learning models today, especially in domains that necessitate interpretability. We present an algorithm that accelerates the training of random forests and other popular tree-based learning methods. At the core of our algorithm is a novel node-splitting subroutine, dubbed MABSplit, used to efficiently find split points when constructing decision trees. Our algorithm borrows techniques from the multi-armed bandit literature to judiciously determine how to allocate samples and computational power across candidate split points. We provide theoretical guarantees that MABSplit improves the sample complexity of each node split from linear to logarithmic in the number of data points. In some settings, MABSplit leads to 100x faster training (an 99% reduction in training time) without any decrease in generalization performance. We demonstrate similar speedups when MABSplit is used across a variety of forest-based variants, such as Extremely Random Forests and Random Patches. We also show our algorithm can be used in both classification and regression tasks. Finally, we show that MABSplit outperforms existing methods in generalization performance and feature importance calculations under a fixed computational budget. All of our experimental results are reproducible via a one-line script at https://github.com/ThrunGroup/FastForest.

PaperPDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

Syntology holds a reference implementation of MABSplit, generated from the paper text (not the authors' code), at level 2 on Syntology's ladder: V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)” (quoted from Syntology's server card). No rung compares this code against the authors' implementation. For agents: get_reference_implementation(name='MABSplit') (how to connect); the free check have('2212.07473') needs no token.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 14 code samples harvested from 1 repository linked to this paper: 7 ran (of which 1 constructed an object rather than computing a result; 2 with no instrument failure: 1 honoured, 0 violated, 1 with no contract checked; 5 where Syntology's instrument failed) · 7 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 3 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 14 samples from 1 repository, 7 ran (2 with no instrument failure; 5 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

thrungroup/fastforest officialmentioned in paperSyntology: 14 samples, 7 ran (5 instrument-failed) · 7 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

14 samples harvested: 7 ran (of which 1 constructed an object rather than computing a result; 2 with no instrument failure: 1 honoured, 0 violated, 1 with no contract checked; 5 where Syntology's instrument failed) · 7 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
2ran · our draft was wrong
3ran; the contract check could not run
1ran
7unverified

Licence: 14 of the 14 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from thrungroup/fastforest. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

thrungroup/fastforest official repository 14 samples, 7 ran (5 instrument-failed) · 7 unverified
Histogram utils/solvers.py ran no licence file found · pointer only · 186f8aa9fefbb971 · report fixture: returned Histogram · level recorded 2026-09-22
choose_bin_type utils/solvers.py ran · our draft was wrong no licence file found · pointer only · 0753bfbc13b72385 · report fixture: signature D:int/0/int, N:int/0/int, B:int/0/int · returned str · level recorded 2026-09-22
class_to_idx utils/solvers.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 8a5b76b92538164a · report fixture: signature classes:ndarray/1/<U4 · returned dict · level recorded 2026-09-22
get_entropy in 18 papers
census: 7 implementations from 7 papers, 7 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 2 of 2, arg 1: rank 2, kind int, dtype int64
utils/solvers.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted no licence file found · pointer only · c11ef2293c1894fc · report fixture: signature counts_vec:ndarray/2/int, ret_var:bool/0/bool, pop_size:NoneType/0/?, n:NoneType/0/? · returned ndarray · level recorded 2026-09-22
get_gini utils/solvers.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted no licence file found · pointer only · bdb81f9073baf931 · report fixture: signature counts_vec:ndarray/2/int, ret_var:bool/0/bool, pop_size:ndarray/1/int, n:ndarray/1/int · returned tuple · level recorded 2026-09-22
get_mse in 5 papers utils/solvers.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted no licence file found · pointer only · 2ccb8b761652b05e · report fixture: signature args:ndarray/2/float, ret_var:bool/0/bool, pop_size:NoneType/0/? · returned ndarray · level recorded 2026-09-22
welford_variance_calc utils/solvers.py ran · honoured contract fingerprinted no licence file found · pointer only · 142b3ed4bdb7655f · report fixture: signature n1:int/0/int, mean1:float/0/float, var1:float/0/float, n2:int/0/int, mean2:float/0/float, var2:float/0/float · returned float · level recorded 2026-09-22
empty_histograms utils/solvers.py unverified no licence file found · pointer only · 710b4b08c61beede · report
get_impurity_fn utils/solvers.py unverified no licence file found · pointer only · 58d5bd11c8ad825b · report
get_impurity_reductions utils/solvers.py unverified no licence file found · pointer only · c67e06269033ed88 · report
make_histograms utils/solvers.py unverified no licence file found · pointer only · 06f76a1bb6683cb8 · report
sample_targets utils/solvers.py unverified no licence file found · pointer only · d7020c0c5dc36ace · report
solve_mab utils/solvers.py unverified no licence file found · pointer only · f94e0a35fecdcb2b · report
time_measured_fit experiments/runtime_exps/compare_runtimes.py unverified no licence file found · pointer only · d9ea6ab91cff145f · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. For a generated assembly, an independent peer is a second implementation generated separately from the same paper text; neither implementation read the authors' code. At level 2 the two agreed numerically on the fixture's inputs; level 3 is recorded when property tests derived from the paper also passed on both, and each level 3 card prints how many its report lists. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it. A generated assembly's label was set when its code was generated for the method, and no model judged it; its card prints it as "by construction" or "not judged by a model". Where an assembly's phrase has no constructed figure, a brick that ran is not among the harvested samples this build reads, and whether a brick's run only constructed an object is read from that brick's harvested sample, so the figure was not counted; it does not say there were none.

2 assemblies on this paper: 1 harvested, 1 generated.

generated Assembly for MABSplit (graph method: MABSplit), generated from the paper text, not the repository's code. 1 brick; individually on a fixture: 1 ran (1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. Ran end-to-end against an independent peer (level 2).

label matches by construction: the code was generated for this method (not judged by a model)

  1. update_histogram_statistics entry · level 2 · ran · 3001f3501ca92f71d69dc60ba0f238b55272276e3c00c151384eb7533dc0b84b

harvested Assembly for MABSplit (graph method: MABSplit). 13 bricks; individually on a fixture: 7 ran (of which 1 constructed an object rather than computing a result; 2 with no instrument failure: 1 honoured, 0 violated, 1 with no contract checked; 5 where Syntology's instrument failed) · 6 unverified. The assembly has not been run end-to-end.

  1. solve_mab entry · level 0 · unverified · f94e0a35fecdcb2b
  2. empty_histograms helper · level 0 · unverified · 710b4b08c61beede
  3. make_histograms helper · level 0 · unverified · 06f76a1bb6683cb8
  4. sample_targets sampler · level 0 · unverified · d7020c0c5dc36ace
  5. Histogram helper · level 1 · ran · 186f8aa9fefbb971
  6. choose_bin_type helper · level 1 · ran · our draft was wrong · 0753bfbc13b72385
  7. get_impurity_reductions loss · level 0 · unverified · c67e06269033ed88
  8. class_to_idx helper · level 1 · ran · our draft was wrong · 8a5b76b92538164a
  9. welford_variance_calc helper · level 1 · ran · honoured contract · 142b3ed4bdb7655f
  10. get_impurity_fn helper · level 0 · unverified · 58d5bd11c8ad825b
  11. get_entropy helper · level 1 · ran; the contract check could not run (RAISES) · c11ef2293c1894fc
  12. get_gini helper · level 1 · ran; the contract check could not run (RAISES) · bdb81f9073baf931
  13. get_mse helper · level 1 · ran; the contract check could not run (RAISES) · 2ccb8b761652b05e

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2212.07473") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Feature ImportanceMulti-Armed Bandits

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections