| commit | 9628c422846c29d1ec479d326adf937c5dab63cc | [log] [tgz] |
|---|---|---|
| author | Willy Tarreau <w@1wt.eu> | Thu Oct 21 14:45:28 2021 +0200 |
| committer | Willy Tarreau <w@1wt.eu> | Thu Oct 21 15:28:24 2021 +0200 |
| tree | 0e9bd163cf01370c927416764911a495d584e9b2 | |
| parent | dd362b7b24ea24d8f3c882dab1a69cf78af7cc90 [diff] |
OPTIM: resolvers: move the eb32 node before the data in the answer_item perf top shows that we spend a lot of time trying to read item->type in the lookup loop, because the node is placed after the very long name, so when the node is found, no data is in the cache yet. Let's simply move the node upper in the struct. This results in the CPU usage of resolv_validate_dns_response() to drop by 4 points.