I will fix cpp race conditions memory leaks and optimize low latency performance
About this gig
Is your C++ app suffering from random SIGSEGV crashes, memory leaks, or tail-latency spikes under multithreaded loads?
I specialize in C++17/20 diagnostics, lock-free concurrency, and low-latency optimization on Linuxisolating hardware bottlenecks like False Sharing, Cache Misses, and Memory Ordering bugs.
What I Deliver:
- Crash & Race Triage: Fix segfaults, deadlocks, and data races via ASan, TSan, and UBSan.
- Cache & Latency Tuning: Profile bottlenecks with Linux perf, eliminate False Sharing (alignas(64)), and boost IPC.
- Lock-Free Design: Build thread-safe SPSC/MPMC ring buffers with strict std::memory_order semantics.
Proven Case Study (AMD EPYC / Linux):
- p99 Latency: 180.0 µs -> 2.14 µs (84x Faster)
- L1/L2 Cache Misses: 68.4% -> 1.8%
- CPU Efficiency: 0.35 IPC -> 2.31 IPC
- Stability: 100% ThreadSanitizer pass (16M+ ops, 0 races)
Why Work With Me?
- Clean modern C++20 (-Wall -Wextra -Werror) backed by perf & sanitizer proof, plus a clear root-cause report.
PLEASE MESSAGE ME BEFORE ORDERING with your OS/compiler, isolated code snippet, and crash/latency logs for a free initial check.
Get to know Peter
C plus plus 20 Low Latency Engineer, Lock Free Concurrency, Memory Debugging
- FromUnited States
- Member sinceNov 2026
Languages
English
FAQ
What information do you need from me before we start?
Please message me first with: (1) your target OS, CPU architecture, compiler version (GCC, Clang, MSVC), and C++ standard; (2) the isolated source/header files (1–5 self-contained files) or a minimal reproducible snippet; and (3) any crash logs, Sanitizer outputs, or latency goals.
Do you work on massive legacy codebases or via remote desktop (AnyDesk/TeamViewer)?
To guarantee deterministic quality and rapid turnaround, I focus strictly on self-contained modules and code-level concurrency/memory refactoring rather than live remote desktop sessions or full-system environment setups.
How do you verify that the fixes are thread-safe and leak-free?
All delivered code is engineered to pass strict compiler flags (-Wall -Wextra -Werror) and designed for verification under AddressSanitizer (ASan), ThreadSanitizer (TSan), and UBSan, complete with ready-to-run verification commands for your build environment.

