{"id":370363,"date":"2024-05-21T04:23:33","date_gmt":"2024-05-21T04:23:33","guid":{"rendered":"http:\/\/savepearlharbor.com\/?p=370363"},"modified":"-0001-11-30T00:00:00","modified_gmt":"-0001-11-29T21:00:00","slug":"","status":"publish","type":"post","link":"https:\/\/savepearlharbor.com\/?p=370363","title":{"rendered":"<span>\u0422\u043e\u0440\u043c\u043e\u0437\u044f\u0449\u0430\u044f \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u044f \u043d\u0430 x86. \u041d\u0435\u0431\u043e\u043b\u044c\u0448\u0430\u044f \u043f\u043e\u043f\u044b\u0442\u043a\u0430 \u0440\u0430\u0437\u043e\u0431\u0440\u0430\u0442\u044c\u0441\u044f. \u0427\u0430\u0441\u0442\u044c 2: ESXi by Broadcom<\/span>"},"content":{"rendered":"<div><!--[--><!--]--><\/div>\n<div id=\"post-content-body\">\n<div>\n<div class=\"article-formatted-body article-formatted-body article-formatted-body_version-2\">\n<div xmlns=\"http:\/\/www.w3.org\/1999\/xhtml\">\n<p><strong>\u0414\u043b\u044f \u043b\u0438\u0433\u0438 \u043b\u0435\u043d\u0438.<\/strong> \u041a\u0430\u043a\u0430\u044f-\u0442\u043e \u0437\u0430\u0443\u043c\u044c \u043f\u0440\u043e \u0442\u043e, \u0447\u0442\u043e \u043d\u0435 \u043d\u0443\u0436\u043d\u043e,  \u043f\u043e\u0442\u043e\u043c\u0443 \u0447\u0442\u043e \u0432\u0441\u0435 \u0440\u0430\u0432\u043d\u043e \u0443 \u043d\u043e\u0440\u043c\u0430\u043b\u044c\u043d\u044b\u0445 \u043b\u044e\u0434\u0435\u0439 \u0432\u0441\u0435 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u0434\u0430\u0432\u043d\u043e \u0432 \u043e\u0431\u043b\u0430\u043a\u0430\u0445  \u043d\u0430 \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u0430\u0445, \u0438 \u043f\u0440\u0435\u043a\u0440\u0430\u0441\u043d\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u044e\u0442. <\/p>\n<p><a href=\"https:\/\/habr.com\/ru\/articles\/798969\/\" rel=\"noopener noreferrer nofollow\">\u0422\u043e\u0440\u043c\u043e\u0437\u044f\u0449\u0430\u044f \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u044f \u043d\u0430 x86. \u041d\u0435\u0431\u043e\u043b\u044c\u0448\u0430\u044f \u043f\u043e\u043f\u044b\u0442\u043a\u0430 \u0440\u0430\u0437\u043e\u0431\u0440\u0430\u0442\u044c\u0441\u044f. \u0427\u0430\u0441\u0442\u044c 1: \u041e\u0431\u0449\u0438\u0439 \u043e\u0431\u0437\u043e\u0440<\/a><\/p>\n<p><strong>\u0427\u0430\u0441\u0442\u044c 2.<\/strong> \u0427\u0442\u043e \u0438\u0437 \u044d\u0442\u043e\u0433\u043e \u0441\u043b\u0435\u0434\u0443\u0435\u0442, \u0438 \u043a\u0430\u043a \u0443\u0441\u0442\u0440\u043e\u0435\u043d  \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u0432 Broadcom ESXi. \u0422\u0443\u0442 \u043d\u0435 \u0431\u0443\u0434\u0435\u0442 \u043d\u0438\u0447\u0435\u0433\u043e \u043d\u043e\u0432\u043e\u0433\u043e \u0434\u043b\u044f \u0442\u0435\u0445, \u043a\u0442\u043e  \u043e\u0442\u043a\u0440\u044b\u0432\u0430\u043b \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044e \u043f\u0440\u043e \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u0435 \u043c\u043e\u0434\u0435\u043b\u0438 \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u0430 <a href=\"https:\/\/vm-guru.com\/news\/vmware-vsphere-side-channel-aware-scheduler-v2\" rel=\"noopener noreferrer nofollow\">side-channel aware scheduler (SCA) &#8212; SCAv2<\/a>, \u0434\u043e\u0431\u0430\u0432\u0438\u0432 <a href=\"https:\/\/vm-guru.com\/news\/vmware-vsphere-7-u2-amd-performance-optimization-whitepaper\" rel=\"noopener noreferrer nofollow\">Performance Optimizations in VMware vSphere 7.0 U2 CPU Scheduler for AMD EPYC Processors<\/a>\u00a0\u0438 <a href=\"https:\/\/vm-guru.com\/news\/vmware-nvidia-smartnic-dpu-performance\" rel=\"noopener noreferrer nofollow\">Optimizing Networking and Security Performance Using VMware vSphere and NVIDIA BlueField DPU with BWI<\/a>   <\/p>\n<p>\u0415\u0449\u0435 \u0432 <strong>2017<\/strong> \u0433\u043e\u0434\u0443 \u0432\u044b\u0448\u043b\u0430 \u0431\u0435\u0441\u043f\u043b\u0430\u0442\u043d\u0430\u044f \u043a\u043d\u0438\u0433\u0430 <strong>VMware vSphere 6.5 Host Resources Deep Dive<\/strong>, \u0432 \u043a\u043e\u0442\u043e\u0440\u043e\u0439 \u0442\u0435\u043c\u0430 \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0430, \u0438 \u043f\u043e\u0432\u0442\u043e\u0440\u044f\u0442\u044c \u0435\u0435 \u043d\u0435\u0442 \u0441\u043c\u044b\u0441\u043b\u0430. \u041a\u043d\u0438\u0433\u0430 \u043d\u0435 \u043d\u0430 \u0440\u0443\u0441\u0441\u043a\u043e\u043c, \u0435\u0449\u0435 \u0440\u0430\u0437: <strong>\u0431\u0435\u0441\u043f\u043b\u0430\u0442\u043d\u0430\u044f<\/strong>, \u0441\u043a\u0430\u0447\u0430\u0442\u044c \u043c\u043e\u0436\u043d\u043e <a href=\"https:\/\/www.rubrik.com\/resources\/white-papers\/19\/host-resources-deep-dive-ebook\" rel=\"noopener noreferrer nofollow\">\u0442\u0443\u0442<\/a>.<\/p>\n<p>\u0411\u043e\u043b\u0435\u0435 \u043a\u043e\u0440\u043e\u0442\u043a\u0438\u0439 \u0432\u0430\u0440\u0438\u0430\u043d\u0442, \u0431\u0443\u043a\u0432\u0430\u043b\u044c\u043d\u043e \u043d\u0430 3 \u0441\u0442\u0440\u0430\u043d\u0438\u0446\u044b \u0431\u0430\u0437\u043e\u0432\u044b\u0445 \u0442\u0435\u0440\u043c\u0438\u043d\u043e\u0432 \u0438 \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0439, \u043e\u043f\u0438\u0441\u0430\u043d \u0432 \u0441\u0442\u0430\u0442\u044c\u0435 <a href=\"https:\/\/kloudkonnect.wordpress.com\/2019\/08\/23\/understanding-esxi-cpu-scheduling\/\" rel=\"noopener noreferrer nofollow\">Understanding ESXi CPU scheduling<\/a> \u0438\u0437 2019 \u0433\u043e\u0434\u0430.<\/p>\n<p>\u0412 2018 \u0433\u043e\u0434\u0443 \u0432\u044b\u0448\u043b\u0430 ESXi 6.7 (<a href=\"https:\/\/kb.vmware.com\/s\/article\/2143832\" rel=\"noopener noreferrer nofollow\">8169922<\/a>), \u043a\u0441\u0442\u0430\u0442\u0438, \u043d\u0435 \u0437\u0430\u0431\u0443\u0434\u044c\u0442\u0435 \u043f\u043e\u0441\u0442\u0430\u0432\u0438\u0442\u044c \u043d\u0430 \u043d\u0435\u0435, \u0438 \u0432\u0441\u044e \u043b\u0438\u043d\u0435\u0439\u043a\u0443 \u043e\u0442 5.5 \u0434\u043e 8.0.2, <a href=\"https:\/\/www.vmware.com\/security\/advisories\/VMSA-2024-0006.html\" rel=\"noopener noreferrer nofollow\">\u0441\u0432\u0435\u0436\u0430\u0439\u0448\u0438\u0439 \u043f\u0430\u0442\u0447, \u0430 \u0442\u043e \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u0435 \u043f\u043e USB<\/a>, \u043d\u0430 \u043a\u043e\u0442\u043e\u0440\u0443\u044e \u0441\u0435\u0439\u0447\u0430\u0441 , \u0432 \u0440\u0435\u0437\u0443\u043b\u044c\u0442\u0430\u0442\u0435 \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u043e\u0432\u0430\u043d\u0438\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 <u>\u043f\u0440\u043e\u0446\u0435\u0441\u0441\u043e\u0440\u0430<\/u> (Spectre, Meltdown, L1TF, MDS) \u043f\u0440\u0438\u0448\u043b\u043e\u0441\u044c \u043f\u0440\u0438\u043a\u0440\u0443\u0442\u0438\u0442\u044c \u0446\u0435\u043b\u044b\u0445 \u0442\u0440\u0438 \u0432\u0430\u0440\u0438\u0430\u043d\u0442\u0430 \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u0430:<\/p>\n<ul>\n<li>\n<p> \u043f\u043e \u0443\u043c\u043e\u043b\u0447\u0430\u043d\u0438\u044e<\/p>\n<\/li>\n<li>\n<p>Side-Channel Aware Scheduler v1 (SCAv1) \u2013 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u044b\u0439, \u043d\u043e \u00ab\u0447\u0443\u0442\u044c \u0442\u043e\u0440\u043c\u043e\u0437\u0438\u0442\u00bb. <\/p>\n<\/li>\n<\/ul>\n<p> \u0412 6.7 U2 \u0434\u043e\u0431\u0430\u0432\u0438\u043b\u0438 Side-Channel Aware Scheduler v2 (SCAv2) \u2013 \u043c\u0435\u043d\u0435\u0435 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u044b\u0439, \u043f\u043e\u0447\u0442\u0438 \u043d\u0435 \u0442\u043e\u0440\u043c\u043e\u0437\u0438\u0442. <\/p>\n<p>\u0415\u0441\u0442\u044c \u0441\u0442\u0430\u0442\u044c\u044f \u0438\u0437 2019 \u0433\u043e\u0434\u0430 \u00ab\u0447\u0442\u043e \u043a\u043e\u0433\u0434\u0430 \u0432\u044b\u0431\u0438\u0440\u0430\u0442\u044c\u00bb &#8212; <a href=\"https:\/\/blogs.vmware.com\/vsphere\/2019\/05\/which-vsphere-cpu-scheduler-to-choose.html\" rel=\"noopener noreferrer nofollow\">Which vSphere CPU Scheduler to Choose<\/a> \u0438 \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u043e\u0432\u0430\u043b \u043e\u043d\u043b\u0430\u0439\u043d \u043f\u043e\u043c\u043e\u0448\u043d\u0438\u043a &#8212; vSphere 6.7 CPU Scheduler Advisor (\u0441\u043f\u0440\u044f\u0442\u0430\u043b\u0438 \u043a\u0443\u0434\u0430-\u0442\u043e).<br \/>\u0415\u0441\u0442\u044c \u0441\u0442\u0430\u0442\u044c\u044f <a href=\"https:\/\/www.vmware.com\/content\/dam\/digitalmarketing\/vmware\/en\/pdf\/techpaper\/performance\/scheduler-options-vsphere67u2-perf.pdf\" rel=\"noopener noreferrer nofollow\">Performance of vSphere 6.7 Scheduling Options<\/a><\/p>\n<p>\u0412 \u043a\u043e\u0442\u043e\u0440\u043e\u0439 \u043e\u0431\u044a\u044f\u0441\u043d\u044f\u044e\u0442\u0441\u044f \u043e\u0442\u043b\u0438\u0447\u0438\u044f \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u043e\u0432:<\/p>\n<p><strong>\u041f\u0435\u0440\u0435\u0432\u043e\u0434<\/strong><\/p>\n<p>\u0418\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f, \u043f\u0440\u0435\u0434\u043e\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u043d\u044b\u0435 ESXi, \u0432\u043a\u043b\u044e\u0447\u0430\u043b\u0438 \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u0441 \u0443\u0447\u0435\u0442\u043e\u043c \u043f\u043e\u0431\u043e\u0447\u043d\u044b\u0445 \u043a\u0430\u043d\u0430\u043b\u043e\u0432 (SCAv1), \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0441\u043d\u0438\u0436\u0430\u0435\u0442 \u043a\u043e\u043b\u0438\u0447\u0435\u0441\u0442\u0432\u043e \u0432\u0435\u043a\u0442\u043e\u0440\u043e\u0432 \u0430\u0442\u0430\u043a\u0438 \u043a\u043e\u043d\u043a\u0443\u0440\u0438\u0440\u0443\u044e\u0449\u0438\u0445 \u043a\u043e\u043d\u0442\u0435\u043a\u0441\u0442\u043e\u0432 \u0434\u043b\u044f L1TF. \u0415\u0441\u043b\u0438 \u044d\u0442\u043e\u0442 \u0440\u0435\u0436\u0438\u043c \u0432\u043a\u043b\u044e\u0447\u0435\u043d, \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u0431\u0443\u0434\u0435\u0442 \u0440\u0430\u0437\u043c\u0435\u0449\u0430\u0442\u044c \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u044b \u0442\u043e\u043b\u044c\u043a\u043e \u043d\u0430 \u043e\u0434\u043d\u043e\u043c \u043f\u043e\u0442\u043e\u043a\u0435 \u0434\u043b\u044f \u043a\u0430\u0436\u0434\u043e\u0433\u043e \u044f\u0434\u0440\u0430. \u042d\u0442\u043e\u0442 \u0440\u0435\u0436\u0438\u043c \u0432\u043b\u0438\u044f\u0435\u0442 \u043d\u0430 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c \u0433\u043b\u0430\u0432\u043d\u044b\u043c \u043e\u0431\u0440\u0430\u0437\u043e\u043c \u0441 \u0442\u043e\u0447\u043a\u0438 \u0437\u0440\u0435\u043d\u0438\u044f \u043e\u0431\u044a\u0435\u043c\u0430 (\u043c\u0430\u043a\u0441\u0438\u043c\u0430\u043b\u044c\u043d\u043e\u0433\u043e \u0447\u0438\u0441\u043b\u0430 vCPU), \u043f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0441\u0438\u0441\u0442\u0435\u043c\u0430 \u0431\u043e\u043b\u044c\u0448\u0435 \u043d\u0435 \u043c\u043e\u0436\u0435\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u043e\u0431\u0430 HT (\u043f\u043e\u0442\u043e\u043a\u0430) \u043d\u0430 \u044f\u0434\u0440\u0435. \u0421\u0435\u0440\u0432\u0435\u0440, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0443\u0436\u0435 \u0431\u044b\u043b \u043f\u043e\u043b\u043d\u043e\u0441\u0442\u044c\u044e \u0437\u0430\u0433\u0440\u0443\u0436\u0435\u043d \u0438 \u0440\u0430\u0431\u043e\u0442\u0430\u043b \u043d\u0430 \u043c\u0430\u043a\u0441\u0438\u043c\u0430\u043b\u044c\u043d\u043e\u0439 \u043c\u043e\u0449\u043d\u043e\u0441\u0442\u044c \u0441\u043d\u0438\u0437\u0438\u0442 \u043c\u043e\u0449\u043d\u043e\u0441\u0442\u044c \u043f\u0440\u0438\u043c\u0435\u0440\u043d\u043e \u043d\u0430 30%. \u0421\u0435\u0440\u0432\u0435\u0440, \u0440\u0430\u0431\u043e\u0442\u0430\u0432\u0448\u0438\u0439 \u043d\u0430 75% \u043c\u043e\u0449\u043d\u043e\u0441\u0442\u0438 \u043f\u043e\u043b\u0443\u0447\u0438\u0442 \u0433\u043e\u0440\u0430\u0437\u0434\u043e \u043c\u0435\u043d\u044c\u0448\u0435\u0435 \u043f\u0430\u0434\u0435\u043d\u0438\u0435 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438, \u043d\u043e \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0430 CPU \u0432\u043e\u0437\u0440\u0430\u0441\u0442\u0435\u0442.<\/p>\n<p>\u0412 vSphere 6.7 U2 \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u0441 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u043a\u043e\u0439 \u043f\u043e\u0431\u043e\u0447\u043d\u044b\u0445 \u043a\u0430\u043d\u0430\u043b\u043e\u0432 \u0431\u044b\u043b \u0440\u0430\u0441\u0448\u0438\u0440\u0435\u043d (SCAv2) \u0431\u043b\u0430\u0433\u043e\u0434\u0430\u0440\u044f \u043d\u043e\u0432\u043e\u0439 \u043f\u043e\u043b\u0438\u0442\u0438\u043a\u0435, \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0449\u0435\u0439 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c HT, \u0435\u0441\u043b\u0438 \u043e\u0431\u0430 (HT) \u043f\u043e\u0442\u043e\u043a\u0430 \u0432\u044b\u043f\u043e\u043b\u043d\u044f\u044e\u0442 \u043a\u043e\u043d\u0442\u0435\u043a\u0441\u0442\u044b \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0433\u043e CPU \u0438\u0437 \u043e\u0434\u043d\u043e\u0439 \u0438 \u0442\u043e\u0439 \u0436\u0435 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0439 \u043c\u0430\u0448\u0438\u043d\u044b. \u0414\u043e\u043f\u043e\u043b\u043d\u0438\u0442\u0435\u043b\u044c\u043d\u044b\u0435 \u043a\u0430\u043d\u0430\u043b\u044b L1TF* \u043e\u0433\u0440\u0430\u043d\u0438\u0447\u0435\u043d\u044b, \u0447\u0442\u043e\u0431\u044b \u043d\u0435 \u0440\u0430\u0441\u043a\u0440\u044b\u0432\u0430\u0442\u044c \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u044e \u043c\u0435\u0436\u0434\u0443 VM\/VM \u0438\u043b\u0438 VM\/\u0433\u0438\u043f\u0435\u0440\u0432\u0438\u0437\u043e\u0440.<\/p>\n<p>* L1TF &#8212; <a href=\"https:\/\/www.intel.com\/content\/www\/us\/en\/architecture-and-technology\/l1tf.html\" rel=\"noopener noreferrer nofollow\">Resources and Response to Side Channel L1 Terminal Fault<\/a>, \u0441\u043c\u043e\u0442\u0440\u0435\u0442\u044c \u0433\u0440\u0430\u0444\u0438\u043a \u0432 \u0430\u0431\u0437\u0430\u0446\u0435 For a specific subset of environments where it cannot be guaranteed that all virtualized guest operating systems are trusted.<br \/>(\u0442\u0440\u0435\u0442\u0438\u0439 \u0430\u0431\u0437\u0430\u0446 \u043d\u0435 \u043f\u0435\u0440\u0435\u0432\u0435\u0434\u0435\u043d)<\/p>\n<p><strong>\u041e\u0440\u0438\u0433\u0438\u043d\u0430\u043b<\/strong><\/p>\n<p>The ESXi-provided patches included a Side-Channel Aware Scheduler (SCAv1) that mitigates the concurrent-context attack vector for L1TF. Once this mode is enabled, the scheduler will only schedule processes on one thread for each core. This mode impacts performance mostly from a capacity standpoint because the system is no longer able to use both hyper-threads on a core. A server that was already fully utilized and running at maximum capacity would see a decrease in capacity of up to approximately 30%. A server that was running at 75% of capacity would see a much smaller impact to performance, but CPU use would rise.<\/p>\n<p>In vSphere 6.7 U2, the side-channel aware scheduler has been enhanced (SCAv2) with a new policy to allow hyper-threads to be utilized concurrently if both threads are running vCPU contexts from the same VM. In this way, L1TF side channels are constrained to not expose information across VM\/VM or VM\/hypervisor boundaries<\/p>\n<p>To further illustrate how SCAv1 and SCAv2 work, the diagrams below show generally how different schedulers might schedule vCPUs from VMs on the same core. When there is only one VM in the picture (figure 1), the default placement, SCAv1 and SCAv2 will assign one vCPU on each core. When there are two VMs in the picture (figure 2), the default scheduler might schedule vCPUs from two different VMs on the same core, but SCAv1 and SCAv2 will ensure that only the vCPUs from the same VM will be scheduled on the same core. In the case of SCAv1, only one thread is used. In the case of SCAv2, both threads are used, but this always occurs with the vCPUs from the same VM running on a single core.<\/p>\n<p>\u0414\u0430\u043b\u044c\u0448\u0435 \u0432 \u0441\u0442\u0430\u0442\u044c\u0435 \u0438\u0434\u0443\u0442 \u0433\u0440\u0430\u0444\u0438\u043a\u0438, \u043a\u0430\u043a \u0440\u0430\u0437\u043d\u044b\u0435 \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u0438 \u0432\u043b\u0438\u044f\u044e\u0442 \u043d\u0430 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c \u0440\u0430\u0437\u043d\u044b\u0445 \u0442\u0438\u043f\u043e\u0432 VM. \u0414\u043e 30% \u043f\u043e\u0442\u0435\u0440\u044c (\u043e\u0441\u0442\u0430\u0435\u0442\u0441\u044f 70%), \u0447\u0442\u043e \u043e\u0447\u0435\u043d\u044c \u0442\u0430\u043a \u043d\u0435\u043f\u043b\u043e\u0445\u043e.<\/p>\n<p><strong>\u0427\u0442\u043e \u0435\u0449\u0435 \u043d\u0430\u0434\u043e \u0437\u043d\u0430\u0442\u044c \u043f\u0440\u043e \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u0432 ESXi<\/strong><\/p>\n<p>\u041f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u043e\u043f\u0435\u0440\u0438\u0440\u0443\u0435\u0442 \u00ab\u043c\u0438\u0440\u0430\u043c\u0438\u00bb &#8212;\u00a0 world, \u043f\u0440\u0438 \u044d\u0442\u043e\u043c \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u044e\u0442 \u043e\u0442\u0434\u0435\u043b\u044c\u043d\u044b\u0435 \u00ab\u043c\u0438\u0440\u044b\u00bb \u0434\u043b\u044f vcpu (vmx-vcpu), vmx-svga, kvm (vmx-ms), \u0441\u0435\u0442\u0438 \u0438 \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u043e\u0432 \u0441\u0430\u043c\u043e\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u044b. <\/p>\n<p>\u041f\u0440\u043e\u0447\u0438\u0442\u0430\u0442\u044c \u043f\u0440\u043e \u044d\u0442\u043e \u043c\u043e\u0436\u043d\u043e, \u043d\u0430\u0447\u0438\u043d\u0430\u044f (\u043a\u0440\u043e\u043c\u0435 \u0432\u044b\u0448\u0435\u043f\u043e\u043c\u044f\u043d\u0443\u0442\u043e\u0433\u043e Deep dive) \u0432 \u0441\u0442\u0430\u0442\u044c\u0435 <a href=\"https:\/\/blogs.virtualmaestro.in\/2020\/06\/24\/vsphere-6-7-u2-later-cpu-scheduler-modes-default-sca-v1-and-sca-v2\/\" rel=\"noopener noreferrer nofollow\">vSphere 6.7 U2 &amp; later CPU Scheduler modes: Default, SCA v1 and SCA v2<\/a> <\/p>\n<p>\u041a\u0430\u0436\u0434\u044b\u0435 2-30 \u043c\u0438\u043b\u043b\u0438\u0441\u0435\u043a\u0443\u043d\u0434 (1\/1000 \u0441\u0435\u043a\u0443\u043d\u0434\u044b) \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u043f\u0440\u043e\u0432\u0435\u0440\u044f\u0435\u0442 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0443 \u043d\u0430 \u0444\u0438\u0437\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u044f\u0434\u0440\u0430\u0445, \u0438 \u0432\u044b\u0434\u0430\u0435\u0442 \u0442\u0430\u0439\u043c\u0441\u043b\u043e\u0442 (\u0441\u043b\u0430\u0439\u0441) \u0434\u043b\u044f \u0438\u0441\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f vCPU > pCPU. \u041c\u043e\u0436\u043d\u043e \u043f\u043e\u043d\u044b\u0440\u044f\u0442\u044c \u0432 NUMA, \u0442\u043e\u0433\u0434\u0430 \u0441\u0442\u0430\u043d\u0435\u0442 \u0435\u0449\u0435 \u0441\u043b\u043e\u0436\u043d\u0435\u0435 \u043f\u043e\u043d\u044f\u0442\u044c, \u0447\u0442\u043e \u0442\u0430\u043c \u0441\u043d\u0438\u0437\u0443 \u043d\u0430 \u0444\u0438\u0437\u0438\u043a\u0435. <\/p>\n<p>\u0417\u0430\u0442\u0435\u043c \u0432 \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u0434\u043e\u0431\u0430\u0432\u043b\u044f\u044e\u0442\u0441\u044f \u043f\u0440\u0438\u043e\u0440\u0438\u0442\u0435\u0442\u044b \u0438\u0441\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f, \u043a\u043e\u043c\u0443 \u0434\u0430\u0432\u0430\u0442\u044c \u0431\u043e\u043b\u044c\u0448\u0435 \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u043e\u0440\u0430 (\u0438 \u043f\u0430\u043c\u044f\u0442\u0438), \u043e\u043f\u0438\u0441\u0430\u043d\u043d\u044b\u0435 \u0432 \u0440\u0430\u0437\u0434\u0435\u043b\u0435 <a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/7.0\/com.vmware.vsphere.resmgmt.doc\/GUID-8B88D3D8-E9D9-4C05-A065-B3DE1FFFB401.html\" rel=\"noopener noreferrer nofollow\">Resource Allocation Reservation<\/a>. <\/p>\n<p>\u041f\u0440\u0438 \u044d\u0442\u043e\u043c \u0440\u0435\u0441\u0443\u0440\u0441\u044b \u0441\u0447\u0438\u0442\u0430\u044e\u0442\u0441\u044f \u043d\u0435 \u043f\u043e \u0433\u0438\u0433\u0430\u0433\u0435\u0440\u0446\u0430\u043c, \u0430 \u043f\u043e shares, \u0432 \u0437\u0430\u0432\u0438\u0441\u0438\u043c\u043e\u0441\u0442\u0438 \u043e\u0442 \u043f\u0440\u0438\u043e\u0440\u0438\u0442\u0435\u0442\u0430. <br \/>\u0418 \u0435\u0441\u0442\u044c, \u043a\u0430\u043a \u0441\u043a\u0430\u0437\u0430\u043d\u043e \u0432 \u043f\u0435\u0440\u0432\u043e\u0439 \u0447\u0430\u0441\u0442\u0438, \u043e\u0442\u0434\u0435\u043b\u044c\u043d\u0430\u044f \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 &#8212; <a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/7.0\/com.vmware.vsphere.resmgmt.doc\/GUID-9F4FD589-A73B-454A-A5A5-FED4C0F918C3.html\" rel=\"noopener noreferrer nofollow\">Latency Sensitivity<\/a> \u0441\u043e \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u043c\u0438 \u043e\u0433\u0440\u0430\u043d\u0438\u0447\u0435\u043d\u0438\u044f\u043c\u0438:<\/p>\n<p><strong>\u041e\u0440\u0438\u0433\u0438\u043d\u0430\u043b, \u0442\u0443\u0442 \u0432\u0441\u0435 \u043f\u043e\u043d\u044f\u0442\u043d\u043e \u0438 \u0431\u0435\u0437 \u043f\u0435\u0440\u0435\u0432\u043e\u0434\u0430<\/strong><\/p>\n<p>You can turn on latency sensitivity for each VM at the VM level or at the host level. <br \/>This feature:<br \/>Gives exclusive access to physical resources to avoid resource contention due to sharing<br \/>With exclusive physical CPU (pCPU) access given, each vCPU entirely owns a specific pCPU; no other vCPUs and threads (including VMkernel I\/O threads) are allowed to run on it. This achieves nearly zero ready time and no interruption from other VMkernel threads, improving response time and jitter under CPU contention.<br \/>Bypasses virtualization layers to eliminate the overhead of extra processing<br \/>Once exclusive access to pCPUs is obtained, the feature allows the vCPUs to bypass the VMkernel\u2019s CPU scheduling layer and directly halt in the virtual machine monitor (VMM), since there are no other contexts that need to be scheduled. <u>That way, the cost of running the CPU scheduler code and the cost of switching between the VMkernel and VMM are avoided<\/u>, leading to much faster vCPU halt\/wake-up operations.<br \/>Tunes virtualization layers to reduce the overhead<br \/>When the VMXNET3 paravirtualized device is used for VNICs in the VM, VNIC interrupt coalescing and LRO support for the VNICs are automatically disabled to reduce response time and jitter.<br \/>Although these and other features are disabled automatically when setting latency sensitivity to high, <u>we recommend disabling each of these features independently<\/u> to avoid any cascading effects when a single parameter is altered when tuning your virtual machines.<\/p>\n<p><strong>\u041f\u043e \u044d\u0442\u043e\u0439 (Latency Sensitivity) \u0442\u0435\u043c\u0435 \u043c\u043e\u0436\u043d\u043e \u043f\u043e\u0447\u0438\u0442\u0430\u0442\u044c \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0435\u0435: <br \/><\/strong><a href=\"https:\/\/communities.vmware.com\/t5\/VMware-vSphere-Discussions\/Shares-explanation\/td-p\/2222956\" rel=\"noopener noreferrer nofollow\">Shares explanation <\/a><br \/><a href=\"https:\/\/www.vmware.com\/content\/dam\/digitalmarketing\/vmware\/en\/pdf\/techpaper\/latency-sensitive-perf-vsphere55-white-paper.pdf\" rel=\"noopener noreferrer nofollow\">Deploying Extremely Latency-Sensitive Applications in VMware vSphere 5.5<\/a> (\u043e\u0447\u0435\u043d\u044c \u0441\u0442\u0430\u0440\u044b\u0439, \u043d\u043e \u0432\u0441\u0435 \u0435\u0449\u0435 \u043f\u043e\u043b\u0435\u0437\u043d\u044b\u0439 \u0442\u0435\u043a\u0441\u0442)<br \/><a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/6.7\/vsphere-esxi-vcenter-server-672-resource-management-guide.pdf\" rel=\"noopener noreferrer nofollow\">vSphere Resource Management Update 2 14 AUG 2020 VMware vSphere 6.7<\/a><br \/><a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/7.0\/vsphere-esxi-vcenter-server-703-resource-management-guide.pdf\" rel=\"noopener noreferrer nofollow\">vSphere Resource Management Update 3 VMware vSphere 7.0 <\/a><br \/><a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/7.0\/vsphere-esxi-vcenter-server-703-host-management-guide.pdf\" rel=\"noopener noreferrer nofollow\">vCenter Server and Host Management Update 3 Modified on 08 JAN 2024 VMware vSphere 7.0<\/a><\/p>\n<p>\u041d\u0430\u0434\u043e \u0437\u0430\u043c\u0435\u0442\u0438\u0442\u044c, \u0447\u0442\u043e \u0435\u0449\u0435 \u0432 \u043a\u043e\u043d\u0446\u0435 2022 \u0432\u044b\u0448\u043b\u0430 ESXi 8.0 GA \u2013 \u044d\u0442\u043e \u0434\u0430\u0436\u0435 \u043e\u0444\u0438\u0446\u0438\u0430\u043b\u044c\u043d\u043e<a href=\"https:\/\/blogs.vmware.com\/vsphere\/2022\/10\/new-release-model-for-vsphere-8.html\" rel=\"noopener noreferrer nofollow\"> Public beta, \u0441\u043e\u0433\u043b\u0430\u0441\u043d\u043e New Release Model for vSphere 8<\/a>, \u0447\u0442\u043e \u0438 \u043f\u043e\u043a\u0430\u0437\u0430\u043d\u043e \u0432 \u0441\u043f\u0438\u0441\u043a\u0435 \u0437\u0430\u043a\u0440\u044b\u0442\u044b\u0445 \u0431\u0430\u0433\u043e\u0432 \u0434\u043b\u044f ESXi 8.0 Update 2 (<em>\u042d\u0442\u043e\u0442 \u0430\u0431\u0437\u0430\u0446 \u043f\u043e\u0441\u0432\u044f\u0449\u0435\u043d The \u043e\u0434\u043d\u043e\u043c\u0443 \u043c\u043e\u0435\u043c\u0443 \u0437\u043d\u0430\u043a\u043e\u043c\u043e\u043c\u0443. \u041f\u043e\u043a\u043e\u0439\u043d\u043e\u043c\u0443<\/em>), \u0430 \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044e \u043e\u0431\u043d\u043e\u0432\u043b\u044f\u044e\u0442 \u0434\u043b\u044f 7. <\/p>\n<p>\u041a\u0440\u043e\u043c\u0435 \u043f\u0440\u043e\u0447\u0435\u0433\u043e, \u00a0\u043d\u0430 \u0441\u043a\u043e\u0440\u043e\u0441\u0442\u044c \u0440\u0430\u0431\u043e\u0442\u044b \u0432\u043b\u0438\u044f\u0435\u0442 \u0432\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u0435 \\ \u0432\u044b\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u0435 CPU Hot add , \u043f\u043e\u0434\u0440\u043e\u0431\u043d\u0435\u0439\u0448\u0435 \u043e\u043f\u0438\u0441\u0430\u043d\u043d\u043e\u0435 \u0432 2017 &#8212; <a href=\"https:\/\/blogs.vmware.com\/performance\/2017\/03\/virtual-machine-vcpu-and-vnuma-rightsizing-rules-of-thumb.html\" rel=\"noopener noreferrer nofollow\">Virtual Machine vCPU and vNUMA Rightsizing \u2013 Guidelines<\/a>, <br \/>\u0440\u0430\u0437\u0434\u0435\u043b <a href=\"https:\/\/frankdenneman.nl\/2017\/04\/14\/impact-cpu-hot-add-numa-scheduling\/\" rel=\"noopener noreferrer nofollow\">Impact of CPU Hot Add on NUMA schedulin<\/a>g  \u0438 \u0432 \u0441\u0442\u0430\u0442\u044c\u0435 <a href=\"https:\/\/blogs.vmware.com\/performance\/2019\/12\/cpu-hot-add-performance-vsphere67.html\" rel=\"noopener noreferrer nofollow\">CPU Hot Add Performance in vSphere 6.7<\/a> <\/p>\n<p>\u041f\u0435\u0440\u0435\u0432\u043e\u0434 \u0441 \u0434\u043e\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f\u043c\u0438 \u0438\u0437 2019: <a href=\"https:\/\/vm-guru.com\/news\/vmware-vsphere-vcpu-hot-add-performance\" rel=\"noopener noreferrer nofollow\">\u041f\u043e\u0447\u0435\u043c\u0443 CPU Hot Add \u0432\u044b\u043a\u043b\u044e\u0447\u0435\u043d\u043e \u043f\u043e \u0443\u043c\u043e\u043b\u0447\u0430\u043d\u0438\u044e \u0432 VMware vSphere, \u0438 \u043a\u0430\u043a \u044d\u0442\u043e \u0432\u043b\u0438\u044f\u0435\u0442 \u043d\u0430 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c?<\/a><\/p>\n<p>\u041c\u043e\u0436\u043d\u043e VM \u043f\u0440\u0438\u0431\u0438\u0442\u044c \u0433\u0432\u043e\u0437\u0434\u044f\u043c\u0438 \u043f\u0440\u044f\u043c\u043e \u043a \u044f\u0434\u0440\u0443 &#8212; <a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/7.0\/com.vmware.vsphere.resmgmt.doc\/GUID-F40F901D-C1A7-43E2-90AF-E6F98C960E4B.html\" rel=\"noopener noreferrer nofollow\">Assign a Virtual Machine to a Specific Processor<\/a><\/p>\n<p><strong>\u0427\u0442\u043e \u0432\u0441\u0435 \u044d\u0442\u043e \u0437\u043d\u0430\u0447\u0438\u0442 \u00ab\u0432 \u0446\u0435\u043b\u043e\u043c\u00bb<\/strong><\/p>\n<p>\u041f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u0432 ESXi by Broadcom \u0437\u0430\u0432\u0438\u0441\u0438\u0442 \u043e\u0442 \u0434\u0435\u0441\u044f\u0442\u043a\u043e\u0432 \u0444\u0430\u043a\u0442\u043e\u0440\u043e\u0432, \u0438\u0437 \u043a\u043e\u0442\u043e\u0440\u044b\u0445 \u043e\u0441\u043d\u043e\u0432\u043d\u044b\u043c\u0438 \u044f\u0432\u043b\u044f\u044e\u0442\u0441\u044f:<\/p>\n<p>\u041f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u044b\u0435 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0438 \u044d\u043d\u0435\u0440\u0433\u043e\u0441\u0431\u0435\u0440\u0435\u0436\u0435\u043d\u0438\u044f \u0432 BIOS \u0438 \u0441\u0430\u043c\u043e\u0439 ESXi &#8212; <a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/8.0\/vsphere-resource-management\/GUID-4D1A6F4A-8C99-47C1-A8E6-EF3865603F5B.html\" rel=\"noopener noreferrer nofollow\">Host Power Management Policies in ESXi<\/a><br \/>\u0423\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430 \u0430\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0439 \u0434\u043b\u044f BIOS \/ CPU \u0438 \u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u044b\u0439 \u0432\u044b\u0431\u043e\u0440 \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u0430<br \/>\u0423\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430 \u0430\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0439 \u0434\u043b\u044f ESXi by Broadcom<br \/>\u0412\u044b\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u0435 CPU \\ RAM hot add, \u0435\u0441\u043b\u0438 \u0437\u0430\u0447\u0435\u043c-\u0442\u043e \u0432\u043a\u043b\u044e\u0447\u0438\u043b\u0438<br \/>\u0423\u043c\u0435\u043d\u044c\u0448\u0435\u043d\u0438\u0435 (\u0434\u0430, \u0438\u043c\u0435\u043d\u043d\u043e \u0443\u043c\u0435\u043d\u044c\u0448\u0435\u043d\u0438\u0435) \u0447\u0438\u0441\u043b\u0430 vCPU \u0434\u043e \u00ab\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043d\u0443\u0436\u043d\u043e\u00bb, \u0430 \u043d\u0435 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430 \u00ab\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043f\u043e\u043f\u0440\u043e\u0441\u0438\u043b\u0438\u00bb. \u0411\u043e\u043b\u044c\u0448\u0435 \u0432 \u0434\u0430\u043d\u043d\u043e\u043c \u0441\u043b\u0443\u0447\u0430\u0435 \u2013 \u041d\u0415 \u0437\u043d\u0430\u0447\u0438\u0442 \u043b\u0443\u0447\u0448\u0435. <br \/>\u041d\u0430\u0431\u043b\u044e\u0434\u0435\u043d\u0438\u0435 \u0437\u0430 esxtop <a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/8.0\/vsphere-monitoring-performance\/GUID-D89E8267-C74A-496F-B58E-19672CAB5A53.html\" rel=\"noopener noreferrer nofollow\">\u0440\u0430\u0437<\/a>, \u0434\u0432\u0430 Using esxtop to identify storage performance issues for ESX \/ ESXi (multiple versions) (<a href=\"https:\/\/kb.vmware.com\/s\/article\/1008205\" rel=\"noopener noreferrer nofollow\">1008205<\/a>) \u00a0<a href=\"https:\/\/www.virten.net\/vmware\/esxtop\/\" rel=\"noopener noreferrer nofollow\">\u0442\u0440\u0438 <\/a><a href=\"https:\/\/www.virtualizationhowto.com\/2023\/07\/esxtop-commands-the-ultimate-guide\/\" rel=\"noopener noreferrer nofollow\">\u0447\u0435\u0442\u044b\u0440\u0435 <\/a><a href=\"https:\/\/www.yellow-bricks.com\/2020\/04\/02\/esxtop-in-vsphere-7\/\" rel=\"noopener noreferrer nofollow\">\u043f\u044f\u0442\u044c <\/a><a href=\"https:\/\/www.yellow-bricks.com\/esxtop\/\" rel=\"noopener noreferrer nofollow\">\u0448\u0435\u0441\u0442\u044c <\/a><\/p>\n<p>\u0418 \u043f\u043e\u0438\u0441\u043a\u0430\u0442\u044c \u0440\u043e\u043b\u0438\u043a (\u043a\u0443\u0434\u0430 \u0442\u043e \u0441\u043f\u0440\u044f\u0442\u0430\u043b\u0438) \u0441 60 Minutes of Non-Uniform Memory Architecture [HBI2278BE] by Frank Denneman \u0438\u0437 2019 \u0433\u043e\u0434\u0430 <\/p>\n<p><strong>\u041d\u0430 \u0441\u043b\u0430\u0434\u043a\u043e\u0435 \u2013 \u0437\u0430\u043d\u044b\u0440\u0438\u0432\u0430\u0442\u044c \u0432 NUMA &#8212; The 2016 NUMA Deep Dive Series \u043e\u0442 \u0432\u0441\u0435 \u0442\u043e\u0433\u043e \u0436\u0435 \u0430\u0432\u0442\u043e\u0440\u0430: Frank Denneman<\/strong><\/p>\n<p><a href=\"https:\/\/frankdenneman.nl\/2016\/07\/06\/introduction-2016-numa-deep-dive-series\/\" rel=\"noopener noreferrer nofollow\">Part 0: Introduction NUMA Deep Dive Series <\/a><br \/><a href=\"http:\/\/frankdenneman.nl\/2016\/07\/07\/numa-deep-dive-part-1-uma-numa\/\" rel=\"noopener noreferrer nofollow\">Part 1: From UMA to NUMA <\/a><br \/><a href=\"http:\/\/frankdenneman.nl\/2016\/07\/08\/numa-deep-dive-part-2-system-architecture\/\" rel=\"noopener noreferrer nofollow\">Part 2: System Architecture <\/a><br \/><a href=\"http:\/\/frankdenneman.nl\/2016\/07\/11\/numa-deep-dive-part-3-cache-coherency\/\" rel=\"noopener noreferrer nofollow\">Part 3: Cache Coherency\u00a0 <\/a><br \/><a href=\"http:\/\/frankdenneman.nl\/2016\/08\/22\/numa-deep-dive-part-5-esxi-vmkernel-numa-constructs\/\" rel=\"noopener noreferrer nofollow\">Part 4: Local Memory Optimization <\/a><br \/><a href=\"https:\/\/frankdenneman.nl\/2016\/08\/22\/numa-deep-dive-part-5-esxi-vmkernel-numa-constructs\/\" rel=\"noopener noreferrer nofollow\">Part 5: ESXi VMkernel NUMA Constructs <\/a><br \/>Part 6: NUMA Initial Placement and Load Balancing Operations (\u043d\u0435 \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d\u0430)<br \/>Part 7: From NUMA to UMA (\u043d\u0435 \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d\u0430)<\/p>\n<p><strong>\u0418\u0442\u043e\u0433\u043e<\/strong><\/p>\n<p>\u0412\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u044f \u0431\u0435\u0437 \u043d\u0430\u0441\u0442\u0440\u043e\u0435\u043a \u043e\u043f\u0442\u0438\u043c\u0438\u0437\u0430\u0446\u0438\u0438, \u0438\u0437 \u043a\u043e\u0440\u043e\u0431\u043a\u0438 \u043f\u043e \u0443\u043c\u043e\u043b\u0447\u0430\u043d\u0438\u044e, \u0431\u0435\u0437\u0443\u0441\u043b\u043e\u0432\u043d\u043e, \u0442\u043e\u0440\u043c\u043e\u0437\u0438\u0442, \u043f\u043e \u0441\u0440\u0430\u0432\u043d\u0435\u043d\u0438\u044e \u0441 \u0447\u0438\u0441\u0442\u044b\u043c bare metal, \u043d\u0430 \u043a\u043e\u0442\u043e\u0440\u043e\u043c \u0437\u0430\u043f\u0443\u0449\u0435\u043d\u0430 1 (\u043e\u0434\u043d\u0430) \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u0430, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442 100% CPU \u0438 100% RAM, \u0438 \u043d\u0438\u0447\u0435\u0433\u043e \u043d\u0435 \u043f\u0438\u0448\u0435\u0442 \u043d\u0430 \u0434\u0438\u0441\u043a\u0438, \u0438 \u043d\u0435 \u0447\u0438\u0442\u0430\u0435\u0442 \u0441 \u043d\u0438\u0445. \u041f\u043e\u0442\u043e\u043c\u0443 \u0447\u0442\u043e \u0435\u0441\u043b\u0438 \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u0430 \u043f\u0438\u0448\u0435\u0442, \u0438 \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u0447\u0438\u0442\u0430\u0435\u0442, \u0442\u043e \u0442\u0443\u0442 \u0431\u0443\u0434\u0435\u0442 \u0438\u043c\u0435\u0442\u044c \u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0435 \u0435\u0449\u0435 \u0438 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 \u043b\u043e\u043a\u0430\u043b\u044c\u043d\u043e\u0439 \u0438 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u043e\u0439 \u0434\u0438\u0441\u043a\u043e\u0432\u044b\u0445 \u043f\u043e\u0434\u0441\u0438\u0441\u0442\u0435\u043c, \u0431\u0443\u0444\u0435\u0440\u043e\u0432 \u0438 \u0440\u0435\u0436\u0438\u043c\u043e\u0432 \u043a\u043e\u043c\u043c\u0443\u0442\u0430\u0446\u0438\u0438 \u0432\u0441\u0435\u0445 \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432 \u043f\u043e \u043f\u0443\u0442\u0438, \u0441\u043a\u043e\u0440\u043e\u0441\u0442\u0438 \u0440\u0430\u0431\u043e\u0442\u044b Ethernet \u2013 \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u0435\u0441\u043b\u0438 \u043f\u043e \u043f\u0443\u0442\u0438 \u0432\u043a\u0440\u0443\u0447\u0435\u043d DCB, \u0438 \u043b\u043e\u043a\u0430\u043b\u044c\u043d\u043e \u043f\u0440\u0438\u043a\u0440\u0443\u0447\u0435\u043d\u044b TSO \u0438 \u043f\u0440\u043e\u0447\u0430\u044f.<\/p>\n<p>\u041e\u0434\u043d\u0430\u043a\u043e, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0441\u043e\u0432\u0440\u0435\u043c\u0435\u043d\u043d\u044b\u0439 \u0441\u0435\u0440\u0432\u0435\u0440, \u0434\u0430\u0436\u0435 \u043f\u0440\u043e\u0441\u0442\u0435\u0439\u0448\u0438\u0439 ARM \u043d\u0430 32 \u044f\u0434\u0440\u0430, \u0434\u043b\u044f 1-2 \u0437\u0430\u0434\u0430\u0447, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0435\u0449\u0435 \u0438, \u0432 \u0441\u0438\u043b\u0443 \u0444\u0443\u043d\u0434\u0430\u043c\u0435\u043d\u0442\u0430 \u0438\u0437 \u043a\u043e\u0441\u0442\u044b\u043b\u0435\u0439 (1\u0441), \u0442\u043e\u0440\u043c\u043e\u0437\u044f\u0442 \u043d\u0430 \u043b\u044e\u0431\u043e\u043c \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0435 \u0438 \u043d\u0435 \u0441\u043f\u043e\u0441\u043e\u0431\u043d\u044b \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0432\u0441\u0435 32 \u044f\u0434\u0440\u0430 \u2013 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u044d\u043a\u043e\u043d\u043e\u043c\u0438\u0447\u0435\u0441\u043a\u0438 \u043d\u0435\u0446\u0435\u043b\u0435\u0441\u043e\u043e\u0431\u0440\u0430\u0437\u043d\u043e. \u0425\u043e\u0442\u044f \u0438 \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e, \u044d\u0442\u043e \u0432\u044b\u0431\u043e\u0440 \u0431\u0438\u0437\u043d\u0435\u0441\u0430, \u0447\u0442\u043e \u043f\u043e\u043a\u0443\u043f\u0430\u0442\u044c \u0438 \u043a\u0430\u043a \u043f\u0440\u0438\u043c\u0435\u043d\u044f\u0442\u044c. \u0423 \u043e\u0434\u043d\u0438\u0445 \u043c\u043e\u0438\u0445 \u043a\u043e\u043b\u043b\u0435\u0433 \u0441\u0435\u0440\u0432\u0435\u0440\u0430 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043b\u0438\u0441\u044c \u0434\u043b\u044f \u043e\u043f\u0442\u0438\u043c\u0438\u0437\u0430\u0446\u0438\u0438 \u0432\u043e\u0437\u0434\u0443\u0448\u043d\u044b\u0445 \u043f\u043e\u0442\u043e\u043a\u043e\u0432 \u0432 \u0441\u0442\u043e\u0439\u043a\u0435 \u2013 \u043f\u043e\u0442\u043e\u043c\u0443 \u0447\u0442\u043e \u0437\u0430\u0433\u043b\u0443\u0448\u043a\u0438 \u043d\u0430 \u0441\u0442\u043e\u0439\u043a\u0443 \u043d\u0430\u0434\u043e \u043f\u043e\u043a\u0443\u043f\u0430\u0442\u044c \u0447\u0435\u0440\u0435\u0437 \u043a\u043e\u043d\u043a\u0443\u0440\u0441, \u0441\u0435\u0440\u0432\u0435\u0440\u0430 \u0432 \u0441\u0442\u043e\u0439\u043a\u0435 \u0443\u0436\u0435 \u0435\u0441\u0442\u044c, \u0430 \u0432\u044b\u0432\u043e\u0437 \u0441\u0435\u0440\u0432\u0435\u0440\u0430 \u0438\u0437 \u0426\u041e\u0414 &#8212; \u043c\u0435\u0440\u043e\u043f\u0440\u0438\u044f\u0442\u0438\u0435 \u043d\u0430 \u043f\u043e\u043b\u043e\u0432\u0438\u043d\u0443 \u0434\u043d\u044f, \u043f\u043e\u0442\u043e\u043c\u0443 \u0447\u0442\u043e \u0434\u043b\u044f \u044d\u0442\u043e\u0433\u043e \u043d\u0443\u0436\u043d\u043e \u043f\u0440\u0438\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b\u044c\u043d\u043e \u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0435\u043d\u043d\u043e\u0433\u043e \u043b\u0438\u0446\u0430. \u041f\u043e\u044d\u0442\u043e\u043c\u0443 \u0441\u0435\u0440\u0432\u0435\u0440\u0430 \u0440\u0430\u0431\u043e\u0442\u0430\u043b\u0438 \u0437\u0430\u0433\u043b\u0443\u0448\u043a\u043e\u0439. \u041e\u0447\u0435\u043d\u044c \u043f\u043e\u043c\u043e\u0433\u0430\u043b\u043e, \u043a\u0441\u0442\u0430\u0442\u0438, \u043f\u0440\u043e\u0442\u0438\u0432 \u043f\u043e\u0434\u0441\u043e\u0441\u0430 \u0433\u043e\u0440\u044f\u0447\u0435\u0433\u043e \u0432\u043e\u0437\u0434\u0443\u0445\u0430 \u0441 \u0442\u044b\u043b\u0430 \u0441\u0442\u043e\u0439\u043a\u0438 \u043d\u0430 \u0444\u0440\u043e\u043d\u0442.<\/p>\n<p>\u0414\u043b\u044f \u0442\u043e\u0433\u043e, \u0447\u0442\u043e\u0431\u044b \u043f\u0435\u0440\u0435\u0439\u0442\u0438 \u043e\u0442 \u0432\u043d\u0443\u0442\u0440\u0435\u043d\u043d\u0435\u0433\u043e \u043e\u0449\u0443\u0449\u0435\u043d\u0438\u044f \u00ab\u0442\u043e\u0440\u043c\u043e\u0436\u0435\u043d\u0438\u044f\u00bb \u043a \u043a\u0430\u043a\u0438\u043c-\u0442\u043e \u0446\u0438\u0444\u0440\u0430\u043c, \u0435\u0441\u0442\u044c esxtop, \u0435\u0441\u0442\u044c cpu ready \u0438 \u0434\u0435\u0441\u044f\u0442\u043e\u043a \u0438\u043d\u044b\u0445 \u0441\u0447\u0435\u0442\u0447\u0438\u043a\u043e\u0432. \u0415\u0441\u0442\u044c \u0441\u0442\u0430\u0442\u044c\u044f Determining if multiple virtual CPUs are causing performance issues (<a href=\"https:\/\/kb.vmware.com\/s\/article\/1005362\" rel=\"noopener noreferrer nofollow\">1005362<\/a>), \u0432\u043c\u0435\u0441\u0442\u0435 \u0441 \u0432\u0441\u044f\u043a\u0438\u043c co stop (<a href=\"https:\/\/www.heroix.com\/blog\/vmware-vcpu-over-allocation\/\" rel=\"noopener noreferrer nofollow\">Maximizing VMware Performance and CPU Utilization<\/a>) \u0438 iowait (Using esxtop to identify storage performance issues for ESX \/ ESXi (multiple versions) (<a href=\"https:\/\/kb.vmware.com\/s\/article\/1008205\" rel=\"noopener noreferrer nofollow\">1008205<\/a>). \u041c\u043e\u0436\u0435\u0442, \u0438 \u043f\u0440\u0430\u0432\u0434\u0430 \u00ab\u0442\u043e\u0440\u043c\u043e\u0437\u0438\u0442\u00bb. \u041d\u043e, \u0441\u043a\u043e\u0440\u0435\u0435 \u0432\u0441\u0435\u0433\u043e, \u043d\u0430\u0434\u043e \u0438\u0434\u0442\u0438 \u0432\u043d\u0443\u0442\u0440\u044c VM \u0438 \u0441\u043c\u043e\u0442\u0440\u0435\u0442\u044c \u043d\u0430 \u0440\u0430\u0431\u043e\u0442\u0430\u044e\u0449\u0435\u0435 \u0432\u043d\u0443\u0442\u0440\u0438 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0435 \u2013 \u0447\u0435\u0433\u043e \u0435\u043c\u0443, \u0445\u043e\u0440\u043e\u043d\u044f\u043a\u0435, \u043d\u0430 \u0441\u0430\u043c\u043e\u043c \u0434\u0435\u043b\u0435 \u043d\u0430\u0434\u043e. <\/p>\n<p><strong>\u041e\u0414\u041d\u041e\u0417\u041d\u0410\u0427\u041d\u041e\u0413\u041e \u041e\u0422\u0412\u0415\u0422\u0410, \u041a\u0410\u041a \u0418\u041c\u0415\u041d\u041d\u041e \u0422\u041e\u0420\u041c\u041e\u0417\u0418\u0422 \u0423 \u0412\u0410\u0421 \u0418 \u041f\u041e\u0427\u0415\u041c\u0423 \u0422\u041e\u0420\u041c\u041e\u0417\u0418\u0422 \u2013 \u041d\u0415\u0422.<\/strong> <\/p>\n<p>\u0422\u043e\u0447\u043d\u0435\u0435, \u043e\u0442\u0432\u0435\u0442 \u0435\u0441\u0442\u044c, \u043d\u043e \u043e\u043d \u0432\u0430\u043c \u043d\u0435 \u043f\u043e\u043d\u0440\u0430\u0432\u0438\u0442\u0441\u044f.<\/p>\n<p><strong>\u0411\u043e\u043d\u0443\u0441<\/strong><\/p>\n<p><a href=\"https:\/\/www.vmware.com\/techpapers\/2023\/vsphere-esxi-vcenter-server-80U2-performance-best-practices.html\" rel=\"noopener noreferrer nofollow\">Performance Best Practices for VMware vSphere 8.0 Update 2 <\/a><br \/><a href=\"https:\/\/www.vmware.com\/techpapers\/2023\/vsphere-esxi-vcenter-server-80U1-performance-best-practices.html\" rel=\"noopener noreferrer nofollow\">Performance Best Practices for VMware vSphere 8.0 Update 1 <\/a><br \/>\u041f\u0440\u0438 \u044d\u0442\u043e\u043c <a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/7.0\/com.vmware.vsphere.vsan-planning.doc\/GUID-7BDE36E1-2F06-4699-8D83-3694A0E638B5.html\" rel=\"noopener noreferrer nofollow\">Best Practices for vSAN Networking<\/a> \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u0435\u0442 \u043f\u043e\u043a\u0430 \u0442\u043e\u043b\u044c\u043a\u043e \u0434\u043b\u044f 7. <br \/><a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/8.0\/vsphere-resource-management\/GUID-BD4A462D-5CDC-4483-968B-1DCF103C4208.html\" rel=\"noopener noreferrer nofollow\">How ESXi NUMA Scheduling Works<\/a><br \/><a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/8.0\/vsphere-resource-management\/GUID-D2921B12-0AD2-452A-ADE6-1A31DF025A26.html\" rel=\"noopener noreferrer nofollow\">VMware NUMA Optimization Algorithms and Settings<\/a><br \/><a href=\"https:\/\/portal.nutanix.com\/page\/documents\/kbs\/details?targetId=kA07V000000LXAwSAO\" rel=\"noopener noreferrer nofollow\">Intermittent CPU ready time due to NUMA action affinity on VMware ESXi<\/a> (\u043d\u0430\u0447\u0438\u043d\u0430\u044f \u0441 \u0447\u0430\u0441\u0442\u0438 \u043f\u0440\u043e LocalityWeightActionAffinity)<br \/>NUMA nodes are heavily load imbalanced causing high contention for some virtual machines (<a href=\"https:\/\/kb.vmware.com\/s\/article\/2097369\" rel=\"noopener noreferrer nofollow\">2097369<\/a>)<\/p>\n<p>\u0418 \u0435\u0449\u0435, \u0435\u0441\u043b\u0438 \u0432\u044b \u0432\u0434\u0440\u0443\u0433 \u0440\u0435\u0448\u0438\u043b\u0438 \u0447\u0442\u043e \u0432\u0441\u0435 \u043f\u043e\u043d\u044f\u043b\u0438, \u0442\u043e \u043c\u043e\u0436\u043d\u043e \u043d\u044b\u0440\u043d\u0443\u0442\u044c \u0432 <a href=\"https:\/\/www.reddit.com\/r\/vmware\/comments\/15s51ey\/vmware_esxi_cpucores_per_socketsockets_change\/\" rel=\"noopener noreferrer nofollow\">\u0440\u0435\u0434\u0434\u0438\u0442<\/a>, \u0438\u043b\u0438 \u0432 \u0441\u0442\u0430\u0442\u044c\u044e Setting the number of cores per CPU in a virtual machine (<a href=\"https:\/\/kb.vmware.com\/s\/article\/1010184\" rel=\"noopener noreferrer nofollow\">1010184<\/a>) \u0438 \u0432 \u0443\u0436\u0435 \u0440\u0430\u043d\u0435\u0435 \u0443\u043f\u043e\u043c\u044f\u043d\u0443\u0442\u0443\u044e \u0441\u0442\u0430\u0442\u044c\u044e <a href=\"https:\/\/blogs.vmware.com\/performance\/2017\/03\/virtual-machine-vcpu-and-vnuma-rightsizing-rules-of-thumb.html\" rel=\"noopener noreferrer nofollow\">Virtual Machine vCPU and vNUMA Rightsizing \u2013 Guideline<\/a>s &#8212; \u0432 \u043a\u043e\u0442\u043e\u0440\u043e\u0439 \u043d\u0435 \u0442\u043e\u043b\u044c\u043a\u043e \u043f\u0440\u043e NUMA, \u043d\u043e \u0438 \u043d\u0430\u0447\u0438\u043d\u0430\u044e\u0442 \u0438\u0434\u0442\u0438 \u0443\u0436\u0435 \u0433\u043b\u0443\u0431\u0436\u0435, \u0432 \u0441\u0430\u043c\u0443 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u0443\u044e \u043c\u0430\u0448\u0438\u043d\u0443 \u0438 \u0442\u043e, \u043a\u0430\u043a \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u0430 \u0432\u043d\u0443\u0442\u0440\u0438 VM \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u0441 \u043f\u0430\u043c\u044f\u0442\u044c\u044e &#8212; <a href=\"https:\/\/learn.microsoft.com\/en-us\/sql\/database-engine\/configure-windows\/soft-numa-sql-server?view=sql-server-ver16&amp;redirectedfrom=MSDN\" rel=\"noopener noreferrer nofollow\">Soft-NUMA (SQL Server)<\/a>.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<p><!----><!----><\/div>\n<p><!----><!----><br \/> \u0441\u0441\u044b\u043b\u043a\u0430 \u043d\u0430 \u043e\u0440\u0438\u0433\u0438\u043d\u0430\u043b \u0441\u0442\u0430\u0442\u044c\u0438 <a href=\"https:\/\/habr.com\/ru\/articles\/799065\/\"> https:\/\/habr.com\/ru\/articles\/799065\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<div><!--[--><!--]--><\/div>\n<div id=\"post-content-body\">\n<div>\n<div class=\"article-formatted-body article-formatted-body article-formatted-body_version-2\">\n<div xmlns=\"http:\/\/www.w3.org\/1999\/xhtml\">\n<p><strong>\u0414\u043b\u044f \u043b\u0438\u0433\u0438 \u043b\u0435\u043d\u0438.<\/strong> \u041a\u0430\u043a\u0430\u044f-\u0442\u043e \u0437\u0430\u0443\u043c\u044c \u043f\u0440\u043e \u0442\u043e, \u0447\u0442\u043e \u043d\u0435 \u043d\u0443\u0436\u043d\u043e,  \u043f\u043e\u0442\u043e\u043c\u0443 \u0447\u0442\u043e \u0432\u0441\u0435 \u0440\u0430\u0432\u043d\u043e \u0443 \u043d\u043e\u0440\u043c\u0430\u043b\u044c\u043d\u044b\u0445 \u043b\u044e\u0434\u0435\u0439 \u0432\u0441\u0435 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u0434\u0430\u0432\u043d\u043e \u0432 \u043e\u0431\u043b\u0430\u043a\u0430\u0445  \u043d\u0430 \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u0430\u0445, \u0438 \u043f\u0440\u0435\u043a\u0440\u0430\u0441\u043d\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u044e\u0442. <\/p>\n<p><a href=\"https:\/\/habr.com\/ru\/articles\/798969\/\" rel=\"noopener noreferrer nofollow\">\u0422\u043e\u0440\u043c\u043e\u0437\u044f\u0449\u0430\u044f \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u044f \u043d\u0430 x86. \u041d\u0435\u0431\u043e\u043b\u044c\u0448\u0430\u044f \u043f\u043e\u043f\u044b\u0442\u043a\u0430 \u0440\u0430\u0437\u043e\u0431\u0440\u0430\u0442\u044c\u0441\u044f. \u0427\u0430\u0441\u0442\u044c 1: \u041e\u0431\u0449\u0438\u0439 \u043e\u0431\u0437\u043e\u0440<\/a><\/p>\n<p><strong>\u0427\u0430\u0441\u0442\u044c 2.<\/strong> \u0427\u0442\u043e \u0438\u0437 \u044d\u0442\u043e\u0433\u043e \u0441\u043b\u0435\u0434\u0443\u0435\u0442, \u0438 \u043a\u0430\u043a \u0443\u0441\u0442\u0440\u043e\u0435\u043d  \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u0432 Broadcom ESXi. \u0422\u0443\u0442 \u043d\u0435 \u0431\u0443\u0434\u0435\u0442 \u043d\u0438\u0447\u0435\u0433\u043e \u043d\u043e\u0432\u043e\u0433\u043e \u0434\u043b\u044f \u0442\u0435\u0445, \u043a\u0442\u043e  \u043e\u0442\u043a\u0440\u044b\u0432\u0430\u043b \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044e \u043f\u0440\u043e \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u0435 \u043c\u043e\u0434\u0435\u043b\u0438 \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u0430 <a href=\"https:\/\/vm-guru.com\/news\/vmware-vsphere-side-channel-aware-scheduler-v2\" rel=\"noopener noreferrer nofollow\">side-channel aware scheduler (SCA) &#8212; SCAv2<\/a>, \u0434\u043e\u0431\u0430\u0432\u0438\u0432 <a href=\"https:\/\/vm-guru.com\/news\/vmware-vsphere-7-u2-amd-performance-optimization-whitepaper\" rel=\"noopener noreferrer nofollow\">Performance Optimizations in VMware vSphere 7.0 U2 CPU Scheduler for AMD EPYC Processors<\/a>\u00a0\u0438 <a href=\"https:\/\/vm-guru.com\/news\/vmware-nvidia-smartnic-dpu-performance\" rel=\"noopener noreferrer nofollow\">Optimizing Networking and Security Performance Using VMware vSphere and NVIDIA BlueField DPU with BWI<\/a>   <\/p>\n<p>\u0415\u0449\u0435 \u0432 <strong>2017<\/strong> \u0433\u043e\u0434\u0443 \u0432\u044b\u0448\u043b\u0430 \u0431\u0435\u0441\u043f\u043b\u0430\u0442\u043d\u0430\u044f \u043a\u043d\u0438\u0433\u0430 <strong>VMware vSphere 6.5 Host Resources Deep Dive<\/strong>, \u0432 \u043a\u043e\u0442\u043e\u0440\u043e\u0439 \u0442\u0435\u043c\u0430 \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0430, \u0438 \u043f\u043e\u0432\u0442\u043e\u0440\u044f\u0442\u044c \u0435\u0435 \u043d\u0435\u0442 \u0441\u043c\u044b\u0441\u043b\u0430. \u041a\u043d\u0438\u0433\u0430 \u043d\u0435 \u043d\u0430 \u0440\u0443\u0441\u0441\u043a\u043e\u043c, \u0435\u0449\u0435 \u0440\u0430\u0437: <strong>\u0431\u0435\u0441\u043f\u043b\u0430\u0442\u043d\u0430\u044f<\/strong>, \u0441\u043a\u0430\u0447\u0430\u0442\u044c \u043c\u043e\u0436\u043d\u043e <a href=\"https:\/\/www.rubrik.com\/resources\/white-papers\/19\/host-resources-deep-dive-ebook\" rel=\"noopener noreferrer nofollow\">\u0442\u0443\u0442<\/a>.<\/p>\n<p>\u0411\u043e\u043b\u0435\u0435 \u043a\u043e\u0440\u043e\u0442\u043a\u0438\u0439 \u0432\u0430\u0440\u0438\u0430\u043d\u0442, \u0431\u0443\u043a\u0432\u0430\u043b\u044c\u043d\u043e \u043d\u0430 3 \u0441\u0442\u0440\u0430\u043d\u0438\u0446\u044b \u0431\u0430\u0437\u043e\u0432\u044b\u0445 \u0442\u0435\u0440\u043c\u0438\u043d\u043e\u0432 \u0438 \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0439, \u043e\u043f\u0438\u0441\u0430\u043d \u0432 \u0441\u0442\u0430\u0442\u044c\u0435 <a href=\"https:\/\/kloudkonnect.wordpress.com\/2019\/08\/23\/understanding-esxi-cpu-scheduling\/\" rel=\"noopener noreferrer nofollow\">Understanding ESXi CPU scheduling<\/a> \u0438\u0437 2019 \u0433\u043e\u0434\u0430.<\/p>\n<p>\u0412 2018 \u0433\u043e\u0434\u0443 \u0432\u044b\u0448\u043b\u0430 ESXi 6.7 (<a href=\"https:\/\/kb.vmware.com\/s\/article\/2143832\" rel=\"noopener noreferrer nofollow\">8169922<\/a>), \u043a\u0441\u0442\u0430\u0442\u0438, \u043d\u0435 \u0437\u0430\u0431\u0443\u0434\u044c\u0442\u0435 \u043f\u043e\u0441\u0442\u0430\u0432\u0438\u0442\u044c \u043d\u0430 \u043d\u0435\u0435, \u0438 \u0432\u0441\u044e \u043b\u0438\u043d\u0435\u0439\u043a\u0443 \u043e\u0442 5.5 \u0434\u043e 8.0.2, <a href=\"https:\/\/www.vmware.com\/security\/advisories\/VMSA-2024-0006.html\" rel=\"noopener noreferrer nofollow\">\u0441\u0432\u0435\u0436\u0430\u0439\u0448\u0438\u0439 \u043f\u0430\u0442\u0447, \u0430 \u0442\u043e \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u0435 \u043f\u043e USB<\/a>, \u043d\u0430 \u043a\u043e\u0442\u043e\u0440\u0443\u044e \u0441\u0435\u0439\u0447\u0430\u0441 , \u0432 \u0440\u0435\u0437\u0443\u043b\u044c\u0442\u0430\u0442\u0435 \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u043e\u0432\u0430\u043d\u0438\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 <u>\u043f\u0440\u043e\u0446\u0435\u0441\u0441\u043e\u0440\u0430<\/u> (Spectre, Meltdown, L1TF, MDS) \u043f\u0440\u0438\u0448\u043b\u043e\u0441\u044c \u043f\u0440\u0438\u043a\u0440\u0443\u0442\u0438\u0442\u044c \u0446\u0435\u043b\u044b\u0445 \u0442\u0440\u0438 \u0432\u0430\u0440\u0438\u0430\u043d\u0442\u0430 \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u0430:<\/p>\n<ul>\n<li>\n<p> \u043f\u043e \u0443\u043c\u043e\u043b\u0447\u0430\u043d\u0438\u044e<\/p>\n<\/li>\n<li>\n<p>Side-Channel Aware Scheduler v1 (SCAv1) \u2013 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u044b\u0439, \u043d\u043e \u00ab\u0447\u0443\u0442\u044c \u0442\u043e\u0440\u043c\u043e\u0437\u0438\u0442\u00bb. <\/p>\n<\/li>\n<\/ul>\n<p> \u0412 6.7 U2 \u0434\u043e\u0431\u0430\u0432\u0438\u043b\u0438 Side-Channel Aware Scheduler v2 (SCAv2) \u2013 \u043c\u0435\u043d\u0435\u0435 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u044b\u0439, \u043f\u043e\u0447\u0442\u0438 \u043d\u0435 \u0442\u043e\u0440\u043c\u043e\u0437\u0438\u0442. <\/p>\n<p>\u0415\u0441\u0442\u044c \u0441\u0442\u0430\u0442\u044c\u044f \u0438\u0437 2019 \u0433\u043e\u0434\u0430 \u00ab\u0447\u0442\u043e \u043a\u043e\u0433\u0434\u0430 \u0432\u044b\u0431\u0438\u0440\u0430\u0442\u044c\u00bb &#8212; <a href=\"https:\/\/blogs.vmware.com\/vsphere\/2019\/05\/which-vsphere-cpu-scheduler-to-choose.html\" rel=\"noopener noreferrer nofollow\">Which vSphere CPU Scheduler to Choose<\/a> \u0438 \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u043e\u0432\u0430\u043b \u043e\u043d\u043b\u0430\u0439\u043d \u043f\u043e\u043c\u043e\u0448\u043d\u0438\u043a &#8212; vSphere 6.7 CPU Scheduler Advisor (\u0441\u043f\u0440\u044f\u0442\u0430\u043b\u0438 \u043a\u0443\u0434\u0430-\u0442\u043e).<br \/>\u0415\u0441\u0442\u044c \u0441\u0442\u0430\u0442\u044c\u044f <a href=\"https:\/\/www.vmware.com\/content\/dam\/digitalmarketing\/vmware\/en\/pdf\/techpaper\/performance\/scheduler-options-vsphere67u2-perf.pdf\" rel=\"noopener noreferrer nofollow\">Performance of vSphere 6.7 Scheduling Options<\/a><\/p>\n<p>\u0412 \u043a\u043e\u0442\u043e\u0440\u043e\u0439 \u043e\u0431\u044a\u044f\u0441\u043d\u044f\u044e\u0442\u0441\u044f \u043e\u0442\u043b\u0438\u0447\u0438\u044f \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u043e\u0432:<\/p>\n<p><strong>\u041f\u0435\u0440\u0435\u0432\u043e\u0434<\/strong><\/p>\n<p>\u0418\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f, \u043f\u0440\u0435\u0434\u043e\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u043d\u044b\u0435 ESXi, \u0432\u043a\u043b\u044e\u0447\u0430\u043b\u0438 \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u0441 \u0443\u0447\u0435\u0442\u043e\u043c \u043f\u043e\u0431\u043e\u0447\u043d\u044b\u0445 \u043a\u0430\u043d\u0430\u043b\u043e\u0432 (SCAv1), \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0441\u043d\u0438\u0436\u0430\u0435\u0442 \u043a\u043e\u043b\u0438\u0447\u0435\u0441\u0442\u0432\u043e \u0432\u0435\u043a\u0442\u043e\u0440\u043e\u0432 \u0430\u0442\u0430\u043a\u0438 \u043a\u043e\u043d\u043a\u0443\u0440\u0438\u0440\u0443\u044e\u0449\u0438\u0445 \u043a\u043e\u043d\u0442\u0435\u043a\u0441\u0442\u043e\u0432 \u0434\u043b\u044f L1TF. \u0415\u0441\u043b\u0438 \u044d\u0442\u043e\u0442 \u0440\u0435\u0436\u0438\u043c \u0432\u043a\u043b\u044e\u0447\u0435\u043d, \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u0431\u0443\u0434\u0435\u0442 \u0440\u0430\u0437\u043c\u0435\u0449\u0430\u0442\u044c \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u044b \u0442\u043e\u043b\u044c\u043a\u043e \u043d\u0430 \u043e\u0434\u043d\u043e\u043c \u043f\u043e\u0442\u043e\u043a\u0435 \u0434\u043b\u044f \u043a\u0430\u0436\u0434\u043e\u0433\u043e \u044f\u0434\u0440\u0430. \u042d\u0442\u043e\u0442 \u0440\u0435\u0436\u0438\u043c \u0432\u043b\u0438\u044f\u0435\u0442 \u043d\u0430 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c \u0433\u043b\u0430\u0432\u043d\u044b\u043c \u043e\u0431\u0440\u0430\u0437\u043e\u043c \u0441 \u0442\u043e\u0447\u043a\u0438 \u0437\u0440\u0435\u043d\u0438\u044f \u043e\u0431\u044a\u0435\u043c\u0430 (\u043c\u0430\u043a\u0441\u0438\u043c\u0430\u043b\u044c\u043d\u043e\u0433\u043e \u0447\u0438\u0441\u043b\u0430 vCPU), \u043f\u043e\u0441\u043a\u043e\u043b\u044c\u043a\u0443 \u0441\u0438\u0441\u0442\u0435\u043c\u0430 \u0431\u043e\u043b\u044c\u0448\u0435 \u043d\u0435 \u043c\u043e\u0436\u0435\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u043e\u0431\u0430 HT (\u043f\u043e\u0442\u043e\u043a\u0430) \u043d\u0430 \u044f\u0434\u0440\u0435. \u0421\u0435\u0440\u0432\u0435\u0440, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0443\u0436\u0435 \u0431\u044b\u043b \u043f\u043e\u043b\u043d\u043e\u0441\u0442\u044c\u044e \u0437\u0430\u0433\u0440\u0443\u0436\u0435\u043d \u0438 \u0440\u0430\u0431\u043e\u0442\u0430\u043b \u043d\u0430 \u043c\u0430\u043a\u0441\u0438\u043c\u0430\u043b\u044c\u043d\u043e\u0439 \u043c\u043e\u0449\u043d\u043e\u0441\u0442\u044c \u0441\u043d\u0438\u0437\u0438\u0442 \u043c\u043e\u0449\u043d\u043e\u0441\u0442\u044c \u043f\u0440\u0438\u043c\u0435\u0440\u043d\u043e \u043d\u0430 30%. \u0421\u0435\u0440\u0432\u0435\u0440, \u0440\u0430\u0431\u043e\u0442\u0430\u0432\u0448\u0438\u0439 \u043d\u0430 75% \u043c\u043e\u0449\u043d\u043e\u0441\u0442\u0438 \u043f\u043e\u043b\u0443\u0447\u0438\u0442 \u0433\u043e\u0440\u0430\u0437\u0434\u043e \u043c\u0435\u043d\u044c\u0448\u0435\u0435 \u043f\u0430\u0434\u0435\u043d\u0438\u0435 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438, \u043d\u043e \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0430 CPU \u0432\u043e\u0437\u0440\u0430\u0441\u0442\u0435\u0442.<\/p>\n<p>\u0412 vSphere 6.7 U2 \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u0441 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u043a\u043e\u0439 \u043f\u043e\u0431\u043e\u0447\u043d\u044b\u0445 \u043a\u0430\u043d\u0430\u043b\u043e\u0432 \u0431\u044b\u043b \u0440\u0430\u0441\u0448\u0438\u0440\u0435\u043d (SCAv2) \u0431\u043b\u0430\u0433\u043e\u0434\u0430\u0440\u044f \u043d\u043e\u0432\u043e\u0439 \u043f\u043e\u043b\u0438\u0442\u0438\u043a\u0435, \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0449\u0435\u0439 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c HT, \u0435\u0441\u043b\u0438 \u043e\u0431\u0430 (HT) \u043f\u043e\u0442\u043e\u043a\u0430 \u0432\u044b\u043f\u043e\u043b\u043d\u044f\u044e\u0442 \u043a\u043e\u043d\u0442\u0435\u043a\u0441\u0442\u044b \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0433\u043e CPU \u0438\u0437 \u043e\u0434\u043d\u043e\u0439 \u0438 \u0442\u043e\u0439 \u0436\u0435 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0439 \u043c\u0430\u0448\u0438\u043d\u044b. \u0414\u043e\u043f\u043e\u043b\u043d\u0438\u0442\u0435\u043b\u044c\u043d\u044b\u0435 \u043a\u0430\u043d\u0430\u043b\u044b L1TF* \u043e\u0433\u0440\u0430\u043d\u0438\u0447\u0435\u043d\u044b, \u0447\u0442\u043e\u0431\u044b \u043d\u0435 \u0440\u0430\u0441\u043a\u0440\u044b\u0432\u0430\u0442\u044c \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u044e \u043c\u0435\u0436\u0434\u0443 VM\/VM \u0438\u043b\u0438 VM\/\u0433\u0438\u043f\u0435\u0440\u0432\u0438\u0437\u043e\u0440.<\/p>\n<p>* L1TF &#8212; <a href=\"https:\/\/www.intel.com\/content\/www\/us\/en\/architecture-and-technology\/l1tf.html\" rel=\"noopener noreferrer nofollow\">Resources and Response to Side Channel L1 Terminal Fault<\/a>, \u0441\u043c\u043e\u0442\u0440\u0435\u0442\u044c \u0433\u0440\u0430\u0444\u0438\u043a \u0432 \u0430\u0431\u0437\u0430\u0446\u0435 For a specific subset of environments where it cannot be guaranteed that all virtualized guest operating systems are trusted.<br \/>(\u0442\u0440\u0435\u0442\u0438\u0439 \u0430\u0431\u0437\u0430\u0446 \u043d\u0435 \u043f\u0435\u0440\u0435\u0432\u0435\u0434\u0435\u043d)<\/p>\n<p><strong>\u041e\u0440\u0438\u0433\u0438\u043d\u0430\u043b<\/strong><\/p>\n<p>The ESXi-provided patches included a Side-Channel Aware Scheduler (SCAv1) that mitigates the concurrent-context attack vector for L1TF. Once this mode is enabled, the scheduler will only schedule processes on one thread for each core. This mode impacts performance mostly from a capacity standpoint because the system is no longer able to use both hyper-threads on a core. A server that was already fully utilized and running at maximum capacity would see a decrease in capacity of up to approximately 30%. A server that was running at 75% of capacity would see a much smaller impact to performance, but CPU use would rise.<\/p>\n<p>In vSphere 6.7 U2, the side-channel aware scheduler has been enhanced (SCAv2) with a new policy to allow hyper-threads to be utilized concurrently if both threads are running vCPU contexts from the same VM. In this way, L1TF side channels are constrained to not expose information across VM\/VM or VM\/hypervisor boundaries<\/p>\n<p>To further illustrate how SCAv1 and SCAv2 work, the diagrams below show generally how different schedulers might schedule vCPUs from VMs on the same core. When there is only one VM in the picture (figure 1), the default placement, SCAv1 and SCAv2 will assign one vCPU on each core. When there are two VMs in the picture (figure 2), the default scheduler might schedule vCPUs from two different VMs on the same core, but SCAv1 and SCAv2 will ensure that only the vCPUs from the same VM will be scheduled on the same core. In the case of SCAv1, only one thread is used. In the case of SCAv2, both threads are used, but this always occurs with the vCPUs from the same VM running on a single core.<\/p>\n<p>\u0414\u0430\u043b\u044c\u0448\u0435 \u0432 \u0441\u0442\u0430\u0442\u044c\u0435 \u0438\u0434\u0443\u0442 \u0433\u0440\u0430\u0444\u0438\u043a\u0438, \u043a\u0430\u043a \u0440\u0430\u0437\u043d\u044b\u0435 \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u0438 \u0432\u043b\u0438\u044f\u044e\u0442 \u043d\u0430 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c \u0440\u0430\u0437\u043d\u044b\u0445 \u0442\u0438\u043f\u043e\u0432 VM. \u0414\u043e 30% \u043f\u043e\u0442\u0435\u0440\u044c (\u043e\u0441\u0442\u0430\u0435\u0442\u0441\u044f 70%), \u0447\u0442\u043e \u043e\u0447\u0435\u043d\u044c \u0442\u0430\u043a \u043d\u0435\u043f\u043b\u043e\u0445\u043e.<\/p>\n<p><strong>\u0427\u0442\u043e \u0435\u0449\u0435 \u043d\u0430\u0434\u043e \u0437\u043d\u0430\u0442\u044c \u043f\u0440\u043e \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u0432 ESXi<\/strong><\/p>\n<p>\u041f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u043e\u043f\u0435\u0440\u0438\u0440\u0443\u0435\u0442 \u00ab\u043c\u0438\u0440\u0430\u043c\u0438\u00bb &#8212;\u00a0 world, \u043f\u0440\u0438 \u044d\u0442\u043e\u043c \u0441\u0443\u0449\u0435\u0441\u0442\u0432\u0443\u044e\u0442 \u043e\u0442\u0434\u0435\u043b\u044c\u043d\u044b\u0435 \u00ab\u043c\u0438\u0440\u044b\u00bb \u0434\u043b\u044f vcpu (vmx-vcpu), vmx-svga, kvm (vmx-ms), \u0441\u0435\u0442\u0438 \u0438 \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u043e\u0432 \u0441\u0430\u043c\u043e\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u044b. <\/p>\n<p>\u041f\u0440\u043e\u0447\u0438\u0442\u0430\u0442\u044c \u043f\u0440\u043e \u044d\u0442\u043e \u043c\u043e\u0436\u043d\u043e, \u043d\u0430\u0447\u0438\u043d\u0430\u044f (\u043a\u0440\u043e\u043c\u0435 \u0432\u044b\u0448\u0435\u043f\u043e\u043c\u044f\u043d\u0443\u0442\u043e\u0433\u043e Deep dive) \u0432 \u0441\u0442\u0430\u0442\u044c\u0435 <a href=\"https:\/\/blogs.virtualmaestro.in\/2020\/06\/24\/vsphere-6-7-u2-later-cpu-scheduler-modes-default-sca-v1-and-sca-v2\/\" rel=\"noopener noreferrer nofollow\">vSphere 6.7 U2 &amp; later CPU Scheduler modes: Default, SCA v1 and SCA v2<\/a> <\/p>\n<p>\u041a\u0430\u0436\u0434\u044b\u0435 2-30 \u043c\u0438\u043b\u043b\u0438\u0441\u0435\u043a\u0443\u043d\u0434 (1\/1000 \u0441\u0435\u043a\u0443\u043d\u0434\u044b) \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u043f\u0440\u043e\u0432\u0435\u0440\u044f\u0435\u0442 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0443 \u043d\u0430 \u0444\u0438\u0437\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u044f\u0434\u0440\u0430\u0445, \u0438 \u0432\u044b\u0434\u0430\u0435\u0442 \u0442\u0430\u0439\u043c\u0441\u043b\u043e\u0442 (\u0441\u043b\u0430\u0439\u0441) \u0434\u043b\u044f \u0438\u0441\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f vCPU > pCPU. \u041c\u043e\u0436\u043d\u043e \u043f\u043e\u043d\u044b\u0440\u044f\u0442\u044c \u0432 NUMA, \u0442\u043e\u0433\u0434\u0430 \u0441\u0442\u0430\u043d\u0435\u0442 \u0435\u0449\u0435 \u0441\u043b\u043e\u0436\u043d\u0435\u0435 \u043f\u043e\u043d\u044f\u0442\u044c, \u0447\u0442\u043e \u0442\u0430\u043c \u0441\u043d\u0438\u0437\u0443 \u043d\u0430 \u0444\u0438\u0437\u0438\u043a\u0435. <\/p>\n<p>\u0417\u0430\u0442\u0435\u043c \u0432 \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a \u0434\u043e\u0431\u0430\u0432\u043b\u044f\u044e\u0442\u0441\u044f \u043f\u0440\u0438\u043e\u0440\u0438\u0442\u0435\u0442\u044b \u0438\u0441\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f, \u043a\u043e\u043c\u0443 \u0434\u0430\u0432\u0430\u0442\u044c \u0431\u043e\u043b\u044c\u0448\u0435 \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u043e\u0440\u0430 (\u0438 \u043f\u0430\u043c\u044f\u0442\u0438), \u043e\u043f\u0438\u0441\u0430\u043d\u043d\u044b\u0435 \u0432 \u0440\u0430\u0437\u0434\u0435\u043b\u0435 <a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/7.0\/com.vmware.vsphere.resmgmt.doc\/GUID-8B88D3D8-E9D9-4C05-A065-B3DE1FFFB401.html\" rel=\"noopener noreferrer nofollow\">Resource Allocation Reservation<\/a>. <\/p>\n<p>\u041f\u0440\u0438 \u044d\u0442\u043e\u043c \u0440\u0435\u0441\u0443\u0440\u0441\u044b \u0441\u0447\u0438\u0442\u0430\u044e\u0442\u0441\u044f \u043d\u0435 \u043f\u043e \u0433\u0438\u0433\u0430\u0433\u0435\u0440\u0446\u0430\u043c, \u0430 \u043f\u043e shares, \u0432 \u0437\u0430\u0432\u0438\u0441\u0438\u043c\u043e\u0441\u0442\u0438 \u043e\u0442 \u043f\u0440\u0438\u043e\u0440\u0438\u0442\u0435\u0442\u0430. <br \/>\u0418 \u0435\u0441\u0442\u044c, \u043a\u0430\u043a \u0441\u043a\u0430\u0437\u0430\u043d\u043e \u0432 \u043f\u0435\u0440\u0432\u043e\u0439 \u0447\u0430\u0441\u0442\u0438, \u043e\u0442\u0434\u0435\u043b\u044c\u043d\u0430\u044f \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 &#8212; <a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/7.0\/com.vmware.vsphere.resmgmt.doc\/GUID-9F4FD589-A73B-454A-A5A5-FED4C0F918C3.html\" rel=\"noopener noreferrer nofollow\">Latency Sensitivity<\/a> \u0441\u043e \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u043c\u0438 \u043e\u0433\u0440\u0430\u043d\u0438\u0447\u0435\u043d\u0438\u044f\u043c\u0438:<\/p>\n<p><strong>\u041e\u0440\u0438\u0433\u0438\u043d\u0430\u043b, \u0442\u0443\u0442 \u0432\u0441\u0435 \u043f\u043e\u043d\u044f\u0442\u043d\u043e \u0438 \u0431\u0435\u0437 \u043f\u0435\u0440\u0435\u0432\u043e\u0434\u0430<\/strong><\/p>\n<p>You can turn on latency sensitivity for each VM at the VM level or at the host level. <br \/>This feature:<br \/>Gives exclusive access to physical resources to avoid resource contention due to sharing<br \/>With exclusive physical CPU (pCPU) access given, each vCPU entirely owns a specific pCPU; no other vCPUs and threads (including VMkernel I\/O threads) are allowed to run on it. This achieves nearly zero ready time and no interruption from other VMkernel threads, improving response time and jitter under CPU contention.<br \/>Bypasses virtualization layers to eliminate the overhead of extra processing<br \/>Once exclusive access to pCPUs is obtained, the feature allows the vCPUs to bypass the VMkernel\u2019s CPU scheduling layer and directly halt in the virtual machine monitor (VMM), since there are no other contexts that need to be scheduled. <u>That way, the cost of running the CPU scheduler code and the cost of switching between the VMkernel and VMM are avoided<\/u>, leading to much faster vCPU halt\/wake-up operations.<br \/>Tunes virtualization layers to reduce the overhead<br \/>When the VMXNET3 paravirtualized device is used for VNICs in the VM, VNIC interrupt coalescing and LRO support for the VNICs are automatically disabled to reduce response time and jitter.<br \/>Although these and other features are disabled automatically when setting latency sensitivity to high, <u>we recommend disabling each of these features independently<\/u> to avoid any cascading effects when a single parameter is altered when tuning your virtual machines.<\/p>\n<p><strong>\u041f\u043e \u044d\u0442\u043e\u0439 (Latency Sensitivity) \u0442\u0435\u043c\u0435 \u043c\u043e\u0436\u043d\u043e \u043f\u043e\u0447\u0438\u0442\u0430\u0442\u044c \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0435\u0435: <br \/><\/strong><a href=\"https:\/\/communities.vmware.com\/t5\/VMware-vSphere-Discussions\/Shares-explanation\/td-p\/2222956\" rel=\"noopener noreferrer nofollow\">Shares explanation <\/a><br \/><a href=\"https:\/\/www.vmware.com\/content\/dam\/digitalmarketing\/vmware\/en\/pdf\/techpaper\/latency-sensitive-perf-vsphere55-white-paper.pdf\" rel=\"noopener noreferrer nofollow\">Deploying Extremely Latency-Sensitive Applications in VMware vSphere 5.5<\/a> (\u043e\u0447\u0435\u043d\u044c \u0441\u0442\u0430\u0440\u044b\u0439, \u043d\u043e \u0432\u0441\u0435 \u0435\u0449\u0435 \u043f\u043e\u043b\u0435\u0437\u043d\u044b\u0439 \u0442\u0435\u043a\u0441\u0442)<br \/><a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/6.7\/vsphere-esxi-vcenter-server-672-resource-management-guide.pdf\" rel=\"noopener noreferrer nofollow\">vSphere Resource Management Update 2 14 AUG 2020 VMware vSphere 6.7<\/a><br \/><a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/7.0\/vsphere-esxi-vcenter-server-703-resource-management-guide.pdf\" rel=\"noopener noreferrer nofollow\">vSphere Resource Management Update 3 VMware vSphere 7.0 <\/a><br \/><a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/7.0\/vsphere-esxi-vcenter-server-703-host-management-guide.pdf\" rel=\"noopener noreferrer nofollow\">vCenter Server and Host Management Update 3 Modified on 08 JAN 2024 VMware vSphere 7.0<\/a><\/p>\n<p>\u041d\u0430\u0434\u043e \u0437\u0430\u043c\u0435\u0442\u0438\u0442\u044c, \u0447\u0442\u043e \u0435\u0449\u0435 \u0432 \u043a\u043e\u043d\u0446\u0435 2022 \u0432\u044b\u0448\u043b\u0430 ESXi 8.0 GA \u2013 \u044d\u0442\u043e \u0434\u0430\u0436\u0435 \u043e\u0444\u0438\u0446\u0438\u0430\u043b\u044c\u043d\u043e<a href=\"https:\/\/blogs.vmware.com\/vsphere\/2022\/10\/new-release-model-for-vsphere-8.html\" rel=\"noopener noreferrer nofollow\"> Public beta, \u0441\u043e\u0433\u043b\u0430\u0441\u043d\u043e New Release Model for vSphere 8<\/a>, \u0447\u0442\u043e \u0438 \u043f\u043e\u043a\u0430\u0437\u0430\u043d\u043e \u0432 \u0441\u043f\u0438\u0441\u043a\u0435 \u0437\u0430\u043a\u0440\u044b\u0442\u044b\u0445 \u0431\u0430\u0433\u043e\u0432 \u0434\u043b\u044f ESXi 8.0 Update 2 (<em>\u042d\u0442\u043e\u0442 \u0430\u0431\u0437\u0430\u0446 \u043f\u043e\u0441\u0432\u044f\u0449\u0435\u043d The \u043e\u0434\u043d\u043e\u043c\u0443 \u043c\u043e\u0435\u043c\u0443 \u0437\u043d\u0430\u043a\u043e\u043c\u043e\u043c\u0443. \u041f\u043e\u043a\u043e\u0439\u043d\u043e\u043c\u0443<\/em>), \u0430 \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044e \u043e\u0431\u043d\u043e\u0432\u043b\u044f\u044e\u0442 \u0434\u043b\u044f 7. <\/p>\n<p>\u041a\u0440\u043e\u043c\u0435 \u043f\u0440\u043e\u0447\u0435\u0433\u043e, \u00a0\u043d\u0430 \u0441\u043a\u043e\u0440\u043e\u0441\u0442\u044c \u0440\u0430\u0431\u043e\u0442\u044b \u0432\u043b\u0438\u044f\u0435\u0442 \u0432\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u0435 \\ \u0432\u044b\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u0435 CPU Hot add , \u043f\u043e\u0434\u0440\u043e\u0431\u043d\u0435\u0439\u0448\u0435 \u043e\u043f\u0438\u0441\u0430\u043d\u043d\u043e\u0435 \u0432 2017 &#8212; <a href=\"https:\/\/blogs.vmware.com\/performance\/2017\/03\/virtual-machine-vcpu-and-vnuma-rightsizing-rules-of-thumb.html\" rel=\"noopener noreferrer nofollow\">Virtual Machine vCPU and vNUMA Rightsizing \u2013 Guidelines<\/a>, <br \/>\u0440\u0430\u0437\u0434\u0435\u043b <a href=\"https:\/\/frankdenneman.nl\/2017\/04\/14\/impact-cpu-hot-add-numa-scheduling\/\" rel=\"noopener noreferrer nofollow\">Impact of CPU Hot Add on NUMA schedulin<\/a>g  \u0438 \u0432 \u0441\u0442\u0430\u0442\u044c\u0435 <a href=\"https:\/\/blogs.vmware.com\/performance\/2019\/12\/cpu-hot-add-performance-vsphere67.html\" rel=\"noopener noreferrer nofollow\">CPU Hot Add Performance in vSphere 6.7<\/a> <\/p>\n<p>\u041f\u0435\u0440\u0435\u0432\u043e\u0434 \u0441 \u0434\u043e\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f\u043c\u0438 \u0438\u0437 2019: <a href=\"https:\/\/vm-guru.com\/news\/vmware-vsphere-vcpu-hot-add-performance\" rel=\"noopener noreferrer nofollow\">\u041f\u043e\u0447\u0435\u043c\u0443 CPU Hot Add \u0432\u044b\u043a\u043b\u044e\u0447\u0435\u043d\u043e \u043f\u043e \u0443\u043c\u043e\u043b\u0447\u0430\u043d\u0438\u044e \u0432 VMware vSphere, \u0438 \u043a\u0430\u043a \u044d\u0442\u043e \u0432\u043b\u0438\u044f\u0435\u0442 \u043d\u0430 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c?<\/a><\/p>\n<p>\u041c\u043e\u0436\u043d\u043e VM \u043f\u0440\u0438\u0431\u0438\u0442\u044c \u0433\u0432\u043e\u0437\u0434\u044f\u043c\u0438 \u043f\u0440\u044f\u043c\u043e \u043a \u044f\u0434\u0440\u0443 &#8212; <a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/7.0\/com.vmware.vsphere.resmgmt.doc\/GUID-F40F901D-C1A7-43E2-90AF-E6F98C960E4B.html\" rel=\"noopener noreferrer nofollow\">Assign a Virtual Machine to a Specific Processor<\/a><\/p>\n<p><strong>\u0427\u0442\u043e \u0432\u0441\u0435 \u044d\u0442\u043e \u0437\u043d\u0430\u0447\u0438\u0442 \u00ab\u0432 \u0446\u0435\u043b\u043e\u043c\u00bb<\/strong><\/p>\n<p>\u041f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0438 \u0432 ESXi by Broadcom \u0437\u0430\u0432\u0438\u0441\u0438\u0442 \u043e\u0442 \u0434\u0435\u0441\u044f\u0442\u043a\u043e\u0432 \u0444\u0430\u043a\u0442\u043e\u0440\u043e\u0432, \u0438\u0437 \u043a\u043e\u0442\u043e\u0440\u044b\u0445 \u043e\u0441\u043d\u043e\u0432\u043d\u044b\u043c\u0438 \u044f\u0432\u043b\u044f\u044e\u0442\u0441\u044f:<\/p>\n<p>\u041f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u044b\u0435 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0438 \u044d\u043d\u0435\u0440\u0433\u043e\u0441\u0431\u0435\u0440\u0435\u0436\u0435\u043d\u0438\u044f \u0432 BIOS \u0438 \u0441\u0430\u043c\u043e\u0439 ESXi &#8212; <a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/8.0\/vsphere-resource-management\/GUID-4D1A6F4A-8C99-47C1-A8E6-EF3865603F5B.html\" rel=\"noopener noreferrer nofollow\">Host Power Management Policies in ESXi<\/a><br \/>\u0423\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430 \u0430\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0439 \u0434\u043b\u044f BIOS \/ CPU \u0438 \u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u044b\u0439 \u0432\u044b\u0431\u043e\u0440 \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u0430<br \/>\u0423\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430 \u0430\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0439 \u0434\u043b\u044f ESXi by Broadcom<br \/>\u0412\u044b\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u0435 CPU \\ RAM hot add, \u0435\u0441\u043b\u0438 \u0437\u0430\u0447\u0435\u043c-\u0442\u043e \u0432\u043a\u043b\u044e\u0447\u0438\u043b\u0438<br \/>\u0423\u043c\u0435\u043d\u044c\u0448\u0435\u043d\u0438\u0435 (\u0434\u0430, \u0438\u043c\u0435\u043d\u043d\u043e \u0443\u043c\u0435\u043d\u044c\u0448\u0435\u043d\u0438\u0435) \u0447\u0438\u0441\u043b\u0430 vCPU \u0434\u043e \u00ab\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043d\u0443\u0436\u043d\u043e\u00bb, \u0430 \u043d\u0435 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430 \u00ab\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043f\u043e\u043f\u0440\u043e\u0441\u0438\u043b\u0438\u00bb. \u0411\u043e\u043b\u044c\u0448\u0435 \u0432 \u0434\u0430\u043d\u043d\u043e\u043c \u0441\u043b\u0443\u0447\u0430\u0435 \u2013 \u041d\u0415 \u0437\u043d\u0430\u0447\u0438\u0442 \u043b\u0443\u0447\u0448\u0435. <br \/>\u041d\u0430\u0431\u043b\u044e\u0434\u0435\u043d\u0438\u0435 \u0437\u0430 esxtop <a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/8.0\/vsphere-monitoring-performance\/GUID-D89E8267-C74A-496F-B58E-19672CAB5A53.html\" rel=\"noopener noreferrer nofollow\">\u0440\u0430\u0437<\/a>, \u0434\u0432\u0430 Using esxtop to identify storage performance issues for ESX \/ ESXi (multiple versions) (<a href=\"https:\/\/kb.vmware.com\/s\/article\/1008205\" rel=\"noopener noreferrer nofollow\">1008205<\/a>) \u00a0<a href=\"https:\/\/www.virten.net\/vmware\/esxtop\/\" rel=\"noopener noreferrer nofollow\">\u0442\u0440\u0438 <\/a><a href=\"https:\/\/www.virtualizationhowto.com\/2023\/07\/esxtop-commands-the-ultimate-guide\/\" rel=\"noopener noreferrer nofollow\">\u0447\u0435\u0442\u044b\u0440\u0435 <\/a><a href=\"https:\/\/www.yellow-bricks.com\/2020\/04\/02\/esxtop-in-vsphere-7\/\" rel=\"noopener noreferrer nofollow\">\u043f\u044f\u0442\u044c <\/a><a href=\"https:\/\/www.yellow-bricks.com\/esxtop\/\" rel=\"noopener noreferrer nofollow\">\u0448\u0435\u0441\u0442\u044c <\/a><\/p>\n<p>\u0418 \u043f\u043e\u0438\u0441\u043a\u0430\u0442\u044c \u0440\u043e\u043b\u0438\u043a (\u043a\u0443\u0434\u0430 \u0442\u043e \u0441\u043f\u0440\u044f\u0442\u0430\u043b\u0438) \u0441 60 Minutes of Non-Uniform Memory Architecture [HBI2278BE] by Frank Denneman \u0438\u0437 2019 \u0433\u043e\u0434\u0430 <\/p>\n<p><strong>\u041d\u0430 \u0441\u043b\u0430\u0434\u043a\u043e\u0435 \u2013 \u0437\u0430\u043d\u044b\u0440\u0438\u0432\u0430\u0442\u044c \u0432 NUMA &#8212; The 2016 NUMA Deep Dive Series \u043e\u0442 \u0432\u0441\u0435 \u0442\u043e\u0433\u043e \u0436\u0435 \u0430\u0432\u0442\u043e\u0440\u0430: Frank Denneman<\/strong><\/p>\n<p><a href=\"https:\/\/frankdenneman.nl\/2016\/07\/06\/introduction-2016-numa-deep-dive-series\/\" rel=\"noopener noreferrer nofollow\">Part 0: Introduction NUMA Deep Dive Series <\/a><br \/><a href=\"http:\/\/frankdenneman.nl\/2016\/07\/07\/numa-deep-dive-part-1-uma-numa\/\" rel=\"noopener noreferrer nofollow\">Part 1: From UMA to NUMA <\/a><br \/><a href=\"http:\/\/frankdenneman.nl\/2016\/07\/08\/numa-deep-dive-part-2-system-architecture\/\" rel=\"noopener noreferrer nofollow\">Part 2: System Architecture <\/a><br \/><a href=\"http:\/\/frankdenneman.nl\/2016\/07\/11\/numa-deep-dive-part-3-cache-coherency\/\" rel=\"noopener noreferrer nofollow\">Part 3: Cache Coherency\u00a0 <\/a><br \/><a href=\"http:\/\/frankdenneman.nl\/2016\/08\/22\/numa-deep-dive-part-5-esxi-vmkernel-numa-constructs\/\" rel=\"noopener noreferrer nofollow\">Part 4: Local Memory Optimization <\/a><br \/><a href=\"https:\/\/frankdenneman.nl\/2016\/08\/22\/numa-deep-dive-part-5-esxi-vmkernel-numa-constructs\/\" rel=\"noopener noreferrer nofollow\">Part 5: ESXi VMkernel NUMA Constructs <\/a><br \/>Part 6: NUMA Initial Placement and Load Balancing Operations (\u043d\u0435 \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d\u0430)<br \/>Part 7: From NUMA to UMA (\u043d\u0435 \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d\u0430)<\/p>\n<p><strong>\u0418\u0442\u043e\u0433\u043e<\/strong><\/p>\n<p>\u0412\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u044f \u0431\u0435\u0437 \u043d\u0430\u0441\u0442\u0440\u043e\u0435\u043a \u043e\u043f\u0442\u0438\u043c\u0438\u0437\u0430\u0446\u0438\u0438, \u0438\u0437 \u043a\u043e\u0440\u043e\u0431\u043a\u0438 \u043f\u043e \u0443\u043c\u043e\u043b\u0447\u0430\u043d\u0438\u044e, \u0431\u0435\u0437\u0443\u0441\u043b\u043e\u0432\u043d\u043e, \u0442\u043e\u0440\u043c\u043e\u0437\u0438\u0442, \u043f\u043e \u0441\u0440\u0430\u0432\u043d\u0435\u043d\u0438\u044e \u0441 \u0447\u0438\u0441\u0442\u044b\u043c bare metal, \u043d\u0430 \u043a\u043e\u0442\u043e\u0440\u043e\u043c \u0437\u0430\u043f\u0443\u0449\u0435\u043d\u0430 1 (\u043e\u0434\u043d\u0430)<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-370363","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts\/370363","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=370363"}],"version-history":[{"count":0,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts\/370363\/revisions"}],"wp:attachment":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=370363"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=370363"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=370363"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}