JoeDog/siege

[error] socket: unable to connect sock.c:282: Operation already in progress

lynomet opened this issue · 7 comments

I am trying to prepare for heavy website load, already optimized the open file limits and rate limit
when running Siege v4.1.5 from Ubuntu 20.04 with above 1000 Concurrency users
it takes 2 second to return this errors
"[error] socket: unable to connect sock.c:282: Operation already in progress"
any idea what;s wrong?
when running with 900 Concurrency it works just fine, limit on web servers are higher the 1k

How large is your web server's thread pool? If you schedule 1000 simulated users and you configure the server with 256 threads, then connections are going to wait for handlers until at some point they start timing out.

On Sun, Jan 8, 2023 at 4:06 PM lynomet @.> wrote: When running Siege v4.1.5 from Ubuntu with above 1000 Concurrency users it takes 2 second to return this error "[error] socket: unable to connect sock.c:282: Operation already in progress" any idea what;s wrong? am trying to prepare for heavy website load, already optimized the open file limits and rate limit — Reply to this email directly, view it on GitHub <#217>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJRHZW7UH7NH26YJFPF4MLWRMT7FANCNFSM6AAAAAATUY3PVE . You are receiving this because you are subscribed to this thread.Message ID: @.>
-- Jeff Fulmer 1-717-799-8226 https://www.joedog.org/ He codes

web server limit is at 10k, it's not even hitting the web server but immediately throw "sock.c:282" error

you mean by ten concurrent users, then run another Siege with ten users and so on, or something else?

I received Failed around 490 Concurrent