Goku

Created By
jcaromiqa year ago
Goku is an HTTP load testing application written in Rust
Overview

What is Goku?

Goku is a high-performance, scalable HTTP load-testing application written in Rust, designed for benchmarking and performance analysis of web services.

How to use Goku?

To use Goku, you can install it via automatic download, Cargo, or manual download from the GitHub Releases page. After installation, you can run tests using the command line with various options to specify the target URL, number of clients, iterations, and more.

Key features of Goku?

  • Fast and scalable HTTP load testing
  • Supports structured, real-time metrics
  • Detailed performance analytics

Use cases of Goku?

  1. Benchmarking web services under load
  2. Performance testing for API endpoints
  3. Analyzing traffic patterns and response times

FAQ from Goku?

  • Is Goku suitable for all types of web services?

Yes! Goku can be used to test any HTTP-based service.

  • How do I install Goku?

You can install Goku using automatic download, Cargo, or by manually downloading from the GitHub Releases page.

  • Can I customize the load testing parameters?

Yes! Goku allows you to customize parameters such as the number of clients, iterations, and request headers.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jcaromiq
Star
135
Language
Rust
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago