silx
silx settles into maintenance a release after its PySide6 migration
Comparison · Analytics
cholera vs TimescaleDB
A side-by-side editorial comparison of cholera and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
cholera vs TimescaleDB: at a glance
What is cholera?
John Snow's 1854 cholera map is being rebuilt on real geographic coordinates.
cholera packages the Broad Street cholera outbreak data with tools to recompute pump neighbourhoods by Voronoi and walking distance. The last two releases carried the dataset from Snow's original plate coordinates onto georeferenced longitude and latitude, exposed through a latlong = TRUE argument on most functions. Function naming and plotting APIs are being tidied at the same pace.
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.
cholera vs TimescaleDB: editorial side-by-side
cholera
0.0ANALYTICS
John Snow's 1854 cholera map is being rebuilt on real geographic coordinates.
◆ Current state
cholera packages the Broad Street cholera outbreak data with tools to recompute pump neighbourhoods by Voronoi and walking distance. The last two releases carried the dataset from Snow's original plate coordinates onto georeferenced longitude and latitude, exposed through a latlong = TRUE argument on most functions. Function naming and plotting APIs are being tidied at the same pace.
◆ Where it's heading
The direction is clear and sustained: convert a historical, self-referential coordinate system into one that interoperates with modern GIS. Each release extends latlong coverage to more datasets — pumps, roads, landmarks, and now the plague pit and map frame — while archiving the older prototypes. Parallelisation and the walking-distance solver were reworked along the way to keep the heavier computations usable.
◆ Prediction
Remaining non-georeferenced pieces and the archived latlong prototypes are the obvious next targets, alongside continued consolidation of the add*()/plot*() function pairs.
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 cholera 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 cholera 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 cholera alternatives → · See all TimescaleDB alternatives →
Recent activity from cholera 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
- 1y agocholeraGeoreferences the plague pit and road segments
- 1y agocholeraLongitude and latitude support across nearly all data and functions ⚡
- 3y agocholeraFirst longitude/latitude prototypes and new distance functions
- 4y agocholeraAdds streetNames(); fixes Delaunay and pump-token plotting
- 5y agocholeraIsochrone helpers, weather data and Voronoi location options
- 6y agocholeraParallel computation support on Windows
Frequently asked questions
What is the difference between cholera 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 cholera 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 cholera?
Top cholera alternatives in Analytics are ranked by recent ship velocity. Browse the "cholera alternatives" section above for the current picks, or visit /alternatives/cholera-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.