HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
rendro
sediment-benchmark
Python2026–2026
rendro / sediment-benchmark

sediment-benchmark

Benchmark suite for memory systems (Sediment, ChromaDB, Mem0, Letta)

2Distinct people
2Mentions
0Explicit recommenders
1GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Benchmark suite for memory systems (Sediment, ChromaDB, Mem0, Letta)

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:27:27 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day2 dated mentions

Observed mentions: 2026-02-08 14:41:07 UTC to 2026-02-23 06:05:17 UTC.

012026-02-08 00:00:00 UTC to 2026-02-09 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 82026-02-09 00:00:00 UTC to 2026-02-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-10 00:00:00 UTC to 2026-02-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-11 00:00:00 UTC to 2026-02-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-12 00:00:00 UTC to 2026-02-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-13 00:00:00 UTC to 2026-02-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-14 00:00:00 UTC to 2026-02-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-15 00:00:00 UTC to 2026-02-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 152026-02-16 00:00:00 UTC to 2026-02-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-17 00:00:00 UTC to 2026-02-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-18 00:00:00 UTC to 2026-02-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-19 00:00:00 UTC to 2026-02-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-20 00:00:00 UTC to 2026-02-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-21 00:00:00 UTC to 2026-02-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-22 00:00:00 UTC to 2026-02-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-23 00:00:00 UTC to 2026-02-24 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 23

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 82026-02-08 00:00:00 UTC2026-02-09 00:00:00 UTC110
Feb 92026-02-09 00:00:00 UTC2026-02-10 00:00:00 UTC000
Feb 102026-02-10 00:00:00 UTC2026-02-11 00:00:00 UTC000
Feb 112026-02-11 00:00:00 UTC2026-02-12 00:00:00 UTC000
Feb 122026-02-12 00:00:00 UTC2026-02-13 00:00:00 UTC000
Feb 132026-02-13 00:00:00 UTC2026-02-14 00:00:00 UTC000
Feb 142026-02-14 00:00:00 UTC2026-02-15 00:00:00 UTC000
Feb 152026-02-15 00:00:00 UTC2026-02-16 00:00:00 UTC000
Feb 162026-02-16 00:00:00 UTC2026-02-17 00:00:00 UTC000
Feb 172026-02-17 00:00:00 UTC2026-02-18 00:00:00 UTC000
Feb 182026-02-18 00:00:00 UTC2026-02-19 00:00:00 UTC000
Feb 192026-02-19 00:00:00 UTC2026-02-20 00:00:00 UTC000
Feb 202026-02-20 00:00:00 UTC2026-02-21 00:00:00 UTC000
Feb 212026-02-21 00:00:00 UTC2026-02-22 00:00:00 UTC000
Feb 222026-02-22 00:00:00 UTC2026-02-23 00:00:00 UTC000
Feb 232026-02-23 00:00:00 UTC2026-02-24 00:00:00 UTC101

What Hacker News says

1 sources
Though the README is probably enough context, would there be value in an agent skill for this? https://agentskills.io/what-are-skills SKILL.md format: https://agentskills.io/specification#skill-md-format The skill creator skill SKILL.md: https://github.com/anthropics/skills/blob/main/skills/skill-... . SWE bench involves solving GitHub issues. Which of the SWE bench agents read from or write to GitHub issues? . There could be a local cache of remote issues, and/or an overlayfs-like write cache From https://github.com/GothenburgBitFactory/bugwarrior : > bugwarrior - Pull tickets from github, bitbucket, bugzilla, jira, trac, and others into taskwarrior https://github.com/bergercookie/syncall : > Bi-directional synchronization between services such as Taskwarrior, Google Calendar, Notion, Asana, and more . ditz is on the filesystem ditz: h
Read the rest
ttps://github.com/jashmenn/ditz : > Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar git-ditz: https://github.com/ihrke/git-ditz . sqlite-utils does SQLite FTS full text search config. There are additional tables for FTS indexes. sqlite-utils: https://github.com/simonw/sqlite-utils sqlite-utils > Configuring full-text search: https://sqlite-utils.datasette.io/en/stable/cli.html#configu... : sqlite-utils enable-fts mydb.db documents title summary # after subsequent writes sqlite-utils populate-fts mydb.db documents title summary # rebuild the FTS indexes sqlite-utils rebuild-fts mydb.db documents . One of these mentions sensitivity analysis and basically cache poisoning; From "I built a memory system for Claude that solves the context loss issue" https://news.ycombinator.com/item?id=45546276 : - buildautomata_memory_mcp: https://github.com/brucepro/buildautomata_memory_mcp Notes from "Show HN: Recall: Give Claude memory with Redis-backed persistent context" a few days ago: https://news.ycombinator.com/context?id=45517613 : - recall: https://github.com/joseairosa/recall sediment: https://github.com/rendro/sediment : > Semantic memory for AI agents. Local-first, MCP-native sediment-benchmark: https://github.com/rendro/sediment-benchmark : > Benchmark suite for memory systems (Sediment, ChromaDB, Mem0, Letta)
In Show HN: Saga – A Jira-like project tracker MCP server for AI agents (SQLite)

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.