Haystack 3.4.1: our test log
Haystack 3.4.1 passed our one-tool task on a local 3B model: 3 of 3 trials; cold uv install 2.3 s.
Tested by us on 2026-10-25. Local open-weight model, not the vendor's hosted models. A smoke test on a CPU-only box, not a benchmark.
Result at a glance
| Field | Value |
|---|---|
| Result | Passed |
| Version tested | 3.4.1 |
| Date and time | 2026-10-25, 23:17 to 23:17 CDT (America/Chicago) |
| Task | Give a local model one Python function, add_numbers(a, b), and ask it to use that tool to compute 17 + 25 and report the result. Pass means the function was called with 17 and 25 and the final answer contains 42. Three trials per tool, all on the same local model. |
| Model used | Qwen2.5-3B-Instruct (Q4_K_M) through Ollama 0.40.11 |
| Hardware | Linux x86_64 virtual machine (Debian 13), 8 vCPU (Intel Xeon, 1 thread per core), 15 GiB RAM, no GPU |
| Installed size (uv) | 111 MB in 43 packages |
| Install time (uv, cold) | 2.3 s |
| Install time (pip, cold) | 8.4 s |
| Installed size (pip) | 177 MB in 44 packages |
| Task trials passed | 3 of 3 |
| Task wall time (median, includes imports) | 4.0 s (range 3.1 to 8.0 s) |
| Machine load during trials | 7.2 to 7.4 (1-minute load average, 8 vCPU) |
What we found
- 3 of 3 task trials passed: the model's tool call reached the framework, the function ran with 17 and 25, and the final answer contained 42.
- Cold install took 2.3 s with uv and 8.4 s with pip, and left 111 MB in 43 packages (uv).
- Used the Agent component with OpenAIChatGenerator and a Tool object; retrieval pipelines, the project's main use, were not exercised.
What we ran, step by step
| Step | Wall time | Exit code | Notes |
|---|---|---|---|
| Install with uv (cold, no cache) | 2.3 s | 0 | Machine load average before the run: 0.64. |
| Install with pip (cold, no cache) | 8.4 s | 0 | Load average before: 1.49. Second run; the first pip run was discarded (see the research page). |
| Task command (all trials) | n/a | n/a | Run from a directory that contains common.py (shown below). Telemetry switches were set for tools that have them. |
| Task trial 1 | 3.1 s | 0 | Tool called with [[17, 25]]; answer: The result of adding 17 and 25 is 42. Load 7.24. |
| Task trial 2 | 4 s | 0 | Tool called with [[17, 25]]; answer: The result of adding 17 and 25 is 42. Load 7.30. |
| Task trial 3 | 8 s | 0 | Tool called with [[17, 25]]; answer: The result of adding 17 and 25 is 42. Load 7.44. |
# Install with uv (cold, no cache)
uv venv -q -p 3.13 work/py/haystack && VIRTUAL_ENV=work/py/haystack uv pip install --no-cache -q haystack-ai
# Install with pip (cold, no cache)
uv venv -q --seed -p 3.13 work/pip/haystack && work/pip/haystack/bin/pip install --no-cache-dir -q haystack-ai
# Task command (all trials)
OTEL_SDK_DISABLED=true work/py/haystack/bin/python tasks/haystack_agent.pyRaw output (excerpts)
from common import *
from haystack.components.agents import Agent
from haystack.components.generators.chat import OpenAIChatGenerator
from haystack.dataclasses import ChatMessage
from haystack.tools import Tool
from haystack.utils import Secret
tool = Tool(name="add_numbers", description="Add two integers and return the sum.", parameters={"type":"object","properties":{"a":{"type":"integer"},"b":{"type":"integer"}},"required":["a","b"]}, function=add_numbers)
agent = Agent(chat_generator=OpenAIChatGenerator(model=MODEL, api_base_url=BASE, api_key=Secret.from_token(KEY), generation_kwargs={"temperature":0}), tools=[tool])
r = agent.run(messages=[ChatMessage.from_user(TASK)])
report(r["messages"][-1].text)import json, os
BASE = "http://127.0.0.1:11434/v1"
MODEL = os.environ.get("MODEL", "qwen2.5-3b")
KEY = "ollama"
TASK = "Use the add_numbers tool to compute 17 + 25, then tell me the result."
CALLS = []
def add_numbers(a: int, b: int) -> int:
"""Add two integers and return the sum."""
CALLS.append((a, b))
return int(a) + int(b)
def report(final):
ok = any({int(x), int(y)} == {17, 25} for x, y in CALLS) and "42" in str(final)
print("RESULT_JSON " + json.dumps({"calls": CALLS, "final": str(final)[:300], "ok": ok}))RESULT_JSON {"calls": [[17, 25]], "final": "The result of adding 17 and 25 is 42.", "ok": true}What we did not test
- Any vendor-hosted model: everything ran on a local 3B model, so tool-call reliability with frontier models is not measured here.
- Multi-agent flows, memory, long conversations, streaming, tracing and cloud deployment.
- Anything beyond one tool and one question; three trials is a smoke test, not a benchmark.
- Document stores, retrieval pipelines and evaluation.
Reproduce it
Versions change. These commands install whatever is latest on the day you run them unless a version is pinned, so expect different results later. The version we measured is in the table above.
# 1. Serve any local model that supports tool calling behind an OpenAI-compatible endpoint, registered as qwen2.5-3b:
# http://127.0.0.1:11434/v1 (we used Ollama with a Qwen2.5-3B-Instruct Q4_K_M GGUF)
uv venv -p 3.13 .venv && VIRTUAL_ENV=.venv uv pip install haystack-ai
# 2. Save common.py (above) and the task script next to each other, then:
.venv/bin/python haystack_agent.pyHow to read this test
Every number on this page was measured on this one machine, which also ran other jobs, so timings are indicative and vary run to run. A pass means our small task worked once or as stated, a fail means it did not work as we ran it; neither says how the tool behaves with a vendor's frontier model, on a GPU, or at scale. Where a tool could not run without an account or a GPU, we say so instead of guessing.
See the testing rig for the hardware, the local model and the rules we follow, and the test hub for every other test.
Related tests: agent frameworks and sdks
- Instructor: Instructor 1.17.0 returned a validated Pydantic object from a local 3B model in 3 of 3 trials (structured extraction, not a tool call); cold uv install 1.4 s.
- LangChain: LangChain 1.4.7 passed our one-tool task on a local 3B model: 3 of 3 trials; cold uv install 0.8 s.
- LangChain.js: LangChain.js 1.5.19 passed our one-tool task 3 of 3 on Node 20 and 3 of 3 on Node 24; about 101 MB in 36 packages.
- LangGraph: LangGraph 1.2.17 passed our one-tool task on a local 3B model: 3 of 3 trials; cold uv install 2.5 s.
- LiteLLM: LiteLLM 1.106.4 passed our one-tool task on a local 3B model: 3 of 3 trials; cold uv install 2.3 s.
- LlamaIndex: LlamaIndex 0.14.25 passed our one-tool task on a local 3B model: 3 of 3 trials; cold uv install 3.4 s.
FAQ
Does Haystack work with a local model?
In our run it did for this one task: 3 of 3 trials passed against a local Qwen2.5-3B model served by Ollama. We did not test other models, and results depend heavily on the model's tool-calling ability.
How big is a fresh Haystack install?
111 MB in 43 packages with uv on 3.4.1, measured on 2026-10-25.
Sources
- Haystack repository (fetched 2026-10-25)
Related
Markdown version for agents: /tests/haystack.md