← Back to home
Comparison · Analytics

DHARMa vs TimescaleDB

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

DHARMa vs TimescaleDB: at a glance

FeatureDHARMaTimescaleDB
SectorAnalyticsAnalytics
Velocity score0.05.0
Sparks · 30d00
Top themesresidual-diagnostics, glmm, breaking-change, bayesiantime-series, postgresql, columnstore, query-optimization
Last editorial update2d ago1d ago
WebsiteVisit →Visit →

What is DHARMa?

DHARMa changed how GLMM residuals are simulated, so the same code now returns different numbers.

DHARMa generates scaled quantile residuals for fitted GLMMs and runs the dispersion, uniformity, and autocorrelation tests built on them. Version 0.5.0 changed the default simulation for hierarchical models from the model's own default, mostly unconditional, to conditional simulation, and states plainly that residuals will differ from those computed by older versions. The same release added brms to the supported model set and reworked how predictors are passed to plotting and testing functions.

Read the full DHARMa trajectory →

What is TimescaleDB?

TimescaleDB is paying down correctness debt in its columnstore query paths.

The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.

Read the full TimescaleDB trajectory →

DHARMa vs TimescaleDB: editorial side-by-side

D
DHARMa
ANALYTICS
0.0

DHARMa changed how GLMM residuals are simulated, so the same code now returns different numbers.

◆ Current state

DHARMa generates scaled quantile residuals for fitted GLMMs and runs the dispersion, uniformity, and autocorrelation tests built on them. Version 0.5.0 changed the default simulation for hierarchical models from the model's own default, mostly unconditional, to conditional simulation, and states plainly that residuals will differ from those computed by older versions. The same release added brms to the supported model set and reworked how predictors are passed to plotting and testing functions.

◆ Where it's heading

The package has spent several releases widening which model backends it can diagnose, from glmmTMB through mgcv, phylolm and now brms, while methodological work has gone into handling correlated residuals via the rotation argument. Version 0.5.0 shifts from adding coverage to changing defaults for statistical power. The formula interface arriving across plotResiduals, testCategorical, testQuantiles and the autocorrelation tests suggests the API is being unified rather than extended function by function.

◆ Prediction

The next releases will likely broaden brms support past the simple-model restriction and continue converting remaining functions to the formula interface.

T
TimescaleDB
ANALYTICS
5.0

TimescaleDB is paying down correctness debt in its columnstore query paths.

◆ Current state

The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.

◆ Where it's heading

The feature work of 2.27 and 2.28 - vectorized filter evaluation, first/last derived straight from columnstore batch metadata, sparse indexes, SkipScan on compressed data - has been followed by a steady stream of fixes to those same code paths. 2.29.2 alone repairs SkipScan dropping uncompressed rows, sparse-index pushdown returning wrong results for IS NULL, and gapfill over window aggregates. That is the normal cost of pushing query optimizations into a compressed columnar store, and the project is working through it release by release rather than pausing.

◆ Prediction

With three consecutive patch releases on the 2.29 line and no new highlighted features since 2.29.0, the next minor is likely to resume the columnstore performance work - though the density of wrong-results fixes suggests more patches first.

Alternatives to DHARMa and TimescaleDB

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 DHARMa or TimescaleDB.

See all DHARMa alternatives → · See all TimescaleDB alternatives →

Recent activity from DHARMa and TimescaleDB

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

  1. 1d agoTimescaleDB2.29.2: SkipScan and sparse-index correctness fixes
  2. 15d agoTimescaleDB2.29.1: security fixes plus compression bugfixes
  3. 19d agoTimescaleDB2.29.0: chunk exclusion speeds up UPDATE and DELETE
  4. 1mo agoTimescaleDB2.28.3: columnar pipeline correctness fixes
  5. 1mo agoTimescaleDB2.28.2: upgrade-path fixes for 2.28.1
  6. 1mo agoTimescaleDB2.28.1: compressed-table crash and constraint fixes
  7. 2mo agoDHARMaConditional simulation becomes the GLMM default, changing residuals
  8. 1y agoDHARMaDHARMa 0.4.7
  9. 3y agoDHARMaDHARMa 0.4.6
  10. 4y agoDHARMaDHARMa 0.4.5
  11. 4y agoDHARMaDHARMa 0.4.4
  12. 5y agoDHARMaDHARMa 0.4.3

Frequently asked questions

What is the difference between DHARMa and TimescaleDB?

They serve adjacent needs but don't currently overlap on shipped themes. TimescaleDB 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.

Is DHARMa better than TimescaleDB?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. TimescaleDB 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.

What are the best alternatives to DHARMa?

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

What are the best alternatives to TimescaleDB?

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