4
32%
master: 32%

Ran 31 Aug 2018 02:23PM UTC

Files 53

Run time 4s

Badge

Embed ▾

Committed 31 Aug 2018 01:52PM UTC coverage: 39.869% (-0.02%) from 39.888%

Job # 1177.4

Build Type

push

travis-ci

Committed by

Geal

Commit Message

implement an accept queue

instead of accepting new sockets once we have room for new client
sessions (with the buffer pool usage, etc), we accept as many sockets as
possible, and put them in a LIFO queue, storing the date at which it was
accepted. We then go through that queue and create as many clients as
possible.
In normal load, the queue is always empty. Under considerable load, the
accept queue will fill up, and clients will be created in priority for
the most recent sockets (thanks to the LIFO queue), and sockets older
than 60s will be closed directly.
This allows us to keep wait times low even when under load. With the
previous code, when sozu was under load, we would avoid accepting new
connections. But those connections were already accepted by the kernel
(TCP handshake) and are holding kernel resources (some data can even be
already available). And if we take too much time accepting those, we
could get in a case where we parse that available data, send to backend,
get the response, but when we send the response to the client, the
client has already dropped the connection (timeout).
By closing sockets that are too old, we can signal early to the client
that we're overloaded, and they should try later.

Run Details

5350 of 13419 relevant lines covered (39.87%)

0.45 hits per line

sozu-proxy / sozu / 1177 / 4
32%
master: 32%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1177.4

sozu-proxy / sozu / 1177 / 4 32% master: 32%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1177.4

sozu-proxy / sozu / 1177 / 4
32%
master: 32%

README BADGES
x