← Back to home
Comparison · Infra & APIs

discretetests vs Dragonfly

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

discretetests vs Dragonfly: at a glance

FeaturediscretetestsDragonfly
SectorInfra & APIsInfra & APIs
Velocity score0.05.0
Sparks · 30d00
Top themesstatistical-testing, exact-tests, nonparametric, r-packageredis-compatible, tiered-storage, upstream-parity, cluster-correctness
Last editorial update2h ago11h ago
WebsiteVisit →Visit →

What is discretetests?

Four years of releases land in four minutes as the changelog gets backfilled to GitHub

DiscreteTests computes exact p-values and their full support for discrete statistical tests, returning results as a class that carries the observations, the test statistic and the null distribution. All four visible releases were tagged within four minutes of each other on a single day in May 2026, in reverse order — 0.4.1 carries the earliest timestamp and 0.4.0 the latest — so this is a historical changelog being pushed to GitHub at once, not four days of work.

Read the full discretetests trajectory →

What is Dragonfly?

Dragonfly spends its releases on correctness in the parts of Redis compatibility nobody tests.

The visible window is almost entirely correctness and internals work on the 1.39/1.40 lines. The newest release consolidates two tiering knobs into a single tiered_max_pending_bytes and exports it to metrics. Behind it sit a memory-accounting backport, a cluster fix that journals FLUSHSLOTS from inside the flush transaction, and a HyperLogLog resync with valkey upstream that pulled in a CVE fix and exposed three Dragonfly-local bugs.

Read the full Dragonfly trajectory →

discretetests vs Dragonfly: editorial side-by-side

D
discretetests
INFRA · APIS
0.0

Four years of releases land in four minutes as the changelog gets backfilled to GitHub

◆ Current state

DiscreteTests computes exact p-values and their full support for discrete statistical tests, returning results as a class that carries the observations, the test statistic and the null distribution. All four visible releases were tagged within four minutes of each other on a single day in May 2026, in reverse order — 0.4.1 carries the earliest timestamp and 0.4.0 the latest — so this is a historical changelog being pushed to GitHub at once, not four days of work.

◆ Where it's heading

Read by version rather than by timestamp, the package grew from binomial, Fisher, McNemar and Poisson tests into rank-based and resampling territory: Wilcoxon signed rank and rank sum, Mann-Whitney U, a conditional homogeneity test, then sign tests and a general permutation test with several built-in statistics. Alongside that the result class was extended to hold ragged observation lists and computational detail, the print output was rewritten on cli, and the old dot-separated function names were made defunct.

◆ Prediction

The permutation test with pluggable statistics is the most open-ended addition here, and adding further built-in statistics to it is the cheapest way to extend the package from where it now stands.

D
Dragonfly
INFRA · APIS
5.0

Dragonfly spends its releases on correctness in the parts of Redis compatibility nobody tests.

◆ Current state

The visible window is almost entirely correctness and internals work on the 1.39/1.40 lines. The newest release consolidates two tiering knobs into a single tiered_max_pending_bytes and exports it to metrics. Behind it sit a memory-accounting backport, a cluster fix that journals FLUSHSLOTS from inside the flush transaction, and a HyperLogLog resync with valkey upstream that pulled in a CVE fix and exposed three Dragonfly-local bugs.

◆ Where it's heading

Two threads run through this window. One is upstream parity — the hyperloglog sync explicitly re-forks from valkey and keeps upstream formatting so future syncs stay cheap, which is a maintenance-cost decision as much as a correctness one. The other is the RESP IO loop v2 migration, visible in a pub/sub ordering fix gated on the v1 loop and in tests being skipped on the v1 leg of the regression matrix. Dragonfly is hardening a drop-in Redis replacement in the places where drop-in claims usually break: cluster operations, pub/sub ordering under pipelining, and memory accounting.

◆ Prediction

Expect continued RESP IO loop v2 work and more upstream syncs on forked Redis internals. The tiering flag consolidation plus its metrics export suggests tiered storage tuning is the next area to get operator-facing surface.

Alternatives to discretetests and Dragonfly

Other Infra & APIs 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 discretetests or Dragonfly.

See all discretetests alternatives → · See all Dragonfly alternatives →

Recent activity from discretetests and Dragonfly

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 3d agoDragonflyTiering pending-bytes limit unified and exported to metrics
  2. 5d agoDragonflyBackported memory-accounting fix; FLUSHSLOTS journaled in-transaction
  3. 18d agoDragonflyi1.39.11: chore(hll): sync hyperloglog.c with valkey upstream (#7961)
  4. 24d agoDragonflyFix mutable cross-thread access on shared reply builder
  5. 26d agoDragonflyi1.39.9: fix(facade): preserve pub/sub order on unsubscribe (v1 IO loop) (#7909)
  6. 1mo agoDragonflyi1.39.6: test: skip V2-only pause tests under V1 (#7822)
  7. 2mo agodiscretetestsSign tests and a pluggable permutation test
  8. 2mo agodiscretetestsInput observation names carried through results
  9. 2mo agodiscretetestsWilcoxon, Mann-Whitney and homogeneity tests join the package
  10. 2mo agodiscretetestsmacOS compilation fix

Frequently asked questions

What is the difference between discretetests and Dragonfly?

They serve adjacent needs but don't currently overlap on shipped themes. Dragonfly 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 discretetests better than Dragonfly?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Dragonfly 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to discretetests?

Top discretetests alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "discretetests alternatives" section above for the current picks, or visit /alternatives/discretetests for the full list with editorial commentary on each.

What are the best alternatives to Dragonfly?

Top Dragonfly alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dragonfly alternatives" section above for the current picks, or visit /alternatives/dragonfly for the full list with editorial commentary on each.