← Back to home
Comparison · Analytics

fabletools vs TimescaleDB

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

Shared themes:time-series

fabletools vs TimescaleDB: at a glance

FeaturefabletoolsTimescaleDB
SectorAnalyticsAnalytics
Velocity score0.05.0
Sparks · 30d00
Top themesforecasting, tidyverts, model-combination, reconciliationtime-series, postgresql, columnstore, query-optimization
Last editorial update4d ago1d ago
WebsiteVisit →Visit →

What is fabletools?

The tidyverts forecasting core rebuilt model combination on full residual covariance.

fabletools is the framework layer under fable and fpp3 — mables, fables, accuracy measures, reconciliation, and the model arithmetic that lets forecasters express ensembles as expressions. Version 0.8.0 reworked that arithmetic: combination now uses a joint N-way convolution accounting for the full residual covariance across components rather than composing pairwise, and every arithmetic operator collapses to a single model_combination with correctly implied weights, so nested expressions like ((m1 + m2)/2 + m3)/2 flatten automatically. In parallel, the package has been shedding graphics to {ggtime} on a deliberately slow deprecation clock.

Read the full fabletools 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 →

fabletools vs TimescaleDB: editorial side-by-side

F
fabletools
ANALYTICS
0.0

The tidyverts forecasting core rebuilt model combination on full residual covariance.

◆ Current state

fabletools is the framework layer under fable and fpp3 — mables, fables, accuracy measures, reconciliation, and the model arithmetic that lets forecasters express ensembles as expressions. Version 0.8.0 reworked that arithmetic: combination now uses a joint N-way convolution accounting for the full residual covariance across components rather than composing pairwise, and every arithmetic operator collapses to a single model_combination with correctly implied weights, so nested expressions like ((m1 + m2)/2 + m3)/2 flatten automatically. In parallel, the package has been shedding graphics to {ggtime} on a deliberately slow deprecation clock.

◆ Where it's heading

The framework is being narrowed and deepened at the same time. Narrowed, because plotting is moving out to a dedicated package over an announced two-year deprecation, leaving fabletools to modeling infrastructure. Deepened, because the recent statistical work targets correctness in places users could not easily inspect — combination weights, inverse-variance weighting computed on response rather than innovation residuals, reconciliation coherency matrices exposed via coherent_smat() and coherent_cmat(). Class hygiene follows the same instinct, with mdl_lst replacing lst_mdl and gaining augment(), glance(), and tidy() so global and reconciliation models report statistics like any other.

◆ Prediction

With combination and reconciliation infrastructure freshly reworked, the remaining announced work is the ggtime separation, so expect the graphics re-exports to keep degrading toward removal while modeling changes stay incremental.

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

See all fabletools alternatives → · See all TimescaleDB alternatives →

Recent activity from fabletools 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. 20d 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 agofabletoolsModel combination rebuilt on joint N-way convolution
  7. 1mo agoTimescaleDB2.28.1: compressed-table crash and constraint fixes
  8. 3mo agofabletoolsCoherency matrices exposed, mdl_lst gains tidier methods
  9. 6mo agofabletoolsGraphics methods now require fabletools to be attached
  10. 6mo agofabletoolsTime series graphics migrating out to ggtime
  11. 8mo agofabletoolsggplot2 4.0.0 compatibility patch
  12. 8mo agofabletoolsIRF() generic and multivariate bootstrap sample paths

Frequently asked questions

What is the difference between fabletools and TimescaleDB?

Both compete on the same themes — time-series — within Analytics. 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 fabletools 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 fabletools?

Top fabletools alternatives in Analytics are ranked by recent ship velocity. Browse the "fabletools alternatives" section above for the current picks, or visit /alternatives/fabletools 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.