TOOL SIGNAL / DISCONTINUED

slow_cooker

Buoyant

Micro-benchmark CLI Open Source Self-hosted

NOT YET REVIEWED · CATALOG DATA

Official site ↗ Source repo ↗
Pricing model
Free; Apache License 2.0.
First released
2016
Last verified
Answer

slow_cooker sends predictable HTTP traffic for long-duration tests and emits periodic QPS and latency reports instead of only an end-of-run summary. The project is quiet and no longer a recommended current runner, so it is listed as discontinued.

What it is

slow_cooker sends predictable HTTP traffic for long-duration tests and emits periodic QPS and latency reports instead of only an end-of-run summary. The project is quiet and no longer a recommended current runner, so it is listed as discontinued.

Best for

  • Quick HTTP or protocol micro-benchmarks from a single machine
  • Teams that prefer open-source licensing and self-hosting options
  • Groups comfortable scripting in Go

Not the best fit when

  • New greenfield programs (prefer an active successor or alternative)
  • Full multi-protocol enterprise journeys and rich business-flow reporting
  • Teams unwilling to operate generators, results storage, and scaling

Architecture and concurrency

slow_cooker is typically driven as a CLI micro-benchmark with Go. It favors single-host or simple distributed runs rather than enterprise controller grids.

Fact sheet

Specs

Scripting
Go
Protocols
HTTPHTTPS
Operating systems
LinuxmacOS
Tags
goclisoakhttp
Repo health
★ 347 · last push 2023-12-05

CATALOG LAST VERIFIED · 2026-08-12 · CURATED BY NAVEENKUMAR NAMACHIVAYAM

Frequently asked

ANSWER-SHAPED
Who is slow_cooker for?

slow_cooker is best for developers who need fast HTTP or protocol micro-benchmarks from a terminal. It is open source, so teams can self-host and extend it. Vendor: Buoyant. Deployment model: self-hosted. Free; Apache License 2.0. Confirm details against the official site and a short proof-of-concept in your environment.

How does slow_cooker differ from Vegeta?

Compared with Vegeta, both sit in micro-benchmark cli, so shortlist on protocols, team skills, and pricing rather than category alone. slow_cooker lists protocols HTTP, HTTPS; Vegeta lists HTTP, HTTPS. Status is discontinued versus active. Use the Test Rig to compare full specs side by side before a proof-of-concept.

What scripting language and concurrency model does slow_cooker use?

slow_cooker uses Go for scripting or scenario definition. Runtime model: CLI-driven request generation with a lightweight concurrency model suited to single-host benchmarks. OS support: Linux, macOS. Protocols: HTTP, HTTPS. Match these to how your team already authors tests and which systems you must drive under load.

What is the cloud or enterprise path for slow_cooker?

slow_cooker is primarily self-hosted; teams typically run generators on their own machines, CI runners, or private cloud. Plan for generator capacity, network access to targets, and result storage yourself. As open source, commercial support or hosted siblings may exist separately. Check the official site. Pricing note: Free; Apache License 2.0.

What are known limitations of slow_cooker?

slow_cooker appears as discontinued in this directory. Prefer an actively maintained alternative for new work. Historical references remain so older docs and diagrams still resolve. Verify any remaining commercial support directly with the vendor before depending on it. Confirm details against the official site and a short proof-of-concept in your environment.