logger
R's logging package handed to new maintainers and rebuilt from the inside out
Comparison · Infra & APIs
Dragonfly vs portfoliobacktest
A side-by-side editorial comparison of Dragonfly and portfoliobacktest — release velocity, themes, recent moves, and the top alternatives to consider.
Dragonfly vs portfoliobacktest: at a glance
| Feature | Dragonfly | portfoliobacktest |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | redis-compatible, tiered-storage, upstream-parity, cluster-correctness | quantitative-finance, backtesting, portfolio-optimization, r-package |
| Last editorial update | 11h ago | 2h ago |
| Website | Visit → | Visit → |
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.
What is portfoliobacktest?
Four dormant years end with a test fix, not a feature
portfolioBacktest runs portfolio strategies across multiple datasets and resampled windows, producing performance tables, leaderboards and charts. After a run of substantive releases through 2021 and early 2022 it went quiet for four years. The May 2026 release does one thing: fix unit tests against a breaking change in PerformanceAnalytics::Return.portfolio(), which now returns results for the full input series rather than only from the first weight date.
Dragonfly vs portfoliobacktest: editorial side-by-side
Dragonfly
5.0INFRA · APIS
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.
portfoliobacktest
0.0INFRA · APIS
Four dormant years end with a test fix, not a feature
◆ Current state
portfolioBacktest runs portfolio strategies across multiple datasets and resampled windows, producing performance tables, leaderboards and charts. After a run of substantive releases through 2021 and early 2022 it went quiet for four years. The May 2026 release does one thing: fix unit tests against a breaking change in PerformanceAnalytics::Return.portfolio(), which now returns results for the full input series rather than only from the first weight date.
◆ Where it's heading
The development work is behind it. The 2019 to 2022 releases built the substance — parallel execution, resampling that works beyond stock data and beyond daily bars, transaction-cost-aware designs through w_current, and a switch from compounded to uncompounded returns in the Sharpe and annualized return calculations. Since then the package has moved only when a dependency forced it, and even then only far enough to keep the tests green.
◆ Prediction
Nothing in the entries suggests planned work; the next release is most likely triggered by another dependency change, on the same four-year-gap pattern.
Alternatives to Dragonfly and portfoliobacktest
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 Dragonfly or portfoliobacktest.
discretetests
Four years of releases land in four minutes as the changelog gets backfilled to GitHub
medicalcoder
A comorbidity-coding package relicenses to BSD and grows past the American coding systems
Unleash
Three kill-switch explainers to one point release — Unleash's feed is content-led, not release-led.
Jackett
Jackett's daily release treadmill now spends commits undoing tracker removals it made days earlier.
Kinsta
Kinsta keeps moving MyKinsta's control panel into its API, month by month.
See all Dragonfly alternatives → · See all portfoliobacktest alternatives →
Recent activity from Dragonfly and portfoliobacktest
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3d agoDragonflyTiering pending-bytes limit unified and exported to metrics
- 5d agoDragonflyBackported memory-accounting fix; FLUSHSLOTS journaled in-transaction
- 18d agoDragonflyi1.39.11: chore(hll): sync hyperloglog.c with valkey upstream (#7961)
- 24d agoDragonflyFix mutable cross-thread access on shared reply builder
- 26d agoDragonflyi1.39.9: fix(facade): preserve pub/sub order on unsubscribe (v1 IO loop) (#7909)
- 1mo agoDragonflyi1.39.6: test: skip V2-only pause tests under V1 (#7822)
- 3mo agoportfoliobacktestTests fixed for a PerformanceAnalytics breaking change
- 4y agoportfoliobacktestSharpe ratio charts and reworked weight outputs
- 4y agoportfoliobacktestUncompounded return metrics and transaction-cost-aware designs
- 5y agoportfoliobacktestResampling generalised beyond daily stock data
- 6y agoportfoliobacktestCRAN example fixes and vignette references
- 6y agoportfoliobacktestDrawdown, cumulative return and stacked bar charts
Frequently asked questions
What is the difference between Dragonfly and portfoliobacktest?
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 Dragonfly better than portfoliobacktest?
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 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.
What are the best alternatives to portfoliobacktest?
Top portfoliobacktest alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "portfoliobacktest alternatives" section above for the current picks, or visit /alternatives/portfoliobacktest for the full list with editorial commentary on each.