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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 minutes ago