documentation:technical_docs:performance
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
documentation:technical_docs:performance [2019/07/09 18:04] – [Where is the bottleneck ?] olivier | documentation:technical_docs:performance [2019/11/21 17:16] – [Choosing good Hardware] olivier | ||
---|---|---|---|
Line 90: | Line 90: | ||
Avoid NUMA architecture but prefer a CPU in only one package with maximum core (8 or 16). | Avoid NUMA architecture but prefer a CPU in only one package with maximum core (8 or 16). | ||
- | If you are using NUMA, check that inbound/ | + | If you are using NUMA, check that inbound/ |
=== Network Interface Card === | === Network Interface Card === | ||
Line 764: | Line 764: | ||
less / | less / | ||
</ | </ | ||
+ | |||
+ | === Lock contention source === | ||
+ | |||
+ | To identifying lock contention source (like if function lock_delay or __mtx_lock_sleep was quite high from the pcm output), you can try to search which lock is contended and why with lockstat. | ||
+ | |||
+ | You can generate 2 output: | ||
+ | * contented locks broken down by type: < | ||
+ | * stacks associated with the lock contention to identify the source: < |
documentation/technical_docs/performance.txt · Last modified: 2020/01/18 01:04 by olivier