Skip to content
View ToughLad's full-sized avatar
:copilot:
:copilot:
  • San Francisco

Block or report ToughLad

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don't include any personal information such as legal names or email addresses. Markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
ToughLad/README.md

ToughLad — systems & performance

I ship low-latency services, make code cheaper, and own the tail.

Rust Go C++ Linux AWS LinkedIn


Recruiter snapshot

  • Roles: systems / backend / performance (Rust, Go, C/C++)
  • Strengths: protocol work, observability, P99/P999 control, cost/perf trade-offs
  • Scale: millions+ requests; deterministic behavior in prod
  • Availability: audits, architecture, staff-level IC

Receipts

  • Rust-AI — CPU inference with arena allocators + SIMD. ~3× faster than Python baselines on targeted workloads.
  • void-go — minimal web stack with low-alloc hot path. ~100k+ req/s synthetic, stable P99s.
  • fasthttp/http2 — stream scheduling + perf tuning used in production ecosystems.

Deterministic latency > headline throughput. I optimize for tail and jitter.


Toolbox

Rust · Go · C/C++ · epoll/kqueue · io_uring (selective) · SIMD · ring buffers · lock-free
HTTP/1.1/2 · gRPC · WebSockets · flow control · HPACK/QPACK
PostgreSQL · Redis · MongoDB (used judiciously)
perf/pprof · flamegraphs · bcc/eBPF · tracing · GitHub Actions · Docker/K8s


Approach

  1. Measure first (profiles, traces, budgets)
  2. Fix the heaviest edge (allocs → copies → locks → syscalls)
  3. Prove it (A/B, SLO deltas, cost per 10k req)
  4. Make it boring (observability, blast-radius, rollback)

Selected projects

  • Rust-AI — memory-safe inference, cache-aware data structures
  • void-go — zero-allocation hot path, sane defaults
  • fasthttp/http2 — correctness & throughput under load
Benchmark notes Throughput numbers are synthetic (wrk/vegeta) on commodity hardware; I prioritize tail-latency & jitter. Real wins came from pooling, scatter/gather I/O, fewer copies, bounded queues, and backpressure.

Contact

Email: [email protected]


“Make it work. Make it right. Make it fast.

Pinned Loading

  1. Rust-AI Rust-AI Public

    Rust

  2. dgrr/http2 dgrr/http2 Public

    HTTP/2 implementation for fasthttp

    Go 230 43