Skip to content

striiike/Efficient-Pattern-Detection

View on GitHub ↗Related repositories →

active 2025-10-032025-10-08 (UTC)

Complete coverage26,591 / 26,591 hourly files (100%) · 2 absent upstream2023-08-152026-08-26 (UTC)
Events
35
Pushes
8
Pull requests
3
Issues
23
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 6 days from 2025-10-03 to 2025-10-08. Pushes: 8 total, peak 4 in a day. Pull requests: 3 total, peak 2 in a day. Issues: 23 total, peak 19 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

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

ContributorContributionsPushesPRsComments
Amirjjf23410
striiike11420

Recent activity

Latest issues, pull requests and releases

  • Issue#20striiike2025-10-08 13:32
    Recall should be calculated correctly
  • Pull request#24Amirjjf2025-10-07 20:56
  • Issue#22striiike2025-10-05 14:19
    better load shedding strategy based on the score
  • Issue#19Amirjjf2025-10-05 03:59
    (Advanced) Scalability study
  • Issue#18Amirjjf2025-10-05 03:59
    Latency-bound recall sweeps (10–90%)
  • Issue#17Amirjjf2025-10-05 03:59
    Baseline vs shedding runs
  • Issue#16Amirjjf2025-10-05 03:59
    Burst workload generator
  • Issue#15Amirjjf2025-10-05 03:59
    Shedding integrated in pipeline
  • Issue#11Amirjjf2025-10-05 03:59
    Instrumentation (latency/throughput/recall)
  • Issue#12Amirjjf2025-10-05 03:59
    Overload detection signal (+ detection latency)
  • Issue#13Amirjjf2025-10-05 03:59
    Utility/score function for shedding
  • Issue#14Amirjjf2025-10-05 03:59
    Shedding policy
  • Issue#10Amirjjf2025-10-05 03:59
    Emit complex events / projection
  • Issue#18Amirjjf2025-10-05 03:58
    Latency-bound recall sweeps (10–90%)
  • Issue#17Amirjjf2025-10-05 03:58
    Baseline vs shedding runs
  • Issue#16Amirjjf2025-10-05 03:58
    Burst workload generator
  • Issue#15Amirjjf2025-10-05 03:56
    Shedding integrated in pipeline
  • Issue#13Amirjjf2025-10-05 03:55
    Utility/score function for shedding
  • Issue#12Amirjjf2025-10-05 03:55
    Overload detection signal (+ detection latency)
  • Issue#10Amirjjf2025-10-05 03:54
    Emit complex events / projection
  • Issue#9Amirjjf2025-10-05 03:50
    condition 6 was wrong. no need for that
  • Issue#8striiike2025-10-04 10:55
    Simpliest load shedding strategy for recall rate calculation
  • Issue#7striiike2025-10-04 10:25
    calculation of recall rate
  • Pull request#6striiike2025-10-03 23:17
  • Pull request#6striiike2025-10-03 23:16

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.