Skip to content

seamusabshere/lock_and_cache

View on GitHub ↗Related repositories →

Most caching libraries don't do locking, meaning that >1 process can be calculating a cached value at the same time. Since you presumably cache things because they cost CPU, database reads, or money, doesn't it make sense to lock while caching?

active 2023-12-14 → 2024-09-12 (UTC)

Complete coverage28,372 / 28,372 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-11-09 (UTC)
Events
4
Pushes
0
Pull requests
0
Issues
1
Stars
0
Forks
1

Activity over time

Daily event counts in the loaded window

Line chart, 274 days from 2023-12-14 to 2024-09-12. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 1 total, peak 1 in a day. Comments: 2 total, peak 1 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
1c72001
klacointe1001

Recent activity

Latest issues, pull requests and releases

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.