← Back to home
Comparison · Analytics

mlr3mbo vs mlr3tuning

A side-by-side editorial comparison of mlr3mbo and mlr3tuning — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:mlr3hyperparameter-tuning

mlr3mbo vs mlr3tuning: at a glance

Featuremlr3mbomlr3tuning
SectorAnalyticsAnalytics
Velocity score2.52.5
Sparks · 30d00
Top themesbayesian-optimization, mlr3, hyperparameter-tuning, r-statsmlr3, hyperparameter-tuning, async-optimization, callbacks
Last editorial update3h ago1h ago
WebsiteVisit →Visit →

What is mlr3mbo?

mlr3mbo picked its defaults from a benchmark study, not from taste

mlr3mbo does model-based and Bayesian optimisation for mlr3. Its 1.0.0 release added a dictionary of pre-built acquisition-function optimisers and, more consequentially, replaced the default surrogate, acquisition function and optimiser settings with values derived from a large-scale benchmark study. The releases since are corrections to the acquisition-optimiser path exposed by that new default configuration.

Read the full mlr3mbo trajectory →

What is mlr3tuning?

mlr3tuning is rebuilding its async machinery under a stable public surface

mlr3tuning provides hyperparameter optimization for the mlr3 ecosystem, and its recent history is dominated by the asynchronous tuning path: archive freezing, callback stages around queue evaluation, and version-locked compatibility with the rush backend. Releases pair a small feature with several fixes and an explicit compatibility line naming the mlr3 or rush version they track. The most recent release drops all workarounds for older rush versions, which suggests that dependency has stabilized enough to require rather than accommodate.

Read the full mlr3tuning trajectory →

mlr3mbo vs mlr3tuning: editorial side-by-side

M
mlr3mbo
ANALYTICS
2.5

mlr3mbo picked its defaults from a benchmark study, not from taste

◆ Current state

mlr3mbo does model-based and Bayesian optimisation for mlr3. Its 1.0.0 release added a dictionary of pre-built acquisition-function optimisers and, more consequentially, replaced the default surrogate, acquisition function and optimiser settings with values derived from a large-scale benchmark study. The releases since are corrections to the acquisition-optimiser path exposed by that new default configuration.

◆ Where it's heading

The package has moved from a toolkit that expected users to assemble a Bayesian optimisation loop into one with a defensible default loop, and the recent fixes — warm-start sizing on multi-objective archives, silently discarded terminators, stale x_domain values — are the consequences of more people running the default path.

◆ Prediction

Expect continued hardening of the acquisition-optimiser classes rather than new acquisition functions.

M
mlr3tuning
ANALYTICS
2.5

mlr3tuning is rebuilding its async machinery under a stable public surface

◆ Current state

mlr3tuning provides hyperparameter optimization for the mlr3 ecosystem, and its recent history is dominated by the asynchronous tuning path: archive freezing, callback stages around queue evaluation, and version-locked compatibility with the rush backend. Releases pair a small feature with several fixes and an explicit compatibility line naming the mlr3 or rush version they track. The most recent release drops all workarounds for older rush versions, which suggests that dependency has stabilized enough to require rather than accommodate.

◆ Where it's heading

Two things are being tidied at once. The async archive is converging on a consistent data.table representation across batch and async variants, so results are shaped the same regardless of how tuning ran. Separately, the package is becoming a better ecosystem citizen — unioning tuner properties on load instead of overwriting them, removing its callbacks on unload, and raising informative errors from AutoTuner accessors on an untrained model. Both are the marks of a package used as a dependency more than as a destination.

◆ Prediction

With rush pinned to 1.2.0 and the compatibility shims gone, the next release is likely to expose more of the async path through callbacks rather than change the tuning interface.

Alternatives to mlr3mbo and mlr3tuning

Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either mlr3mbo or mlr3tuning.

See all mlr3mbo alternatives → · See all mlr3tuning alternatives →

Recent activity from mlr3mbo and mlr3tuning

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 18d agomlr3tuningmlr3tuning 1.6.1 stops clobbering other packages' tuner properties
  2. 23d agomlr3mboAcquisition optimiser fixes for warm starts and archives
  3. 3mo agomlr3mboDictionary lookup and restart-limit fixes
  4. 4mo agomlr3mborush 1.0.0 compatibility and Surrogate$check()
  5. 4mo agomlr3tuningmlr3tuning 1.6.0 aligns archive column order across tuning classes
  6. 5mo agomlr3mbomlr3mbo 1.0.0 ships benchmark-derived default settings
  7. 8mo agomlr3tuningmlr3tuning 1.5.1 tracks xgboost 3.1.2.1
  8. 8mo agomlr3tuningmlr3tuning 1.5.0 adds queue evaluation stages to async callbacks
  9. 10mo agomlr3mbomlr3learners 0.13.0 compatibility
  10. 11mo agomlr3mboMaintainer change and mlr3pipelines 0.9.0 upkeep
  11. 1y agomlr3tuningmlr3tuning 1.4.0 unifies logging under a base mlr3 logger
  12. 1y agomlr3tuningmlr3tuning 1.3.0 adds a frozen async archive and leaner worker storage

Frequently asked questions

What is the difference between mlr3mbo and mlr3tuning?

Both compete on the same themes — mlr3, hyperparameter-tuning — within Analytics. mlr3mbo and mlr3tuning are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is mlr3mbo better than mlr3tuning?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mlr3mbo and mlr3tuning are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to mlr3mbo?

Top mlr3mbo alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3mbo alternatives" section above for the current picks, or visit /alternatives/mlr3mbo for the full list with editorial commentary on each.

What are the best alternatives to mlr3tuning?

Top mlr3tuning alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3tuning alternatives" section above for the current picks, or visit /alternatives/mlr3tuning for the full list with editorial commentary on each.