silx
silx settles into maintenance a release after its PySide6 migration
Comparison · Analytics
collapse vs TimescaleDB
A side-by-side editorial comparison of collapse and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
collapse vs TimescaleDB: at a glance
What is collapse?
collapse got a JSS paper and a 7x fmean speedup in the same release.
collapse provides fast grouped statistical computing and data transformation for R, built on a C backend with its own grouping, hashing and aggregation primitives. The 2.1.x line is a maintenance and optimization series: SIMD multiple-accumulator work delivering roughly 2x on fsum() and 7x on fmean() for systems without OpenMP, a custom internal unlist() with better attribute preservation, and a steady stream of correctness fixes in collap(), pivot() and roworderv().
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.
collapse vs TimescaleDB: editorial side-by-side
collapse
0.0ANALYTICS
collapse got a JSS paper and a 7x fmean speedup in the same release.
◆ Current state
collapse provides fast grouped statistical computing and data transformation for R, built on a C backend with its own grouping, hashing and aggregation primitives. The 2.1.x line is a maintenance and optimization series: SIMD multiple-accumulator work delivering roughly 2x on fsum() and 7x on fmean() for systems without OpenMP, a custom internal unlist() with better attribute preservation, and a steady stream of correctness fixes in collap(), pivot() and roworderv().
◆ Where it's heading
The package is consolidating institutionally as much as technically. The repository moved to the fastverse organization with multiple people granted access, the Journal of Statistical Software paper landed as the primary citation, and documentation now includes an AI-generated interactive layer. Technically the focus is the hashing and grouping core — the decision to treat -0 and 0 as equal across funique(), group(), fmatch(), fmode() and their derivatives was made in sync with an equivalent change in Rcpp, and accepted a measured 3% cost to get it. The last release with breaking changes sits outside this six-entry window.
◆ Prediction
Expect further targeted performance work on the grouped statistical functions and continued small correctness fixes; the governance move to fastverse suggests contribution volume rather than direction is what the maintainer is managing.
TimescaleDB
5.0ANALYTICS
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 collapse 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 collapse or TimescaleDB.
Plotly
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread
aniread stops asking you to know which tracker wrote the file
Rho
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
OpenCTI
OpenCTI spends a release unblocking queues and hardening upserts
See all collapse alternatives → · See all TimescaleDB alternatives →
Recent activity from collapse and TimescaleDB
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoTimescaleDB2.29.2: SkipScan and sparse-index correctness fixes
- 15d agoTimescaleDB2.29.1: security fixes plus compression bugfixes
- 19d agoTimescaleDB2.29.0: chunk exclusion speeds up UPDATE and DELETE
- 1mo agoTimescaleDB2.28.3: columnar pipeline correctness fixes
- 1mo agoTimescaleDB2.28.2: upgrade-path fixes for 2.28.1
- 1mo agoTimescaleDB2.28.1: compressed-table crash and constraint fixes
- 3mo agocollapseSIMD accumulators give fmean a 7x speedup without OpenMP
- 7mo agocollapseNegative zero now hashes equal to zero across the package
- 9mo agocollapsecollap() no longer double-aggregates external weights
- 10mo agocollapseCustom unlist() preserves attributes
- 1y agocollapseAssorted bug fixes
- 1y agocollapsena_insert gains by-reference mode; gsplit and pivot speed up
Frequently asked questions
What is the difference between collapse 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 collapse 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 collapse?
Top collapse alternatives in Analytics are ranked by recent ship velocity. Browse the "collapse alternatives" section above for the current picks, or visit /alternatives/collapse-r 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.