Building a Benchmark

MemoryBench ships with three datasets — LoCoMo, LongMemEval, and ConvoMem — but they won’t cover every product. If your agent has a workflow the built-in benchmarks don’t exercise (a specific domain, a scenario your users actually hit, a regression you want to guard against), you can add your own benchmark dataset and every provider — including Supermemory — runs against it the same way.

Choosing between the built-in datasets

Before building your own, check whether one of the existing datasets already covers what you need:

Benchmark	Best for	Primary challenge
LoCoMo	Personal assistants, support bots — anything with recurring sessions over days/weeks	Temporal context, cross-session recall
LongMemEval	RAG / document search, knowledge bases	Information density, precise retrieval, synthesis
ConvoMem	Dialogue systems, interview bots, meeting assistants	Reference resolution within a single conversation

You can also run all three to get a full picture of where a memory system is strong or weak — a system that’s great at LoCoMo but weak at LongMemEval is good at temporal recall but struggles with dense information retrieval, for example.

The Benchmark interface

Every dataset — built-in or custom — implements the same interface (src/types/benchmark.ts):

interface Benchmark {
  name: string
  load(config?: BenchmarkConfig): Promise<void>
  getQuestions(filter?: QuestionFilter): UnifiedQuestion[]
  getHaystackSessions(questionId: string): UnifiedSession[]
  getGroundTruth(questionId: string): string
  getQuestionTypes(): QuestionTypeRegistry
}

Sessions — the raw conversational data a provider ingests before being asked a question — are normalized to a single shape regardless of benchmark:

interface UnifiedSession {
  sessionId: string
  messages: Array<{ role: "user" | "assistant"; content: string }>
  metadata?: {
    date?: string           // ISO format
    formattedDate?: string  // human readable
    [key: string]: any
  }
}

Adding your own benchmark

Create src/benchmarks/mybenchmark/index.ts implementing the Benchmark interface above
load() parses your dataset (JSON, CSV, whatever you have) into UnifiedSessions and questions
getQuestions() returns your question set, each with a ground-truth answer and a question type
Register it in src/benchmarks/index.ts and add the name to BenchmarkName in src/types/benchmark.ts
Run it exactly like a built-in benchmark:

bun run src/index.ts run -p supermemory -b mybenchmark
bun run src/index.ts compare -p supermemory,mem0,zep -b mybenchmark

Question types are your own vocabulary — group questions however matters to your product (billing_history, escalation_context, preference_drift, etc.), and the final report breaks accuracy down per type so you can see exactly where a provider is strong or weak on your scenarios, not a generic academic one.

Full interface details and a working template: src/benchmarks/README.md in the repo.

Adding a Provider

Measuring Results

How accuracy, latency, and MemScore are computed.

Getting Started

Concepts

Using supermemory

Deployment

Other resources

Migration Guides

Choosing between the built-in datasets

The Benchmark interface

Adding your own benchmark

Next

Adding a Provider

Measuring Results

​Choosing between the built-in datasets

​The Benchmark interface

​Adding your own benchmark

​Next

Adding a Provider

Measuring Results

Choosing between the built-in datasets

The Benchmark interface

Adding your own benchmark

Next