Let’s talk about the third option, since there is not much optimization needed for the first two. Embracing it, by optimizing CPU/memory placing in both user- and kernel-space.Denying it, by using single node servers, just like Facebook does with OCP Yosemite platform.Ignoring it, by disabling it in BIOS or running your software under numactl -interleave=all, you can get mediocre, but somewhat consistent performance.This is basically what NUMA is: multiple execution and storage units with a fast interconnect.įor the comprehensive overview of NUMA and its implications you can consult “ NUMA Deep Dive Series” by Frank Denneman.īut, long story short, you have a choice of: Modern CPUs are actually multiple separate CPU dies connected by very fast interconnect and sharing various resources, starting from L1 cache on the HT cores, through 元 cache within the package, to Memory and PCIe links within sockets. Unless you are only utilizing only a single NUMA node you should set vm.zone_reclaim_mode to 0.Set THP to madvise and enable them only when you are sure they are beneficial, otherwise you may get a order of magnitude slowdown while aiming for 20% latency improvement.You can use Qualys SSL Test, to verify your endpoint against the current set of best practices, and if you want to know more about TLS in general, consider subscribing to Feisty Duck Bulletproof TLS Newsletter.Īll mm/ tunings are usually very workflow specific, there are only a handful of things to recommend: Though I’ll be mentioning TLS libraries and their settings a bunch of times, you and your security team, should evaluate the performance and security implications of each of them. If you want to know more, you should read High Performance Browser Networking by Ilya Grigorik.Īnd, this is also not the TLS best practices compilation. I’ll be touching client-side performance when I cover latency-related optimizations, but only briefly. This is not a browser-performance post either. If you want to learn more about them you may want to read through Brendan Gregg’s blog. This is not a Linux performance post, even though I will make lots of references to bcc tools, eBPF, and perf, this is by no means the comprehensive guide to using performance profiling tools. For the sake of the scientific method, apply them one-by-one, measure their effect, and decide whether they are indeed useful in your environment. ![]() In this post we’ll be discussing lots of ways to tune web servers and proxies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |