What does this tool do?

It derives sysctl settings with calculateSysctl: BDP (bandwidth × RTT / 8) with 4/3 headroom sets rmem/wmem ceilings and tcp_rmem/tcp_wmem maxima, the profile sets somaxconn/syn-backlog/swappiness, and RAM scales file-max and inotify watches — emitted as key = value lines with explanations.

What is the reference calculation, and how do profiles differ?

1000 Mbps × 100 ms gives bdpBytes 12,500,000 and maxBufferBytes 16,666,667. web-server uses swappiness 10 with somaxconn 4096, database uses 1 with 2048, file-server 20 with 1024, and k8s-node 0 with 4096.

Is my host data uploaded or stored?

No. All arithmetic is local — RAM, RTT, and bandwidth never leave your browser.

Non-finite or non-positive RAM, RTT, or bandwidth (including 0) throws must be a positive number, and an unknown profile throws Unknown profile. There is no clamping fallback.

Linux Sysctl Tuner

Calculate Linux kernel and network buffer settings locally in your browser

System and network profile

RAM (GB)

RTT (ms)

Bandwidth (Mbps)

Workload profile

BDP: 12,500,000 bytes · max buffer: 16,666,667 bytes

Generated sysctl.conf

# Generated by Linux Sysctl Tuner
net.core.rmem_max = 16666667
net.core.wmem_max = 16666667
net.ipv4.tcp_rmem = 4096 87380 16666667
net.ipv4.tcp_wmem = 4096 16384 16666667
net.core.somaxconn = 4096
net.ipv4.tcp_max_syn_backlog = 8192
fs.file-max = 4194304
fs.inotify.max_user_watches = 131072
vm.swappiness = 10

Parameter	Value	Reason
net.core.rmem_max	16666667	Receive buffer ceiling is 4/3 of the 12500000 bytes BDP (1000 Mbps × 100 ms), with a 4 MiB floor.
net.core.wmem_max	16666667	Send buffer ceiling matches the BDP-derived 16666667 bytes maximum so high-latency transfers can fill the link.
net.ipv4.tcp_rmem	4096 87380 16666667	TCP receive triplet keeps Linux defaults for minimum/pressure and uses 16666667 bytes as its BDP-aware maximum.
net.ipv4.tcp_wmem	4096 16384 16666667	TCP send triplet keeps a conservative minimum and uses the same 16666667-byte BDP-aware maximum.
net.core.somaxconn	4096	Web server workload: queue up to 4096 established connections waiting for accept().
net.ipv4.tcp_max_syn_backlog	8192	Web server workload: allow 8192 pending TCP handshakes during bursts.
fs.file-max	4194304	RAM-scaled global file-handle ceiling: 4194304 (262,144 handles per GB, never below 131,072).
fs.inotify.max_user_watches	131072	RAM-scaled watcher budget: 131072 watches (8,192 per GB, never below 65,536).
vm.swappiness	10	Web server policy: prefer keeping active application pages in RAM; 10 balances cache and swap pressure.

About

Calculate BDP-aware TCP buffers plus connection queues, file handles, inotify watches, and swappiness locally in your browser.

Proxies & Observability: Nginx, Traefik, Sysctl, PromQL

Generate Nginx and Traefik proxy configs, tune Linux sysctl buffers, build valid PromQL queries with alerts, and scaffold Grafana panel JSON.

.env Secret Safety Linter

Validate .env syntax and spot likely leaked credentials or placeholder secrets.

.htaccess Generator

Build an Apache .htaccess — HTTPS redirects, rewrites, error pages, security headers, and basic auth

2D Fluid Dynamics & Particle Physics Sandbox

A physics playground with two engines sharing one canvas. The fluid mode runs a real Eulerian Navier-Stokes solver — semi-Lagrangian advection, explicit diffusion, Jacobi pressure projection and vorticity confinement — that you paint with dye and velocity using mouse or touch. The particle mode is a damped Verlet N-body engine with gravity wells, Coulomb attractors and repulsors, spring links, wall restitution and elastic circle collisions. Particle counts adapt to the device (100k target on WebGL2 desktop, 2k-5k on CPU fallback), and every configuration exports as runnable code: a Matter.js world, a PixiJS ticker setup, or a standalone vanilla Canvas engine.

AI Function Calling Schema Generator

Generate function calling JSON schemas from TypeScript interfaces

Algorithm Arena & Data Structure Visualizer

Interactive arena for algorithms and data structures: eight sorting algorithms racing on one seeded input, six pathfinding algorithms walking generated mazes, and BST, AVL, Red-Black, B-tree, heap and trie operations replayed step by step with rotations highlighted. Every run shows the Big-O table and the phase-highlighted reference implementation in four languages, and compared values can be played as pitch (sonification) through the shared audio engine. Everything runs client-side; inputs never leave the browser.

Ansible Playbook Generator

Build an Ansible playbook — hosts, vars, and tasks with modules — as YAML