tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of performance and Grafana Mimir — release velocity, themes, recent moves, and the top alternatives to consider.
performance keeps adding ways to check a model you have already fitted.
performance is at 0.17.1, which added check_priors() for prior predictive checks on Bayesian models and gave check_overdispersion(), check_model() and check_predictions() arguments to control residual type and plot range. The releases before it are a similar mix: a -2LL criterion column in test_likelihoodratio(), Bayesian predictive checks routed through modelbased, and in 0.16.0 a set of breaking renames including RMSA to the correct RMSR.
Mimir's feed is mostly Helm automation; the real work is inside the query engine.
The apparent cadence is misleading — five of the last seven entries are bot-generated weekly Helm chart releases carrying no functional change. The substantive item is the 3.2 release candidate, which collects 693 PRs from 61 authors and concentrates on Mimir Query Engine optimizations, PromQL function coverage, and native histogram handling.
performance is at 0.17.1, which added check_priors() for prior predictive checks on Bayesian models and gave check_overdispersion(), check_model() and check_predictions() arguments to control residual type and plot range. The releases before it are a similar mix: a -2LL criterion column in test_likelihoodratio(), Bayesian predictive checks routed through modelbased, and in 0.16.0 a set of breaking renames including RMSA to the correct RMSR.
Two consistent habits. Diagnostics keep gaining arguments to narrow what is examined — ppc_range, x_limits, maximum_dots, show_ci — which reads as a package being used on models large and awkward enough that the defaults stopped working. And simulated residuals via DHARMa keep displacing standard ones as the basis for the checks themselves.
With check_priors() newly added and Bayesian predictive checks now routed through modelbased, the next release most likely extends the Bayesian diagnostic set rather than reworking the frequentist checks.
The apparent cadence is misleading — five of the last seven entries are bot-generated weekly Helm chart releases carrying no functional change. The substantive item is the 3.2 release candidate, which collects 693 PRs from 61 authors and concentrates on Mimir Query Engine optimizations, PromQL function coverage, and native histogram handling.
MQE is where the engineering is going: added support for histogram_quantiles, a native histogram trim operation, and a rename of the experimental duration-arithmetic helpers to min_of and max_of. The chart pipeline runs on its own weekly schedule and says nothing about product direction, so read this feed by ignoring roughly two-thirds of it.
With 3.2.0-rc.0 out, a 3.2.0 general release is the near-certain next step, followed by a mimir-distributed chart release once the weekly train picks up the new version.
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 performance or Grafana Mimir.
tidyr replaced separate() with a family that says what it does.
modeltime built conformal intervals in, then went quiet on features.
CmdStanPy is clearing deprecations ahead of a 2.0 it keeps announcing.
DoWhy adds one estimation method a year and keeps its identification edge.
OpenHouse is hardening the seams where table policies and jobs quietly fail.
silx 3.0 moved its default Qt binding to PySide6 — a migration for everyone embedding it.
See all performance alternatives → · See all Grafana Mimir alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Grafana Mimir is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Grafana Mimir is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top performance alternatives in Analytics are ranked by recent ship velocity. Browse the "performance alternatives" section above for the current picks, or visit /alternatives/easystats-performance for the full list with editorial commentary on each.
Top Grafana Mimir alternatives in Analytics are ranked by recent ship velocity. Browse the "Grafana Mimir alternatives" section above for the current picks, or visit /alternatives/grafana-mimir for the full list with editorial commentary on each.