silx
silx settles into maintenance a release after its PySide6 migration
Comparison · Analytics
cheapr vs TimescaleDB
A side-by-side editorial comparison of cheapr and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
cheapr vs TimescaleDB: at a glance
What is cheapr?
cheapr turned multi-threaded, and its next stop is a C++20 public API.
cheapr supplies lower-overhead replacements for base R's data manipulation primitives — subsetting, recycling, concatenation, attribute handling, data frame construction. Through 2025 it grew function by function: sset_df/sset_row/sset_col, list_as_df, cheapr_c, counts, str_coalesce, df_modify. The 1.5.0 release in April 2026 changed the nature of the package, adding parallelised math functions, user-settable thread counts, multi-threaded vector initialisers, and a SIMD-parallelised if_else_, with threading on by default at two threads.
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.
cheapr vs TimescaleDB: editorial side-by-side
cheapr
0.0ANALYTICS
cheapr turned multi-threaded, and its next stop is a C++20 public API.
◆ Current state
cheapr supplies lower-overhead replacements for base R's data manipulation primitives — subsetting, recycling, concatenation, attribute handling, data frame construction. Through 2025 it grew function by function: sset_df/sset_row/sset_col, list_as_df, cheapr_c, counts, str_coalesce, df_modify. The 1.5.0 release in April 2026 changed the nature of the package, adding parallelised math functions, user-settable thread counts, multi-threaded vector initialisers, and a SIMD-parallelised if_else_, with threading on by default at two threads.
◆ Where it's heading
Two arcs run at once. The visible one is parallelism: what began as single-threaded C shortcuts is becoming a threaded compute layer, and the notes state the C/C++ API is mid-rewrite with a stable form promised at 2.0.0 behind a C++20 requirement. The quieter one is R C API compliance — 1.5.1 removed R_MissingArg, R_UnboundValue, Rf_findVar and Rf_findVarinFrame, the non-API entry points being closed off upstream. The 1.5.x patches since are narrow crash fixes, which reads as consolidation before the 2.0.0 break.
◆ Prediction
Expect 2.0.0 to land the stable C/C++ API behind a C++20 toolchain floor, with more of the existing function surface threaded in the interim. The package has announced both moves in its own release notes.
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 cheapr 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 cheapr 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 cheapr alternatives → · See all TimescaleDB alternatives →
Recent activity from cheapr 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 agocheaprrep_len_ crash on shrinking lengths fixed
- 1mo agoTimescaleDB2.28.2: upgrade-path fixes for 2.28.1
- 1mo agoTimescaleDB2.28.1: compressed-table crash and constraint fixes
- 4mo agocheaprNon-API R internals removed
- 4mo agocheaprParallelised math, thread control, and a C API rewrite ⚡
- 1y agocheaprSubsetting speedups; sset_col negative-index crash fixed
- 1y agocheaprdf_modify added; attribute helpers renamed for intent
- 1y agocheaprcounts and str_coalesce added; reconstruct renamed to rebuild
Frequently asked questions
What is the difference between cheapr 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 cheapr 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 cheapr?
Top cheapr alternatives in Analytics are ranked by recent ship velocity. Browse the "cheapr alternatives" section above for the current picks, or visit /alternatives/cheapr-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.