Willy Tarreau 87e072eea5 MEDIUM: stick-table: use a distinct lock for the updates tree ...

Updating an entry in the updates tree is currently performed under the
table's write lock, which causes huge contention with other accesses
such as lookups and free. Aside the updates tree, the update,
localupdate and commitupdate variables, nothing is manipulated, so
let's create a distinct lock (updt_lock) to protect these together
to remove this contention. It required to add an extra lock in the
few places where we delete the update (though only if we're really
going to delete it) to protect the tree. This is very convenient
because now peer_send_teachmsgs() only needs to take this read lock,
and there is very little contention left on the stick-table.

With this alone, the performance jumped from 614k to 1140k/s on a
80-thread machine with a peers section! Stick-table updates with
no peers however now has to stand two locks and slightly regressed
from 4.0-4.1M/s to 3.9-4.0. This is fairly minimal compared to the
significant unlocking of the peers updates and considered totally
acceptable.

2023-08-11 19:03:35 +02:00

..

haproxy

MEDIUM: stick-table: use a distinct lock for the updates tree

2023-08-11 19:03:35 +02:00

import

MAJOR: threads/plock: update the embedded library again

2023-08-11 19:03:35 +02:00

make

BUILD: makefile: fix build issue on GNU make < 3.82

2023-05-24 15:51:03 +02:00