Siege & stress test: You should be able to use siege indefinitely without having to restart the server (take a look at siege -b).

[RanniSch]

I ran the following without restarting the server:

siege -c 10 -t 1M http://localhost:8000/animal.jpg --> perfect

siege -c 10 -t 1M http://localhost:8000/upload.html --> perfect

siege -c 10 -t 1M http://localhost:8000/index.html --> perfect

siege -c 10 -t 1M http://localhost:8000/cgi-bin/script-post-2.py --> perfect

siege -b http://localhost:8000/listing_Kopie.html when I run it short --> perfect when I run it super long

With 27 transactions failed.

[MaxIhme]

Ahh summary from the bottom: "on mac I did not have to restart the server." Via docker it gives segfaults and bad allocs

I ran the following: I had to restart the server because of segfault and "bad alloc" via docker. But in between came that.

on docker: siege -c 10 -t 1M http://localhost:8000/animal.jpg

then on mac (because i get many segfaults and bad allocs on docker) siege -c 10 -t 1M http://localhost:8000/upload.html

without restarting on mac: siege -c 10 -t 1M http://localhost:8000/index.html

without restarting on mac: -> the script does not work on my mac (don't know why) siege -c 10 -t 1M http://localhost:8000/cgi-bin/script-post-2.py

without restarting on my mac: siege -b http://localhost:8000/listing_Kopie.html

[RanniSch]

So let's wait for @LukasKava to test it.

[MaxIhme]

I have again a broken pipe via Docker and using siege. Did you guys saw that somehow? @RanniSch @LukasKava ? It happens when I do: siege -c 10 -t 1M http://localhost:8000/animal.jpg and then ctr + c siege

[MaxIhme]

I checked from the first post: siege -c 10 -t 1M http://localhost:8000/animal.jpg -> 100% availability after done I had a broken pipe! how about you @RanniSch @LukasKava