← Back to home
Comparison · Analytics

dfms vs TimescaleDB

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

dfms vs TimescaleDB: at a glance

FeaturedfmsTimescaleDB
SectorAnalyticsAnalytics
Velocity score0.05.0
Sparks · 30d00
Top themesnowcasting, state-space-models, econometrics, ropenscitime-series, postgresql, columnstore, query-optimization
Last editorial update4d ago1d ago
WebsiteVisit →Visit →

What is dfms?

Peer-reviewed, feature-complete, and now able to hand its models to other forecasting engines.

dfms estimates dynamic factor models in R, the workhorse for nowcasting economic activity from ragged, mixed-frequency data. The package worked through the Banbura and Modugno (2014) specification in stages — quarterly variables in 0.3.0, AR(1) idiosyncratic errors combined with mixed frequency in 0.4.0 — then declared 1.0.0 feature-complete on completing rOpenSci peer review, adding news decomposition to attribute forecast revisions to specific data releases. Version 1.0.1 adds convert(), which exports fitted models to dlm or KFAS state-space objects.

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

dfms vs TimescaleDB: editorial side-by-side

D
dfms
ANALYTICS
0.0

Peer-reviewed, feature-complete, and now able to hand its models to other forecasting engines.

◆ Current state

dfms estimates dynamic factor models in R, the workhorse for nowcasting economic activity from ragged, mixed-frequency data. The package worked through the Banbura and Modugno (2014) specification in stages — quarterly variables in 0.3.0, AR(1) idiosyncratic errors combined with mixed frequency in 0.4.0 — then declared 1.0.0 feature-complete on completing rOpenSci peer review, adding news decomposition to attribute forecast revisions to specific data releases. Version 1.0.1 adds convert(), which exports fitted models to dlm or KFAS state-space objects.

◆ Where it's heading

The package has finished the implementation programme it set out in its 2023 vignette and is now working on the edges: interoperability with other state-space packages rather than more estimation methods of its own. The convert() function is the clearest signal — instead of implementing smoothing and prediction intervals natively, it hands the model to packages that already have them. The rOpenSci move also puts it on a review-backed, documented footing that research users can cite.

◆ Prediction

Expect continued interoperability and diagnostic work rather than new estimators, since the maintainer has explicitly scoped the package as complete. Bug fixes against RcppArmadillo releases will likely remain the other recurring driver.

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

See all dfms alternatives → · See all TimescaleDB alternatives →

Recent activity from dfms 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 agodfmsconvert() exports models to dlm and KFAS state-space objects
  8. 6mo agodfms1.0: rOpenSci review passed, news decomposition added
  9. 7mo agodfmsMixed-frequency estimation gains AR(1) idiosyncratic errors
  10. 9mo agodfmsC++ compatibility with RcppArmadillo 15.0.2
  11. 1y agodfmsFixes estimation with a single quarterly variable
  12. 1y agodfmsAdds mixed-frequency estimation via quarterly.vars

Frequently asked questions

What is the difference between dfms 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 dfms 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 dfms?

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