From e0b1466f74694777307457f0e0226495af7368f6 Mon Sep 17 00:00:00 2001 From: Frank Date: Wed, 21 Oct 2026 02:26:24 -0700 Subject: [PATCH] docs(searxng): the upstream engine count is an order of magnitude, not a fact The intro carried "388 engine entries" from a 2026-10-19 probe; upstream is at 385 today. The number moves every week, which makes a precise one a liability in a runbook. The page now states the size class, names `/config` as the only authority for what an instance loads, and keeps the fleet's live 262 with today's date. Refs #64 --- omp-docs/agentic-web-research/searxng-tuning.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/omp-docs/agentic-web-research/searxng-tuning.md b/omp-docs/agentic-web-research/searxng-tuning.md index 4724e68..ebc8b27 100644 --- a/omp-docs/agentic-web-research/searxng-tuning.md +++ b/omp-docs/agentic-web-research/searxng-tuning.md @@ -15,11 +15,12 @@ resource: https://docs.searxng.org # SearXNG Tuning -SearXNG is a metasearch engine. It aggregates hundreds of upstream search -services into one result set (upstream `settings.yml` defines 388 engine -entries at master, probed 2026-10-19; the live fleet instance loads 262). -Configuration lives in `settings.yml`. The recommended deployment is Docker -Compose (or Podman Quadlet) with a Valkey container. +SearXNG is a metasearch engine: it aggregates upstream search services into one result set. +Upstream ships several hundred engine entries (385 in `settings.yml` at master, read +2026-10-21 — the count drifts every week, so treat it as an order of magnitude, not a fact); +what your instance actually loads is what `/config` reports, and the fleet's loads **262** +(re-read 2026-10-21). Configuration lives in `settings.yml`. The recommended deployment is +Docker Compose (or Podman Quadlet) with a Valkey container. This page lists the settings that matter for speed, privacy, and useful results.