Appendices
These are the topics in this section, each on its own page with a stable path you can bookmark or share.
What topics are covered in this section?
- Which mathematical notation does this documentation use consistently?
- What does complete HNSW pseudocode look like, paper-style and implementation-style?
- Which distance function should you choose, and when?
- What should a complete HNSW benchmark record to be trustworthy?
- How should an HNSW binary format be specified for stable persistence?
Appendices hold durable reference material: notation, full pseudocode, distance-function selection, benchmark recording checklists, and binary format considerations for HNSW persistence.
When should you reach for an appendix instead of a Part?
Use appendices when you need a canonical lookup while implementing or evaluating – not when you are learning the story for the first time. Notation keeps formulas consistent across the site. Pseudocode bridges papers and code. Distance selection summarizes metric choice. Benchmark records list what to capture. Binary format guidance stabilizes on-disk evolution.
Five appendix pages cover those jobs.
How do they support Weaviate users?
Distance and benchmark appendices inform collection config and eval harnesses. Persistence notes illuminate why snapshots and versioning matter when indexes leave process memory. Read Parts for understanding; use appendices while building.
Glossary hubs remain the place for single-term definitions.
What should you open first?
If implementing, start with pseudocode and notation. If evaluating, start with the benchmark checklist. If choosing a metric, open the distance-function appendix.
Appendices are the reference shelf beside the curriculum. Next, pick the appendix that matches your immediate task, then return to the Part you were working through.