BOMBARDMENT(1)
π£ BOMBARDMENT(1) π£
ok so this is the bombardment page from the siege2csv manual section β yes bestie, that's the manual name, we're moving on π«Ά
β¨ NAME β¨
bombardment β run siege with an ever-increasing number of users π₯
π SYNOPSIS π
bombardment [urlfile] [clients] [increment] [trials] [delay]
bombardment urls.txt 5 10 20 1
π DESCRIPTION π
okay so bombardment is literally part of the siege distribution, no cap. it calls siege with an initial number of clients. then when that run finishes, it immediately calls siege again with that number of clients plus the increment. iconic escalation behaviour β¨
and it does this the number of times specified in the fourth argument. periodt. π
πΈ OPTIONS πΈ
urlfileβ the name of the file holding one or more URLs forsiegeto test π¦clientsβ the initial number of clients used on the first run πincrementβ how many clients get added to each ensuing run πtrialsβ the number of times to runsiegeβdelayβ the amount of time, in seconds, that each client will wait between requests. heads up: thesiegedefault gets overridden bybombardmentπ
π SEE ALSO π
siege(1), siege2csv(1) β go read those too bestie, iykyk π
π AUTHOR π
written by Peter Hutnick, et al. π«Ά
ngl that's the whole page β short, sweet, and it will absolutely ramp your client count into the stratosphere π π₯
okay bye ily, this page is from JoeDog, dated 2026-08-18 β mwah ππ
π¦ where this page comes from
- arch rolling: siege 4.2.0-1 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms