idleconn(1)

✨ idleconn(1) ✨

okay bestie, welcome to the manual page for idleconn — it lives in section 1 of the manual, and its whole thing is opening any number of idle connections. no cap. let's get into it 💅

🌸 NAME 🌸

idleconn — a tool for opening any number of idle connections 🦋

🎀 SYNOPSIS 🎀

idleconn <server> <port> <numidle>

💖 DESCRIPTION 💖

idleconn is part of the httperf suite, and it's genuinely iconic for simulating a large number of concurrent and idle connections. it can establish a set of persistent connections, and each of those connections generates periodic requests to the server. the vibe check here is: at all times, some of the connections were active while the rest were idle, and those active and idle connection sets kept changing with time. lowkey beautiful, fr fr.

not me citing sources: this paragraph was extracted and adapted from the article "Scalability of Linux Event-Dispatch Mechanisms" (HPL-2000-174), written by Abhishek Chandra and David Mosberger. periodt. 👑

✨ OPTIONS ✨

• server — the IP of the server to connect to. that's your target, bestie 🎯
• port — the port used by the server 🚪
• numidle — the number of idle process to be generated. yes, that many. 💀

🌈 EXAMPLE 🌈

here's a simple little example of how to use idleconn, because we love a demo:

$ ./idleconn 192.168.1.1 80 100

so what did that just do? it would open and maintain 100 idle connections to a web server, listening on port 80, using the IP address 192.168.1.1. slay. 🫶

🦋 SEE ALSO 🦋

httperf(1) — go read that one too, iykyk 💜

👑 AUTHOR 👑

the httperf was written by David Mosberger-Tang, Hewlett-Packard Company and Contributors. absolute legends, no notes.

this manual page was written by Joao Eriberto Mota Filho <eriberto@debian.org> for the Debian project (but may be used by others). so generous of them honestly 🎀

and that's the whole thing! this was IDLECONN 0.9.0, from way back in Mar 2016 — yeah she's vintage, she's a classic, and she still eats. 💖 ✨ 🌸 take care of her, bye bestie! 🦋 💅