← Back to home
Comparison · Infra & APIs

pkgcache vs rush

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

pkgcache vs rush: at a glance

Featurepkgcacherush
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themespackage-management, r-lib, repositories, authenticationmlr3, distributed-computing, redis, fault-tolerance
Last editorial update1h ago4h ago
WebsiteVisit →Visit →

What is pkgcache?

The metadata cache under pak now speaks to authenticated and corporate repositories.

pkgcache maintains the package metadata cache that pak and pkgdepends build on, so its releases are about knowing where packages live and what platform they were built for. Version 2.2.4 added support for authenticated repositories through repo_auth(), the first time the cache could reach private registries directly. The releases around it track a moving target: Posit Package Manager behaviour, R Universe binaries, macOS binary availability per R version, Bioconductor version mapping, and most recently comments in DESCRIPTION and PACKAGES files following a change in R-devel.

Read the full pkgcache trajectory →

What is rush?

Rush spent 2026 making distributed task ownership correct, starting with a breaking 1.0.

rush is the Redis-backed distributed computing backend behind mlr3's parallel tuning: workers pull tasks, push results and are tracked through heartbeats. Since 1.0.0 in March 2026 it has shipped five releases in four months, almost all correcting how tasks and workers are owned and identified under failure. The most recent lets each worker start in its own mirai call so it can spawn local daemons.

Read the full rush trajectory →

pkgcache vs rush: editorial side-by-side

P
pkgcache
INFRA · APIS
0.0

The metadata cache under pak now speaks to authenticated and corporate repositories.

◆ Current state

pkgcache maintains the package metadata cache that pak and pkgdepends build on, so its releases are about knowing where packages live and what platform they were built for. Version 2.2.4 added support for authenticated repositories through repo_auth(), the first time the cache could reach private registries directly. The releases around it track a moving target: Posit Package Manager behaviour, R Universe binaries, macOS binary availability per R version, Bioconductor version mapping, and most recently comments in DESCRIPTION and PACKAGES files following a change in R-devel.

◆ Where it's heading

The work has shifted from CRAN-shaped assumptions toward the mixed reality of how R packages are actually distributed now — PPM snapshots, R Universe, private and authenticated registries, Bioconductor, and per-platform binaries across several R versions. Resilience is a recurring theme too: 2.2.5 makes an unreachable Bioconductor a non-fatal condition rather than a failure. MRAN's retirement, handled in 2.2.0 by resolving its prefix to PPM, is a reminder of how much of this package's job is absorbing other people's infrastructure changes.

◆ Prediction

Expect continued tracking of R-devel metadata format changes and new binary platforms as R 4.6 lands, since both already appear in 2.2.5. Further work on authenticated repository handling is the plausible follow-on, given how recently that capability arrived.

R
rush
INFRA · APIS
2.5

Rush spent 2026 making distributed task ownership correct, starting with a breaking 1.0.

◆ Current state

rush is the Redis-backed distributed computing backend behind mlr3's parallel tuning: workers pull tasks, push results and are tracked through heartbeats. Since 1.0.0 in March 2026 it has shipped five releases in four months, almost all correcting how tasks and workers are owned and identified under failure. The most recent lets each worker start in its own mirai call so it can spawn local daemons.

◆ Where it's heading

The through-line is moving responsibility from the controller to the worker. 1.0.0 rewrote the task lifecycle and dropped the seed mechanism; 1.2.0 moved fail_tasks(), finish_tasks(), pop_task() and push_running_tasks() from Rush onto RushWorker so only the worker that ran a task can mark it done, and gave worker ids random suffixes so they cannot collide. 1.1.0 had already removed phantom failed tasks when a worker crashes between evaluations.

◆ Prediction

With ownership and identity settled, the remaining pressure points are heartbeat and lost-worker detection; expect the next releases to tighten failure recovery rather than add API surface.

Alternatives to pkgcache and rush

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 pkgcache or rush.

See all pkgcache alternatives → · See all rush alternatives →

Recent activity from pkgcache and rush

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

  1. 21d agorushWorkers start in their own mirai call so they can create local daemons
  2. 1mo agorushTask lifecycle moves onto the worker; worker ids can no longer collide
  3. 3mo agorushPhantom failed tasks and missed results fixed
  4. 4mo agopkgcacheParses comments in DESCRIPTION and PACKAGES files
  5. 4mo agorushSmaller Redis payloads and vector-valued task parameters
  6. 4mo agorushRush 1.0 rewrites the task lifecycle and drops the seed mechanism
  7. 9mo agorushwait_for_workers() can target a count or specific ids
  8. 1y agopkgcacherepo_auth() brings authenticated repositories to the cache
  9. 1y agopkgcacheStops using source URLs for archived PPM packages
  10. 2y agopkgcacheHandles macOS binaries for R 4.5 development builds
  11. 2y agopkgcacheImproves R to Bioconductor version matching
  12. 3y agopkgcacheMRAN prefix deprecated in favour of PPM; platform override added

Frequently asked questions

What is the difference between pkgcache and rush?

They serve adjacent needs but don't currently overlap on shipped themes. rush is currently shipping more aggressively (velocity 2.5 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 pkgcache better than rush?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rush is currently shipping more aggressively (velocity 2.5 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 pkgcache?

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

What are the best alternatives to rush?

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