active 2025-02-20 → 2025-06-06 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 107 days from 2025-02-20 to 2025-06-06. Pushes: 184 total, peak 19 in a day. Pull requests: 18 total, peak 2 in a day. Issues: 11 total, peak 9 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
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| namita-ach | 69 | 68 | 1 | 0 |
| Vishal-Srinivasa | 43 | 43 | 0 | 0 |
| vanillacoke77 | 38 | 38 | 0 | 0 |
| ajayshanbhog | 23 | 7 | 16 | 0 |
| varshinigopal04 | 17 | 17 | 0 | 0 |
| vrenj | 11 | 0 | 0 | 0 |
| m-anshu | 10 | 9 | 1 | 0 |
Recent activity
Latest issues, pull requests and releases
- Pull request#21ajayshanbhog2025-05-30 10:12
- Pull request#21ajayshanbhog2025-05-30 10:12
- Pull request#20ajayshanbhog2025-04-18 10:24
- Pull request#20ajayshanbhog2025-04-18 10:23
- Pull request#19ajayshanbhog2025-04-07 06:42
- Pull request#19ajayshanbhog2025-04-07 06:41
- Pull request#18ajayshanbhog2025-03-28 10:06
- Pull request#18ajayshanbhog2025-03-28 10:05
- Issue#17vrenj2025-03-28 09:44Could you print the distances as well? That will help to determine the accuracy with large datasets
- Issue#16vrenj2025-03-28 09:41Isn't faiss_index.add() needed here with the vector?
- Pull request#15ajayshanbhog2025-03-27 07:12
- Pull request#15ajayshanbhog2025-03-27 07:12
- Pull request#14ajayshanbhog2025-03-26 17:39
- Pull request#14ajayshanbhog2025-03-26 17:39
- Issue#12vrenj2025-03-21 06:24What about using indexing methods supported by Weaviate? (IVF or HNSW)
- Issue#11vrenj2025-03-21 06:23Where do you measure similarity score of the result?
- Issue#10vrenj2025-03-21 05:43You need to consider performance with different batch sizes
- Issue#9vrenj2025-03-21 05:41Update should not consider search latency
- Issue#8vrenj2025-03-21 05:40What about disctance similarity score for the result obtained?
- Issue#7vrenj2025-03-21 05:05It's 5-tuple, so you should take in to account transport layer ports as well.. src_port, dst_port
- Issue#6vrenj2025-03-21 04:58Why? This is going to cause more overhead and affect efficiency.
- Issue#5vrenj2025-03-21 04:52Why limit it to 1 worker? if you have multiple cores in system, programmatically find that and use that instead.
- Issue#4vrenj2025-03-21 04:41Did you chosse 128 for efficiency? WHat is the trade-off here?
- Pull request#3ajayshanbhog2025-03-14 09:48
- Pull request#3ajayshanbhog2025-03-14 09:48
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.