{"id":34335,"date":"2019-10-31T21:57:43","date_gmt":"2019-10-31T18:57:43","guid":{"rendered":"https:\/\/prohoster.info\/blog\/analiz-proizvoditelnosti-virtualnoj-mashiny-v-vmware-vsphere-chast-1-cpu\/"},"modified":"2019-10-31T21:57:43","modified_gmt":"2019-10-31T18:57:43","slug":"analiz-proizvoditelnosti-virtualnoj-mashiny-v-vmware-vsphere-chast-1-cpu","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/analiz-proizvoditelnosti-virtualnoj-mashiny-v-vmware-vsphere-chast-1-cpu","title":{"rendered":"Analiza e performanc\u00ebs s\u00eb makin\u00ebs virtuale n\u00eb VMware vSphere. Pjesa 1: CPU","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb makin\u00ebs virtuale n\u00eb VMware vSphere. Pjesa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/0c077a1754c2e32c1f339999ceacf03a.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nN\u00ebse menaxhoni infrastruktur\u00ebn virtuale t\u00eb bazuar n\u00eb VMware vSphere (ose ndonj\u00eb stack tjet\u00ebr teknologjik), me siguri d\u00ebgjoni shpesh ankesat nga p\u00ebrdoruesit: \"Makin\u00eb virtuale po punon ngadal\u00eb!\". N\u00eb k\u00ebt\u00eb cik\u00ebl artikujsh do t\u00eb analizoj metrikat e performanc\u00ebs dhe do t\u00eb shpjegoj se \u00e7far\u00eb dhe pse po \"ngadal\u00ebson\" dhe si t\u00eb b\u00ebj q\u00eb t\u00eb mos \"ngadal\u00ebsoj\u00eb\".<\/p>\n<p>Do t\u00eb shqyrtoj aspekte t\u00eb ndryshme t\u00eb performanc\u00ebs s\u00eb makinave virtuale:<\/p>\n<ul>\n<li>CPU,<\/li>\n<li>RAM,<\/li>\n<li>DISK,<\/li>\n<li>RRJETI.<\/li>\n<\/ul>\n<p>\nDo t\u00eb filloj me CPU.<\/p>\n<p>P\u00ebr t\u00eb analizuar performanc\u00ebn do t\u00eb na duhen:<\/p>\n<ul>\n<li><b>vCenter Performance Counters<\/b> \u2013 numra performanc\u00ebs, grafik\u00ebt e t\u00eb cil\u00ebve mund t\u00eb shihen p\u00ebrmes vSphere Client. Informacioni p\u00ebr k\u00ebta numra \u00ebsht\u00eb i aksesuesh\u00ebm n\u00eb \u00e7do version t\u00eb klientit (klienti \u201ci r\u00ebnd\u00eb\u201d n\u00eb C#, klienti web n\u00eb Flex dhe klienti web n\u00eb HTML5). N\u00eb k\u00ebto artikuj do t\u00eb p\u00ebrdorim screenshot-e nga klienti n\u00eb C# vet\u00ebm sepse duken m\u00eb mir\u00eb n\u00eb miniatur\u00eb :)<\/li>\n<li><b>ESXTOP<\/b> \u2013 nj\u00eb mjet q\u00eb ekzekutohet nga komandat e linj\u00ebs s\u00eb komand\u00ebs n\u00eb ESXi. Me ndihm\u00ebn e tij, mund t\u00eb merrni vlerat e numrave t\u00eb performanc\u00ebs n\u00eb koh\u00eb reale ose t'i eksportoni ato p\u00ebr nj\u00eb periudh\u00eb t\u00eb caktuar n\u00eb nj\u00eb skedar .csv p\u00ebr analiz\u00eb t\u00eb m\u00ebtejshme. M\u00eb pas do t\u00eb flas m\u00eb tehsi p\u00ebr k\u00ebt\u00eb mjet dhe do t\u00eb jap disa lidhje t\u00eb dobishme p\u00ebr dokumentacionin dhe artikujt n\u00eb tem\u00eb.<\/li>\n<\/ul>\n<p>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Pak teori<\/h3>\n<p>\n<img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb makin\u00ebs virtuale n\u00eb VMware vSphere. Pjesa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/bc415aace7653c45850d26b7104483c9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nN\u00eb ESXi, \u00e7do vCPU (n\u00eb thelb nj\u00eb b\u00ebrtham\u00eb virtuale) mbetet n\u00ebn p\u00ebrgjegj\u00ebsin\u00eb e nj\u00eb procesi t\u00eb ve\u00e7ant\u00eb \u2013 bot n\u00eb terminologjin\u00eb e VMware. Ekzistojn\u00eb gjithashtu procese t\u00eb tjera sh\u00ebrbimi, por nga k\u00ebndv\u00ebshtrimi i analiz\u00ebs s\u00eb performanc\u00ebs s\u00eb VM-ve, ato jan\u00eb m\u00eb pak interesante.<\/p>\n<p>Nj\u00eb proces n\u00eb ESXi mund t\u00eb ndodhet n\u00eb nj\u00ebrin nga kat\u00ebr gjendjet:<\/p>\n<ul>\n<li><b>Ekzekuto<\/b> \u2013 procesi kryen ndonj\u00eb pun\u00eb t\u00eb dobishme.<\/li>\n<li><b>Wait<\/b> \u2013 procesi nuk kryen asnj\u00eb pun\u00eb (inaktiv) ose pret hyrje\/ dalje.<\/li>\n<li><b>Costop<\/b> \u2013 \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0435, \u043a\u043e\u0442\u043e\u0440\u043e\u0435 \u0432\u043e\u0437\u043d\u0438\u043a\u0430\u0435\u0442 \u0432 \u043c\u043d\u043e\u0433\u043e\u044f\u0434\u0435\u0440\u043d\u044b\u0445 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0430\u0448\u0438\u043d\u0430\u0445. \u041e\u043d\u043e \u0432\u043e\u0437\u043d\u0438\u043a\u0430\u0435\u0442, \u043a\u043e\u0433\u0434\u0430 \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a CPU \u0433\u0438\u043f\u0435\u0440\u0432\u0438\u0437\u043e\u0440\u0430 (ESXi CPU Scheduler) \u043d\u0435 \u043c\u043e\u0436\u0435\u0442 \u0437\u0430\u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0430\u0442\u044c \u043e\u0434\u043d\u043e\u0432\u0440\u0435\u043c\u0435\u043d\u043d\u043e\u0435 \u0438\u0441\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u0435 \u043d\u0430 \u0444\u0438\u0437\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u044f\u0434\u0440\u0430\u0445 \u0441\u0435\u0440\u0432\u0435\u0440\u0430 \u0432\u0441\u0435\u0445 \u0430\u043a\u0442\u0438\u0432\u043d\u044b\u0445 \u044f\u0434\u0435\u0440 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0439 \u043c\u0430\u0448\u0438\u043d\u044b. \u0412 \u0444\u0438\u0437\u0438\u0447\u0435\u0441\u043a\u043e\u043c \u043c\u0438\u0440\u0435 \u0432\u0441\u0435 \u044f\u0434\u0440\u0430 \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u043e\u0440\u0430 \u0440\u0430\u0431\u043e\u0442\u0430\u044e\u0442 \u043f\u0430\u0440\u0430\u043b\u043b\u0435\u043b\u044c\u043d\u043e, \u0433\u043e\u0441\u0442\u0435\u0432\u0430\u044f \u041e\u0421 \u0432\u043d\u0443\u0442\u0440\u0438 \u0412\u041c \u0440\u0430\u0441\u0441\u0447\u0438\u0442\u044b\u0432\u0430\u0435\u0442 \u043d\u0430 \u0430\u043d\u0430\u043b\u043e\u0433\u0438\u0447\u043d\u043e\u0435 \u043f\u043e\u0432\u0435\u0434\u0435\u043d\u0438\u0435, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 \u0433\u0438\u043f\u0435\u0440\u0432\u0438\u0437\u043e\u0440\u0443 \u043f\u0440\u0438\u0445\u043e\u0434\u0438\u0442\u0441\u044f \u0437\u0430\u043c\u0435\u0434\u043b\u044f\u0442\u044c \u044f\u0434\u0440\u0430 \u0412\u041c, \u0443 \u043a\u043e\u0442\u043e\u0440\u044b\u0445 \u0435\u0441\u0442\u044c \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c \u0437\u0430\u043a\u043e\u043d\u0447\u0438\u0442\u044c \u0442\u0430\u043a\u0442 \u0431\u044b\u0441\u0442\u0440\u0435\u0435. \u0412 \u0441\u043e\u0432\u0440\u0435\u043c\u0435\u043d\u043d\u044b\u0445 \u0432\u0435\u0440\u0441\u0438\u044f\u0445 ESXi \u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0449\u0438\u043a CPU \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u043d\u0430\u0437\u044b\u0432\u0430\u0435\u0442\u0441\u044f relaxed co-scheduling: \u0433\u0438\u043f\u0435\u0440\u0432\u0438\u0437\u043e\u0440 \u0441\u0447\u0438\u0442\u0430\u0435\u0442 \u0440\u0430\u0437\u0440\u044b\u0432 \u043c\u0435\u0436\u0434\u0443 \u0441\u0430\u043c\u044b\u043c \u00ab\u0431\u044b\u0441\u0442\u0440\u044b\u043c\u00bb \u0438 \u0441\u0430\u043c\u044b\u043c \u201c\u043c\u0435\u0434\u043b\u0435\u043d\u043d\u044b\u043c&#187; \u044f\u0434\u0440\u043e\u043c \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0439 \u043c\u0430\u0448\u0438\u043d\u044b (skew). \u0415\u0441\u043b\u0438 \u0440\u0430\u0437\u0440\u044b\u0432 \u043f\u0440\u0435\u0432\u044b\u0448\u0430\u0435\u0442 \u043e\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u043d\u044b\u0439 \u043f\u043e\u0440\u043e\u0433, \u00ab\u0431\u044b\u0441\u0442\u0440\u043e\u0435\u00bb \u044f\u0434\u0440\u043e \u043f\u0435\u0440\u0435\u0445\u043e\u0434\u0438\u0442 \u0432 \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0435 costop. \u0415\u0441\u043b\u0438 \u044f\u0434\u0440\u0430 \u0412\u041c \u043f\u0440\u043e\u0432\u043e\u0434\u044f\u0442 \u043c\u043d\u043e\u0433\u043e \u0432\u0440\u0435\u043c\u0435\u043d\u0438 \u0432 \u044d\u0442\u043e\u043c \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0438, \u044d\u0442\u043e \u043c\u043e\u0436\u0435\u0442 \u0432\u044b\u0437\u0432\u0430\u0442\u044c \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u0441 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c\u044e.<\/li>\n<li><b>Gati<\/b> \u2013 procesi kalon n\u00eb k\u00ebt\u00eb gjendje kur hipervizori nuk ka mund\u00ebsi t\u00eb alokoj\u00eb burime p\u00ebr ekzekutimin e tij. Vlerat e larta t\u00eb gatishm\u00ebris\u00eb mund t\u00eb shkaktojn\u00eb probleme me performanc\u00ebn e VM-s\u00eb.<\/li>\n<\/ul>\n<p><\/p>\n<h3>Numrat kryesor\u00eb t\u00eb performanc\u00ebs s\u00eb CPU-s\u00eb s\u00eb makin\u00ebs virtuale<\/h3>\n<p>\n<b>P\u00ebrdorimi i CPU, %.<\/b> Tregon p\u00ebrqindjen e p\u00ebrdorimit t\u00eb CPU-s\u00eb gjat\u00eb nj\u00eb periudhe t\u00eb caktuar.<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb makin\u00ebs virtuale n\u00eb VMware vSphere. Pjesa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/7a5da7dcd45329c3aae8e394c5d35a30.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Si ta analizoni?<\/b> N\u00ebse VM-ja stabilisht p\u00ebrdor CPU n\u00eb 90% ose ka pika deri n\u00eb 100%, at\u00ebher\u00eb kemi probleme. Problemet mund t\u00eb shfaqen jo vet\u00ebm n\u00eb \"pun\u00ebn e ngadal\u00ebsuar\" t\u00eb aplikacionit brenda VM-s\u00eb, por edhe n\u00eb papages\u00ebn e VM-s\u00eb n\u00eb rrjet. N\u00ebse sistemi i monitorimit tregon se VM-ja ndonj\u00ebher\u00eb d\u00ebshton, kushtojini v\u00ebmendje pikave n\u00eb grafikun e P\u00ebrdorimit t\u00eb CPU-s\u00eb.<\/p>\n<p>Ekziston nj\u00eb Alarm standard q\u00eb tregon ngarkes\u00ebn e CPU-s\u00eb s\u00eb makin\u00ebs virtuale:<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb makin\u00ebs virtuale n\u00eb VMware vSphere. Pjesa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/9bfd9bb5b43b9b02e8bbfac307d6c9f9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>\u00c7far\u00eb t\u00eb b\u00ebjm\u00eb?<\/b> N\u00ebse VM-ja vazhdimisht kalon P\u00ebrdorimin e CPU-s\u00eb, mund t\u00eb mendoni p\u00ebr rritjen e numrit t\u00eb vCPU-ve (fatkeq\u00ebsisht, kjo nuk ndihmon gjithmon\u00eb) ose transf\u00e9rin e VM-s\u00eb n\u00eb nj\u00eb server me procesor\u00eb m\u00eb t\u00eb fuqish\u00ebm.<\/p>\n<h3>P\u00ebrdorimi i CPU-s\u00eb n\u00eb MHz<\/h3>\n<p>\nN\u00eb grafik\u00ebt e P\u00ebrdorimit n\u00eb vCenter n\u00eb %, mund t\u00eb shihni vet\u00ebm p\u00ebrgjith\u00ebsisht p\u00ebr makin\u00ebn virtuale, nuk ka grafik\u00eb p\u00ebr b\u00ebrthamat e ve\u00e7anta (n\u00eb Esxtop ka vlera n\u00eb % p\u00ebr b\u00ebrthamat). P\u00ebr \u00e7do b\u00ebrtham\u00eb mund t\u00eb shihni P\u00ebrdorimin n\u00eb MHz.<\/p>\n<p><b>Si ta analizoni?<\/b> Ndonj\u00ebher\u00eb ndodh q\u00eb aplikacioni nuk \u00ebsht\u00eb optimizuar p\u00ebr arkitektur\u00ebn me shum\u00eb b\u00ebrthama: p\u00ebrdor vet\u00ebm nj\u00eb b\u00ebrtham\u00eb me 100%, nd\u00ebrsa b\u00ebrthamat e tjera q\u00ebndrojn\u00eb t\u00eb papunuara. P\u00ebr shembull, me cil\u00ebsimet e paracaktuar, MS SQL aktivizon procesin vet\u00ebm n\u00eb nj\u00eb b\u00ebrtham\u00eb. Si rezultat, kopjimi i rezerv\u00ebs ngadal\u00ebsohet jo p\u00ebr shkak t\u00eb shpejt\u00ebsis\u00eb s\u00eb ngadalt\u00eb t\u00eb disqeve (pik\u00ebrisht p\u00ebr k\u00ebt\u00eb p\u00ebrdoruesi ankohej fillimisht), por p\u00ebr shkak t\u00eb ngarkes\u00ebs s\u00eb procesorit. Problemi u zgjidh duke ndryshuar parametrat: kopjimi i rezerv\u00ebs filloi t\u00eb ekzekutohet paralelisht n\u00eb skedar\u00eb t\u00eb shumt\u00eb (p\u00ebrkat\u00ebsisht, n\u00eb procese t\u00eb shumta).<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb makin\u00ebs virtuale n\u00eb VMware vSphere. Pjesa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/d1bce5fe5ef89a69c31a6a8f043d5d24.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Shembulli i ngarkes\u00ebs s\u00eb pabarabart\u00eb t\u00eb b\u00ebrthamave.<\/i><\/p>\n<p>Gjithashtu ndodh nj\u00eb situat\u00eb (si\u00e7 tregohet n\u00eb grafikun m\u00eb sip\u00ebr) kur b\u00ebrthamat jan\u00eb t\u00eb ngarkuara n\u00eb m\u00ebnyr\u00eb t\u00eb pabarabart\u00eb dhe disa prej tyre kan\u00eb pika n\u00eb 100%. Ashtu si kur ngarkohet vet\u00ebm nj\u00eb b\u00ebrtham\u00eb, alarmi p\u00ebr P\u00ebrdorimin e CPU-s\u00eb nuk do t\u00eb aktivizohet (ai \u00ebsht\u00eb p\u00ebr t\u00eb gjith\u00eb VM-n\u00eb), por do t\u00eb ket\u00eb probleme me performanc\u00ebn.<\/p>\n<p><b>\u00c7far\u00eb t\u00eb b\u00ebjm\u00eb? <\/b>N\u00ebse softi n\u00eb makin\u00ebn virtuale ngarkon b\u00ebrthamat n\u00eb m\u00ebnyr\u00eb t\u00eb pap\u00ebrshtatshme (p\u00ebrdor vet\u00ebm nj\u00eb b\u00ebrtham\u00eb ose nj\u00eb pjes\u00eb t\u00eb b\u00ebrthamave), nuk ka kuptim t\u00eb rrisim numrin e tyre. N\u00eb k\u00ebt\u00eb rast, \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb transferoni VM-n\u00eb n\u00eb nj\u00eb server me procesor\u00eb m\u00eb t\u00eb fuqish\u00ebm.<\/p>\n<p>Gjithashtu, mund t\u00eb provoni t\u00eb kontrolloni cil\u00ebsimet e konsumit t\u00eb energjis\u00eb n\u00eb BIOS t\u00eb serverit. Shum\u00eb administratori aktivizojn\u00eb n\u00eb BIOS modin High Performance dhe k\u00ebshtu \u00e7aktivizojn\u00eb teknologjit\u00eb e ruajtjes s\u00eb energjis\u00eb C-states dhe P-states. N\u00eb procesor\u00ebt modern\u00eb Intel p\u00ebrdoret teknologjia Turbo Boost, e cila rrit frekuenc\u00ebn e b\u00ebrthamave t\u00eb ve\u00e7anta t\u00eb procesorit duke p\u00ebrdorur b\u00ebrtha t\u00eb tjera. Por ajo funksionon vet\u00ebm kur aktivizohen teknologjit\u00eb e ruajtjes s\u00eb energjis\u00eb. N\u00ebse i \u00e7aktivizojm\u00eb, procesori nuk mund t\u00eb ul\u00eb konsumimin e energjis\u00eb s\u00eb b\u00ebrthamave q\u00eb nuk jan\u00eb t\u00eb ngarkuara. <\/p>\n<p>VMware rekomandon q\u00eb t\u00eb mos \u00e7aktivizoni teknologjit\u00eb e ruajtjes s\u00eb energjis\u00eb n\u00eb servera, por t\u00eb zgjidhni m\u00ebnyra q\u00eb maksimizojn\u00eb kontrollin e konsumit t\u00eb energjis\u00eb nga hipervizori. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, n\u00eb cil\u00ebsimet e konsumit t\u00eb energjis\u00eb t\u00eb hipervizorit, duhet t\u00eb zgjidhni High Performance. <\/p>\n<p>N\u00ebse n\u00eb infrastruktur\u00ebn tuaj disa VM (ose b\u00ebrthama VM) k\u00ebrkojn\u00eb frekuenc\u00eb t\u00eb rritur t\u00eb CPU-s\u00eb, cil\u00ebsimi i duhur i konsumit t\u00eb energjis\u00eb mund t\u00eb p\u00ebrmir\u00ebsoj\u00eb ndjesh\u00ebm performanc\u00ebn e tyre.<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb makin\u00ebs virtuale n\u00eb VMware vSphere. Pjesa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/59aec2b77fa87e413d90371a11388629.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>CPU Ready (Gati) <\/h3>\n<p>\nN\u00ebse b\u00ebrthama e VM (vCPU) \u00ebsht\u00eb n\u00eb gjendjen Ready, ajo nuk po kryen pun\u00eb t\u00eb dobishme. Kjo gjendje ndodh kur hipervizori nuk gjen nj\u00eb b\u00ebrtham\u00eb fizike t\u00eb lir\u00eb p\u00ebr t\u00eb caktuar procesin vCPU t\u00eb makin\u00ebs virtuale.<\/p>\n<p><b>Si ta analizoni?<\/b> N\u00eb p\u00ebrgjith\u00ebsi, n\u00ebse b\u00ebrthamat e makin\u00ebs virtuale jan\u00eb n\u00eb gjendjen Ready m\u00eb shum\u00eb se 10% t\u00eb koh\u00ebs, do t\u00eb vini re probleme me performanc\u00ebn. Thjesht, m\u00eb shum\u00eb se 10% t\u00eb koh\u00ebs VM po pret p\u00ebr qasje n\u00eb burimet fizike.<\/p>\n<p>N\u00eb vCenter mund t\u00eb shikoni 2 numra q\u00eb lidhen me CPU Ready:<\/p>\n<ul>\n<li>Gatishm\u00ebria,<\/li>\n<li>Gati.<\/li>\n<\/ul>\n<p>\nVlerat e t\u00eb dy numrave mund t\u00eb shikohen si p\u00ebr t\u00eb gjith\u00eb VM-n\u00eb, ashtu edhe p\u00ebr b\u00ebrthama t\u00eb ve\u00e7anta.<br \/>\nGatishm\u00ebria tregon vler\u00ebn n\u00eb procent, por vet\u00ebm n\u00eb koh\u00eb reale (t\u00eb dh\u00ebnat p\u00ebr or\u00ebn e fundit, intervali i matjeve 20 sekonda). Ky num\u00ebr \u00ebsht\u00eb m\u00eb i mir\u00eb p\u00ebr t\u00eb k\u00ebrkuar probleme \"n\u00eb vend\".<\/p>\n<p>Vlerat e numrit Ready mund t\u00eb shikohen gjithashtu n\u00eb perspektiv\u00ebn historike. Kjo \u00ebsht\u00eb e dobishme p\u00ebr t\u00eb identifikuar tendenca dhe p\u00ebr nj\u00eb analiz\u00eb m\u00eb t\u00eb thell\u00eb t\u00eb problemit. P\u00ebr shembull, n\u00ebse nj\u00eb makin\u00ebs virtuale fillojn\u00eb problemet e performanc\u00ebs n\u00eb nj\u00eb koh\u00eb t\u00eb caktuar, mund t\u00eb p\u00ebrputheni intervalet e vler\u00ebs s\u00eb rritur t\u00eb CPU Ready me ngarkes\u00ebn totale n\u00eb server, ku kjo VM funksionon, dhe t\u00eb merrni masa p\u00ebr t\u00eb ulur ngarkes\u00ebn (n\u00ebse DRS nuk ka p\u00ebrfunduar pun\u00ebn).<\/p>\n<p>Gati n\u00eb krahasim me Gatishm\u00ebrin\u00eb tregohet jo n\u00eb p\u00ebrqindje, por n\u00eb milisekonda. Ky \u00ebsht\u00eb nj\u00eb num\u00ebr i tipit Summation, q\u00eb do t\u00eb thot\u00eb se tregon sa koh\u00eb gjat\u00eb periudh\u00ebs s\u00eb matjes, b\u00ebrthama VM ka qen\u00eb n\u00eb gjendjen Ready. T\u00eb p\u00ebrkthen k\u00ebt\u00eb vler\u00eb n\u00eb p\u00ebrqindje mund t\u00eb b\u00ebhet me nj\u00eb formul\u00eb t\u00eb thjesht\u00eb:<\/p>\n<p>(vlera e p\u00ebrmbledhjes CPU ready \/ (intervali default i azhurnimit t\u00eb grafikut n\u00eb sekonda * 1000)) * 100 = CPU ready %<\/p>\n<p>P\u00ebr shembull, p\u00ebr VM-n\u00eb n\u00eb grafikun m\u00eb posht\u00eb, vlera maksimale e Ready p\u00ebr gjith\u00eb makin\u00ebn virtuale do t\u00eb rezultoj\u00eb si n\u00eb vijon: <\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb makin\u00ebs virtuale n\u00eb VMware vSphere. Pjesa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/3e2df8bca55b572502d88b838cbc306e.jpg\" style=\"display:block;margin: 0 auto;\" \/> <\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb makin\u00ebs virtuale n\u00eb VMware vSphere. Pjesa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/f0371c9cd655c1e4785e90debde61dc8.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKur llogarisni vler\u00ebn e Ready n\u00eb p\u00ebrqindje, duhet t\u00eb keni parasysh dy pika:<\/p>\n<ul>\n<li>Vlera e Ready p\u00ebr gjith\u00eb VM-n\u00eb \u00ebsht\u00eb shuma e Ready p\u00ebr b\u00ebrthamat.<\/li>\n<li>Intervali i matjes. P\u00ebr koh\u00eb reale \u2013 \u00ebsht\u00eb 20 sekonda, dhe p\u00ebr shembuj, n\u00eb grafikat ditore \u2013 \u00ebsht\u00eb 300 sekonda.<\/li>\n<\/ul>\n<p>\nN\u00eb nj\u00eb trajtim aktiv t\u00eb problemeve, k\u00ebto pika t\u00eb thjeshta mund t\u00eb injorohen leht\u00eb dhe t\u00eb humbas\u00ebsh koh\u00eb t\u00eb \u00e7muar duke zgjidhur probleme q\u00eb nuk ekzistojn\u00eb. <\/p>\n<p>Llogarisim Ready t\u00eb bazuar n\u00eb t\u00eb dh\u00ebnat nga grafiku m\u00eb posht\u00eb. (324474\/(20*1000))*100 = 1622% p\u00ebr gjith\u00eb VM-n\u00eb. N\u00ebse shikoni p\u00ebr b\u00ebrthamat, rezultati do t\u00eb jet\u00eb m\u00eb pak alarmant: 1622\/64 = 25% p\u00ebr b\u00ebrtham\u00eb. N\u00eb k\u00ebt\u00eb rast, \u00ebsht\u00eb e leht\u00eb p\u00ebr t'u kuptuar se ka di\u00e7ka t\u00eb \u00e7uditshme: vlera e Ready \u00ebsht\u00eb e pamundur. Por n\u00ebse flasim p\u00ebr 10\u201320% p\u00ebr gjith\u00eb VM-n\u00eb me disa b\u00ebrthama, vlera p\u00ebr secil\u00ebn b\u00ebrtham\u00eb mund t\u00eb jet\u00eb brenda norm\u00ebs.<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb makin\u00ebs virtuale n\u00eb VMware vSphere. Pjesa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/703ab2b1f1fab8bda10aad781c2cef78.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>\u00c7far\u00eb t\u00eb b\u00ebjm\u00eb? <\/b>Nj\u00eb vler\u00eb e lart\u00eb e Ready tregon se serveri i mungon burimet e procesorit p\u00ebr t\u00eb punuar normalisht me makinat virtuale. N\u00eb k\u00ebt\u00eb situat\u00eb, nuk ka alternativ\u00eb tjet\u00ebr ve\u00e7se t\u00eb ulen kapacitetet e procesorit (vCPU:pCPU). Sigurisht, kjo mund t\u00eb arrihet duke reduktuar parametrat e VM-ve ekzistuese ose duke migruar disa VM n\u00eb servere t\u00eb tjera.<\/p>\n<h3>Co-stop<\/h3>\n<p>\n<b>Si ta analizoni?<\/b> Ky num\u00ebr gjithashtu ka tipin Summation dhe kalohet n\u00eb p\u00ebrqindje n\u00eb m\u00ebnyr\u00eb t\u00eb ngjashme me Ready:<\/p>\n<p>(vlera e p\u00ebrmbledhjes CPU co-stop \/ (intervali default i azhurnimit t\u00eb grafikut n\u00eb sekonda * 1000)) * 100 = CPU co-stop %<\/p>\n<p>K\u00ebtu duhet gjithashtu t\u00eb keni parasysh numrin e b\u00ebrthamave n\u00eb VM dhe intervalin e matjes.<br \/>\nN\u00eb gjendjen co-stop b\u00ebrthama nuk kryen pun\u00eb t\u00eb dobishme. Me p\u00ebrzgjedhjen e duhur t\u00eb madh\u00ebsis\u00eb s\u00eb VM dhe ngarkes\u00ebn normale n\u00eb server, numri i co-stop duhet t\u00eb jet\u00eb af\u00ebr zero.<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb makin\u00ebs virtuale n\u00eb VMware vSphere. Pjesa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/e226afbf91155c2d5d3fdc4571e7383a.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>N\u00eb k\u00ebt\u00eb rast, ngarkesa \u00ebsht\u00eb duksh\u00ebm e pazakont\u00eb :)<\/i><\/p>\n<p><b>\u00c7far\u00eb t\u00eb b\u00ebjm\u00eb?<\/b> N\u00ebse disa VM funksionojn\u00eb n\u00eb nj\u00eb hipervizor me nj\u00eb num\u00ebr t\u00eb madh b\u00ebrthamash dhe ka ekzistenc\u00eb t\u00eb CPU-s\u00eb, numri co-stop mund t\u00eb rritet, \u00e7ka do t\u00eb sjell\u00eb probleme me performanc\u00ebn e k\u00ebtyre VM-ve. <\/p>\n<p>Gjithashtu, co-stop do t\u00eb rritet n\u00ebse b\u00ebrthamat aktive t\u00eb nj\u00eb VM p\u00ebrdorin fije n\u00eb nj\u00eb b\u00ebrtham\u00eb fizike t\u00eb serverit me hyper-threading t\u00eb aktivizuar. Kjo situat\u00eb mund t\u00eb ndodh\u00eb, p\u00ebr shembull, n\u00ebse nj\u00eb VM ka m\u00eb shum\u00eb b\u00ebrthama se sa ka fizikisht serveri ku ajo funksionon, ose n\u00ebse p\u00ebr VM \u00ebsht\u00eb aktivizuar konfigurimi 'preferHT'. M\u00eb shum\u00eb rreth k\u00ebtij konfigurimi mund t\u00eb lexoni <noindex><a rel=\"nofollow\" href=\"https:\/\/blogs.vmware.com\/vsphere\/2014\/03\/perferht-use-2.html\">k\u00ebtu<\/a><\/noindex>. <\/p>\n<p>P\u00ebr t\u00eb evituar problemet me performanc\u00ebn e VM-ve p\u00ebr shkak t\u00eb co-stop t\u00eb lart\u00eb, zgjidhni madh\u00ebsin\u00eb e VM-s\u00eb sipas rekomandimeve t\u00eb prodhuesit t\u00eb softuerit q\u00eb funksionon n\u00eb k\u00ebt\u00eb VM dhe mund\u00ebsive t\u00eb serverit fizik ku punon VM-ja. <\/p>\n<p>Mos shtoni b\u00ebrthama p\u00ebr rezerv\u00eb, kjo mund t\u00eb shkaktoj\u00eb probleme me performanc\u00ebn jo vet\u00ebm t\u00eb VM-s\u00eb vet\u00eb, por edhe t\u00eb fqinj\u00ebve t\u00eb saj n\u00eb server.<\/p>\n<h3>Metri t\u00eb tjera t\u00eb dobishme t\u00eb CPU-s\u00eb<\/h3>\n<p>\n<b>Ekzekuto<\/b> \u2013 sa koh\u00eb (ms) n\u00eb periudh\u00ebn e matjes vCPU ishte n\u00eb gjendje RUN, pra realisht po kryente pun\u00eb t\u00eb dobishme.<\/p>\n<p><b>Idle<\/b> \u2013 sa koh\u00eb (ms) n\u00eb periudh\u00ebn e matjes vCPU ishte n\u00eb gjendje idle. Vlera t\u00eb larta t\u00eb Idle nuk jan\u00eb nj\u00eb problem, thjesht vCPU nuk kishte 'p\u00ebr t\u00eb b\u00ebr\u00eb'.<\/p>\n<p><b>Wait<\/b> \u2013 sa koh\u00eb (ms) n\u00eb periudh\u00ebn e matjes vCPU ishte n\u00eb gjendje Wait. Duke qen\u00eb se n\u00eb k\u00ebt\u00eb num\u00ebr p\u00ebrfshihet IDLE, vlera t\u00eb larta t\u00eb Wait gjithashtu nuk tregojn\u00eb p\u00ebr ndonj\u00eb problem. Po k\u00ebshtu, n\u00ebse me Wait t\u00eb lart\u00eb IDLE \u00ebsht\u00eb i ul\u00ebt, at\u00ebher\u00eb VM-ja kishte pritje p\u00ebr p\u00ebrfundimin e operacioneve t\u00eb input\/output, dhe kjo, nga ana tjet\u00ebr, mund t\u00eb tregoj\u00eb p\u00ebr nj\u00eb problem me performanc\u00ebn e hard diskut ose ndonj\u00eb pajisjeje virtuale t\u00eb VM-s\u00eb.<\/p>\n<p><b>Max i kufizuar<\/b> \u2013 sa koh\u00eb (ms) n\u00eb periudh\u00ebn e matjes vCPU ishte n\u00eb gjendje Ready p\u00ebr shkak t\u00eb nj\u00eb limiti t\u00eb vendosur p\u00ebr burimet. N\u00ebse performanca \u00ebsht\u00eb papritur e ul\u00ebt, \u00ebsht\u00eb e dobishme t\u00eb kontrolloni vler\u00ebn e k\u00ebtij numri dhe limitin e CPU-s\u00eb n\u00eb konfigurimin e VM-s\u00eb. VM-ja realisht mund t\u00eb ket\u00eb limite t\u00eb vendosura q\u00eb nuk i dini. P\u00ebr shembull, kjo ndodh kur VM-ja \u00ebsht\u00eb klonuar nga nj\u00eb model q\u00eb kishte nj\u00eb limit p\u00ebr CPU.<\/p>\n<p><b>Pritja Swap<\/b> \u2013 sa koh\u00eb gjat\u00eb periudh\u00ebs s\u00eb matjes vCPU ka pritur nj\u00eb operacion me VMkernel Swap. N\u00ebse vlerat e k\u00ebtij numri jan\u00eb mbi zero, at\u00ebher\u00eb VM-ja sigurisht ka probleme me performanc\u00ebn. M\u00eb shum\u00eb rreth SWAP do t\u00eb diskutojm\u00eb n\u00eb artikullin mbi metrikat e memorjes.<\/p>\n<h3>ESXTOP<\/h3>\n<p>\nN\u00ebse metrikat e performanc\u00ebs n\u00eb vCenter jan\u00eb t\u00eb mira p\u00ebr analizimin e t\u00eb dh\u00ebnave historike, analiza e menj\u00ebhershme e problemeve \u00ebsht\u00eb m\u00eb e mir\u00eb n\u00eb ESXTOP. K\u00ebtu, t\u00eb gjitha vlerat jan\u00eb t\u00eb paraqitura n\u00eb form\u00eb t\u00eb gatshme (nuk ka nevoj\u00eb t\u00eb p\u00ebrkthehet ndNothing), dhe periudha minimale e matjes \u00ebsht\u00eb 2 sekonda.<br \/>\nEkrani ESXTOP p\u00ebr CPU aktivizohet duke shtypur \u00e7el\u00ebsin 'c' dhe duket si m\u00eb posht\u00eb:<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb makin\u00ebs virtuale n\u00eb VMware vSphere. Pjesa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/f4f3611bc383007bdbaa0948001923c4.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nP\u00ebr leht\u00ebsi, mund t\u00eb lini vet\u00ebm proceset e makinave virtuale, duke shtypur Shift-V.<br \/>\nP\u00ebr t\u00eb par\u00eb metrikat p\u00ebr b\u00ebrthamat e ve\u00e7anta t\u00eb VM-s\u00eb, shtypni 'e' dhe vendosni GID-n\u00eb e VM-s\u00eb q\u00eb ju intereson (30919 n\u00eb ekranin m\u00eb posht\u00eb):<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb makin\u00ebs virtuale n\u00eb VMware vSphere. Pjesa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/5f2c0226cee6e4e43128537bd4da843f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nShkurtimisht do t\u00eb kaloj n\u00ebp\u00ebr kolona q\u00eb jan\u00eb t\u00eb paraqitura si standard. Kolona t\u00eb tjera mund t\u00eb shtohen duke shtypur 'f'.<\/p>\n<p><b>NWLD (Numri i Bot\u00ebve)<\/b> \u2013 numri i proceseve n\u00eb grup. P\u00ebr t\u00eb zgjeruar grupin dhe par\u00eb metrikat p\u00ebr \u00e7do proces (p\u00ebr shembull, p\u00ebr \u00e7do b\u00ebrtham\u00eb t\u00eb VM-s\u00eb shum\u00ebb\u00ebrthamore), shtypni 'e'. N\u00ebse n\u00eb grup ka m\u00eb shum\u00eb se nj\u00eb proces, at\u00ebher\u00eb vlerat e metrikave p\u00ebr grupin jan\u00eb t\u00eb barabarta me shum\u00ebn e metrikave p\u00ebr proceset e ve\u00e7anta.<\/p>\n<p><b>%USED<\/b> \u2013 sa cikle CPU serveri p\u00ebrdor procesi ose grupi i proceseve.<\/p>\n<p><b>%RUN<\/b> \u2013 sa koh\u00eb gjat\u00eb periudh\u00ebs s\u00eb matjes procesi ishte n\u00eb gjendje RUN, pra kryente pun\u00eb t\u00eb dobishme. Dallohet nga %USED sepse nuk merr parasysh hyper-threading, scaling t\u00eb frekuenc\u00ebs dhe koh\u00ebn e kaluar p\u00ebr detyra sistemore (%SYS).<\/p>\n<p><b>%SYS<\/b> \u2013 koha e kaluar p\u00ebr detyra sistemore, p\u00ebr shembull: trajtimi i nd\u00ebrprerjeve, input\/output, pun\u00eb rrjeti etj. Vlera mund t\u00eb jet\u00eb e lart\u00eb n\u00ebse VM-ja ka shum\u00eb input\/output.<\/p>\n<p><b>%OVRLP<\/b> \u2013 sa koh\u00eb b\u00ebrthama fizike, mbi t\u00eb cil\u00ebn ekzekutohet procesi i VM-s\u00eb, ka kaluar n\u00eb detyra t\u00eb proceseve t\u00eb tjera.<\/p>\n<p>K\u00ebto metrika jan\u00eb t\u00eb lidhura me nj\u00ebra-tjetr\u00ebn n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb:<\/p>\n<p>%USED = %RUN + %SYS \u2014 %OVRLP.<\/p>\n<p>Zakonisht, metrika %USED \u00ebsht\u00eb m\u00eb informatike.<\/p>\n<p><b>%WAIT<\/b> \u2013 sa koh\u00eb gjat\u00eb periudh\u00ebs s\u00eb matjes procesi ishte n\u00eb gjendje Wait. P\u00ebrfshin IDLE.<\/p>\n<p><b>%IDLE<\/b> \u2013 sa koh\u00eb gjat\u00eb periudh\u00ebs s\u00eb matjes procesi ishte n\u00eb gjendje IDLE.<\/p>\n<p><b>%SWPWT<\/b> \u2013 sa koh\u00eb gjat\u00eb periudh\u00ebs s\u00eb matjes vCPU ka pritur nj\u00eb operacion me VMkernel Swap.<\/p>\n<p><b>%VMWAIT<\/b> \u2013 sa koh\u00eb gjat\u00eb periudh\u00ebs s\u00eb matjes vCPU ishte n\u00eb gjendje pritje p\u00ebr nj\u00eb ngjarje (zakonisht input\/output). Nj\u00eb num\u00ebr t\u00eb till\u00eb nuk ka n\u00eb vCenter. Vlera t\u00eb larta tregojn\u00eb p\u00ebr probleme me input\/output n\u00eb VM.<\/p>\n<p>%WAIT = %VMWAIT + %IDLE + %SWPWT.<\/p>\n<p>N\u00ebse VM-ja nuk p\u00ebrdor VMkernel Swap, \u00ebsht\u00eb e arsyeshme t\u00eb shikoni %VMWAIT p\u00ebr analizimin e problemeve me performanc\u00ebn, pasi kjo metrik\u00eb nuk merr parasysh koh\u00ebn kur VM-ja nuk ka b\u00ebr\u00eb asgj\u00eb (%IDLE).<\/p>\n<p><b>%RDY<\/b> \u2013 sa koh\u00eb gjat\u00eb periudh\u00ebs s\u00eb matjes procesi ka qen\u00eb n\u00eb gjendje Ready.<\/p>\n<p><b>%CSTP<\/b> \u2013 sa koh\u00eb gjat\u00eb periudh\u00ebs s\u00eb matjes procesi ka qen\u00eb n\u00eb gjendje costop.<\/p>\n<p><b>%MLMTD<\/b> \u2013 sa koh\u00eb gjat\u00eb periudh\u00ebs s\u00eb matjes vCPU ka qen\u00eb n\u00eb gjendje Ready p\u00ebr shkak t\u00eb limitit t\u00eb vendosur mbi burimet.<\/p>\n<p>%WAIT + %RDY + %CSTP + %RUN = 100% \u2013 si VM-ja \u00ebsht\u00eb gjithmon\u00eb n\u00eb nj\u00ebr\u00ebn prej k\u00ebtyre kat\u00ebr gjendjeve.<\/p>\n<h3>CPU n\u00eb hipervizor<\/h3>\n<p>\nN\u00eb vCenter ka gjithashtu numra t\u00eb performanc\u00ebs CPU p\u00ebr hipervizorin, por ata nuk paraqesin asgj\u00eb interesante \u2013 \u00ebsht\u00eb thjesht shuma e numrave p\u00ebr t\u00eb gjitha VM-t\u00eb n\u00eb server.<br \/>\nM\u00eb leht\u00eb \u00ebsht\u00eb t\u00eb shikoni gjendjen e CPU-s\u00eb n\u00eb server n\u00eb sked\u00ebn Summary:<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb makin\u00ebs virtuale n\u00eb VMware vSphere. Pjesa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/15b6b9a6da136d892fbaf7f80fc206c1.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nP\u00ebr serverin, ashtu si p\u00ebr nj\u00eb makin\u00eb virtuale, ka Alarm standard:<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb makin\u00ebs virtuale n\u00eb VMware vSphere. Pjesa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/c3ae19ce3acd55cfff40d71437ee3a08.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nMe ngarkes\u00eb t\u00eb lart\u00eb n\u00eb CPU-n\u00eb e serverit, VM-t\u00eb q\u00eb punojn\u00eb mbi t\u00eb fillojn\u00eb t\u00eb ken\u00eb probleme me performanc\u00ebn.<\/p>\n<p>N\u00eb ESXTOP t\u00eb dh\u00ebnat p\u00ebr ngarkes\u00ebn e CPU-s\u00eb s\u00eb serverit paraqiten n\u00eb pjes\u00ebn e sip\u00ebrme t\u00eb ekranit. P\u00ebrve\u00e7 ngarkes\u00ebs standarde t\u00eb CPU-s\u00eb, e cila \u00ebsht\u00eb pak informuese p\u00ebr hipervizor\u00ebt, ka edhe tri metrika t\u00eb tjera:<\/p>\n<p><b>CORE UTIL(%)<\/b> \u2013 ngarkesa e b\u00ebrtham\u00ebs s\u00eb serverit fizik. Ky num\u00ebr tregon se sa koh\u00eb gjat\u00eb periudh\u00ebs s\u00eb matjes b\u00ebrthama ka kryer pun\u00eb.<\/p>\n<p><b>PCPU UTIL(%)<\/b> \u2013 n\u00ebse hyper-threading \u00ebsht\u00eb i aktivizuar, at\u00ebher\u00eb \u00e7do b\u00ebrthame fizike ka dy rrjedha (PCPU). Kjo metrik\u00eb tregon se sa koh\u00eb \u00e7do rrjedh\u00eb ka kryer pun\u00eb.<\/p>\n<p><b>PCPU USED(%)<\/b> \u2013 \u00ebsht\u00eb e nj\u00ebjta si PCPU UTIL(%), por merr parasysh zmadhimin e frekuenc\u00ebs (ose uljen e frekuenc\u00ebs s\u00eb b\u00ebrtham\u00ebs p\u00ebr q\u00ebllime kursimi energjie, ose rritjen e frekuenc\u00ebs s\u00eb b\u00ebrtham\u00ebs p\u00ebrmes teknologjis\u00eb Turbo Boost) dhe hyper-threading.<\/p>\n<p>PCPU_USED% = PCPU_UTIL% * frekuenc\u00ebn efektive t\u00eb b\u00ebrtham\u00ebs \/ frekuenc\u00ebn nominale t\u00eb b\u00ebrtham\u00ebs.<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb makin\u00ebs virtuale n\u00eb VMware vSphere. Pjesa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/dd8562ea91bee55bbf630358df26c217.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>N\u00eb k\u00ebt\u00eb ekran p\u00ebr disa b\u00ebrthama p\u00ebr shkak t\u00eb funksionimit t\u00eb Turbo Boost-it, vlera e USED \u00ebsht\u00eb m\u00eb e madhe se 100%, pasi frekuenca e b\u00ebrtham\u00ebs \u00ebsht\u00eb m\u00eb e lart\u00eb se ajo nominale.<\/i><\/p>\n<p>Nj\u00eb fjal\u00eb p\u00ebr m\u00ebnyr\u00ebn sesi merret n\u00eb konsiderat\u00eb hyper-threading. N\u00ebse proceset ekzekutohen 100% t\u00eb koh\u00ebs n\u00eb t\u00eb dy rrjedhat e b\u00ebrtham\u00ebs fizike t\u00eb serverit, nd\u00ebrkoh\u00eb q\u00eb b\u00ebrthama punon me frekuenc\u00ebn nominale, at\u00ebher\u00eb:<\/p>\n<ul>\n<li>CORE UTIL p\u00ebr b\u00ebrtham\u00ebn do t\u00eb jet\u00eb 100%,<\/li>\n<li>PCPU UTIL p\u00ebr t\u00eb dy rrjedhat do t\u00eb jet\u00eb 100%,<\/li>\n<li>PCPU USED p\u00ebr t\u00eb dy rrjedhat do t\u00eb jet\u00eb 50%.<\/li>\n<\/ul>\n<p>\nN\u00ebse t\u00eb dy rrjedhat nuk kan\u00eb punuar 100% t\u00eb koh\u00ebs gjat\u00eb periudh\u00ebs s\u00eb matjes, at\u00ebher\u00eb n\u00eb ato periudha kur rrjedhat kan\u00eb punuar paralel, PCPU USED p\u00ebr b\u00ebrthamat ndahen p\u00ebr gjysm\u00ebn.<\/p>\n<p>N\u00eb ESXTOP ka gjithashtu nj\u00eb ekran me parametrat e konsumit t\u00eb energjis\u00eb s\u00eb CPU-s\u00eb s\u00eb serverit. K\u00ebtu mund t\u00eb shikoni n\u00ebse serveri p\u00ebrdor teknologjit\u00eb e kursimit t\u00eb energjis\u00eb: C-states dhe P-states. Aktivizohet me \u00e7el\u00ebsin \"p\":<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb makin\u00ebs virtuale n\u00eb VMware vSphere. Pjesa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/531bf847b99f86bec0bd90e005919c79.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Problemet standarde t\u00eb performanc\u00ebs s\u00eb CPU-s\u00eb<\/h3>\n<p>\nN\u00eb fund do t\u00eb kaloj n\u00eb arsyet tipike q\u00eb shkaktojn\u00eb probleme me performanc\u00ebn e CPU-s\u00eb s\u00eb VM-ve dhe do t\u00eb jap disa k\u00ebshilla t\u00eb shkurtra p\u00ebr zgjidhjen e tyre:<\/p>\n<p><b>Nuk ka mjaft frekuenc\u00eb b\u00ebrthame.<\/b> N\u00ebse nuk ka mund\u00ebsi p\u00ebr t\u00eb kaluar VM-n\u00eb n\u00eb b\u00ebrthama m\u00eb t\u00eb fuqishme, mund t\u00eb provoni t\u00eb ndryshoni cil\u00ebsimet e konsumit t\u00eb energjis\u00eb, q\u00eb Turbo Boost t\u00eb punoj\u00eb m\u00eb efektivisht.<\/p>\n<p><b>Kurimi i gabuar i VM-s\u00eb (shum\u00eb b\u00ebrthama \/ shum\u00eb pak b\u00ebrthama).<\/b> N\u00ebse vendosni shum\u00eb pak b\u00ebrthama, do t\u00eb ket\u00eb ngarkes\u00eb t\u00eb lart\u00eb n\u00eb CPU-n\u00eb e VM-s\u00eb. N\u00ebse vendosni shum\u00eb, do t\u00eb hasni nj\u00eb co-stop t\u00eb lart\u00eb.<\/p>\n<p><b>P\u00ebrshkrimi i madh p\u00ebr CPU-n\u00eb n\u00eb server.<\/b> N\u00ebse VM-ja ka nj\u00eb Ready t\u00eb lart\u00eb, ulni p\u00ebrshkrimin p\u00ebr CPU-n\u00eb.<\/p>\n<p><b>Kurimi i gabuar NUMA n\u00eb VM-t\u00eb m\u00eb t\u00eb m\u00ebdha.<\/b> Topologjia NUMA q\u00eb sheh VM-ja (vNUMA) duhet t\u00eb p\u00ebrputhet me topologjin\u00eb NUMA t\u00eb serverit (pNUMA). P\u00ebr diagnostikimin dhe mund\u00ebsit\u00eb e zgjidhjes s\u00eb k\u00ebsaj problemi, \u00ebsht\u00eb shkruar, p\u00ebr shembull, n\u00eb librin <noindex><a rel=\"nofollow\" href=\"https:\/\/pages.rubrik.com\/host-resources-deep-dive_request.html\">\u00abVMware vSphere 6.5 Host Resources Deep Dive\u00bb<\/a><\/noindex>. N\u00ebse nuk d\u00ebshironi t\u00eb thelloheni dhe nuk keni kufizime licencash p\u00ebr OS-n\u00eb e instaluar n\u00eb VM, krijoni shum\u00eb socket-e virtuale n\u00eb VM me nj\u00eb b\u00ebrtham\u00eb. Nuk do t\u00eb humbni shum\u00eb \ud83d\ude42<\/p>\n<p>K\u00ebtu e kam mbyllur p\u00ebr CPU-n\u00eb. B\u00ebni pyetje. N\u00eb pjes\u00ebn tjet\u00ebr do t\u00eb flas p\u00ebr memorjen operative.<\/p>\n<p><b class=\"spoiler_title\">Linqe t\u00eb dobishme<\/b><noindex><a rel=\"nofollow\" href=\"http:\/\/virtual-red-dot.info\/vm-cpu-counters-vsphere\/\">http:\/\/virtual-red-dot.info\/vm-cpu-counters-vsphere\/<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/kb\/1017926\">https:\/\/kb.vmware.com\/kb\/1017926<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2012\/07\/17\/why-is-wait-so-high\/\">http:\/\/www.yellow-bricks.com\/2012\/07\/17\/why-is-wait-so-high\/<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/communities.vmware.com\/docs\/DOC-9279\">https:\/\/communities.vmware.com\/docs\/DOC-9279<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/www.vmware.com\/content\/dam\/digitalmarketing\/vmware\/en\/pdf\/techpaper\/performance\/whats-new-vsphere65-perf.pdf\">https:\/\/www.vmware.com\/content\/dam\/digitalmarketing\/vmware\/en\/pdf\/techpaper\/performance\/whats-new-vsphere65-perf.pdf<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/pages.rubrik.com\/host-resources-deep-dive_request.html\">https:\/\/pages.rubrik.com\/host-resources-deep-dive_request.html<\/a><\/noindex><br \/>\n<br \/>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/452884\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0415\u0441\u043b\u0438 \u0432\u044b \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0438\u0440\u0443\u0435\u0442\u0435 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043d\u0430 \u0431\u0430\u0437\u0435 VMware vSphere (\u0438\u043b\u0438 \u043b\u044e\u0431\u043e\u0433\u043e \u0434\u0440\u0443\u0433\u043e\u0433\u043e \u0441\u0442\u0435\u043a\u0430 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0439), \u0442\u043e \u043d\u0430\u0432\u0435\u0440\u043d\u044f\u043a\u0430 \u0447\u0430\u0441\u0442\u043e \u0441\u043b\u044b\u0448\u0438\u0442\u0435 \u043e\u0442 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0436\u0430\u043b\u043e\u0431\u044b: \u00ab\u0412\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u0430\u044f \u043c\u0430\u0448\u0438\u043d\u0430 \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u043c\u0435\u0434\u043b\u0435\u043d\u043d\u043e!\u00bb. \u0412 \u044d\u0442\u043e\u043c \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u0440\u0430\u0437\u0431\u0435\u0440\u0443 \u043c\u0435\u0442\u0440\u0438\u043a\u0438 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0438 \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0443, \u0447\u0442\u043e \u0438 \u043f\u043e\u0447\u0435\u043c\u0443 \u00ab\u0442\u043e\u0440\u043c\u043e\u0437\u0438\u0442\u00bb \u0438 \u043a\u0430\u043a \u0441\u0434\u0435\u043b\u0430\u0442\u044c \u0442\u0430\u043a, \u0447\u0442\u043e\u0431\u044b \u043d\u0435 \u00ab\u0442\u043e\u0440\u043c\u043e\u0437\u0438\u043b\u043e\u00bb. \u0411\u0443\u0434\u0443 \u0440\u0430\u0441\u0441\u043c\u0430\u0442\u0440\u0438\u0432\u0430\u0442\u044c \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u0435 \u0430\u0441\u043f\u0435\u043a\u0442\u044b \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0430\u0448\u0438\u043d: CPU, RAM, DISK, [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":25892,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-34335","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.0.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0415\u0441\u043b\u0438 \u0432\u044b \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0438\u0440\u0443\u0435\u0442\u0435 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043d\u0430 \u0431\u0430\u0437\u0435 VMware vSphere (\u0438\u043b\u0438 \u043b\u044e\u0431\u043e\u0433\u043e \u0434\u0440\u0443\u0433\u043e\u0433\u043e \u0441\u0442\u0435\u043a\u0430 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0439), \u0442\u043e \u043d\u0430\u0432\u0435\u0440\u043d\u044f\u043a\u0430 \u0447\u0430\u0441\u0442\u043e \u0441\u043b\u044b\u0448\u0438\u0442\u0435 \u043e\u0442 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0436\u0430\u043b\u043e\u0431\u044b: \u00ab\u0412\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u0430\u044f \u043c\u0430\u0448\u0438\u043d\u0430 \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u043c\u0435\u0434\u043b\u0435\u043d\u043d\u043e!\u00bb. \u0412 \u044d\u0442\u043e\u043c \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u0440\u0430\u0437\u0431\u0435\u0440\u0443 \u043c\u0435\u0442\u0440\u0438\u043a\u0438 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0438 \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0443, \u0447\u0442\u043e \u0438 \u043f\u043e\u0447\u0435\u043c\u0443 \u00ab\u0442\u043e\u0440\u043c\u043e\u0437\u0438\u0442\u00bb \u0438 \u043a\u0430\u043a \u0441\u0434\u0435\u043b\u0430\u0442\u044c \u0442\u0430\u043a, \u0447\u0442\u043e\u0431\u044b \u043d\u0435 \u00ab\u0442\u043e\u0440\u043c\u043e\u0437\u0438\u043b\u043e\u00bb. \u0411\u0443\u0434\u0443 \u0440\u0430\u0441\u0441\u043c\u0430\u0442\u0440\u0438\u0432\u0430\u0442\u044c \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u0435 \u0430\u0441\u043f\u0435\u043a\u0442\u044b \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0430\u0448\u0438\u043d: CPU, RAM, DISK,\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/analiz-proizvoditelnosti-virtualnoj-mashiny-v-vmware-vsphere-chast-1-cpu\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.0.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0410\u043d\u0430\u043b\u0438\u0437 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0439 \u043c\u0430\u0448\u0438\u043d\u044b \u0432 VMware vSphere. \u0427\u0430\u0441\u0442\u044c 1: CPU | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0415\u0441\u043b\u0438 \u0432\u044b \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0438\u0440\u0443\u0435\u0442\u0435 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043d\u0430 \u0431\u0430\u0437\u0435 VMware vSphere (\u0438\u043b\u0438 \u043b\u044e\u0431\u043e\u0433\u043e \u0434\u0440\u0443\u0433\u043e\u0433\u043e \u0441\u0442\u0435\u043a\u0430 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0439), \u0442\u043e \u043d\u0430\u0432\u0435\u0440\u043d\u044f\u043a\u0430 \u0447\u0430\u0441\u0442\u043e \u0441\u043b\u044b\u0448\u0438\u0442\u0435 \u043e\u0442 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0436\u0430\u043b\u043e\u0431\u044b: \u00ab\u0412\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u0430\u044f \u043c\u0430\u0448\u0438\u043d\u0430 \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u043c\u0435\u0434\u043b\u0435\u043d\u043d\u043e!\u00bb. \u0412 \u044d\u0442\u043e\u043c \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u0440\u0430\u0437\u0431\u0435\u0440\u0443 \u043c\u0435\u0442\u0440\u0438\u043a\u0438 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0438 \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0443, \u0447\u0442\u043e \u0438 \u043f\u043e\u0447\u0435\u043c\u0443 \u00ab\u0442\u043e\u0440\u043c\u043e\u0437\u0438\u0442\u00bb \u0438 \u043a\u0430\u043a \u0441\u0434\u0435\u043b\u0430\u0442\u044c \u0442\u0430\u043a, \u0447\u0442\u043e\u0431\u044b \u043d\u0435 \u00ab\u0442\u043e\u0440\u043c\u043e\u0437\u0438\u043b\u043e\u00bb. \u0411\u0443\u0434\u0443 \u0440\u0430\u0441\u0441\u043c\u0430\u0442\u0440\u0438\u0432\u0430\u0442\u044c \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u0435 \u0430\u0441\u043f\u0435\u043a\u0442\u044b \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0430\u0448\u0438\u043d: CPU, RAM, DISK,\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/analiz-proizvoditelnosti-virtualnoj-mashiny-v-vmware-vsphere-chast-1-cpu\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T18:57:43+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:57:43+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Analiza e performanc\u00ebs s\u00eb makinave virtuale n\u00eb VMware vSphere. Pjesa 1: CPU | ProHoster","description":"N\u00ebse administroni nj\u00eb infrastruktur\u00eb virtuale mbi VMware vSphere (ose \u00e7do grumbull tjet\u00ebr teknologjish), me siguri d\u00ebgjoni shpesh ankesa nga p\u00ebrdoruesit: \"Makin\u00eb virtuale punon ngadal\u00eb!\". N\u00eb k\u00ebt\u00eb cik\u00ebl artikujsh do t\u00eb shqyrtoj metrikat e performanc\u00ebs dhe do t\u00eb shpjegoj se \u00e7far\u00eb dhe pse \"ngadal\u00ebson\" dhe si t\u00eb b\u00ebni q\u00eb t\u00eb mos \"ngadal\u00ebsohet\". Do t\u00eb shqyrtoj k\u00ebto aspekte t\u00eb performanc\u00ebs s\u00eb makinave virtuale: CPU, RAM, DISK,","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/analiz-proizvoditelnosti-virtualnoj-mashiny-v-vmware-vsphere-chast-1-cpu","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0410\u043d\u0430\u043b\u0438\u0437 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0439 \u043c\u0430\u0448\u0438\u043d\u044b \u0432 VMware vSphere. \u0427\u0430\u0441\u0442\u044c 1: CPU | ProHoster","og:description":"\u0415\u0441\u043b\u0438 \u0432\u044b \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0438\u0440\u0443\u0435\u0442\u0435 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043d\u0430 \u0431\u0430\u0437\u0435 VMware vSphere (\u0438\u043b\u0438 \u043b\u044e\u0431\u043e\u0433\u043e \u0434\u0440\u0443\u0433\u043e\u0433\u043e \u0441\u0442\u0435\u043a\u0430 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0439), \u0442\u043e \u043d\u0430\u0432\u0435\u0440\u043d\u044f\u043a\u0430 \u0447\u0430\u0441\u0442\u043e \u0441\u043b\u044b\u0448\u0438\u0442\u0435 \u043e\u0442 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0436\u0430\u043b\u043e\u0431\u044b: \u00ab\u0412\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u0430\u044f \u043c\u0430\u0448\u0438\u043d\u0430 \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u043c\u0435\u0434\u043b\u0435\u043d\u043d\u043e!\u00bb. \u0412 \u044d\u0442\u043e\u043c \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u0440\u0430\u0437\u0431\u0435\u0440\u0443 \u043c\u0435\u0442\u0440\u0438\u043a\u0438 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0438 \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0443, \u0447\u0442\u043e \u0438 \u043f\u043e\u0447\u0435\u043c\u0443 \u00ab\u0442\u043e\u0440\u043c\u043e\u0437\u0438\u0442\u00bb \u0438 \u043a\u0430\u043a \u0441\u0434\u0435\u043b\u0430\u0442\u044c \u0442\u0430\u043a, \u0447\u0442\u043e\u0431\u044b \u043d\u0435 \u00ab\u0442\u043e\u0440\u043c\u043e\u0437\u0438\u043b\u043e\u00bb. \u0411\u0443\u0434\u0443 \u0440\u0430\u0441\u0441\u043c\u0430\u0442\u0440\u0438\u0432\u0430\u0442\u044c \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u0435 \u0430\u0441\u043f\u0435\u043a\u0442\u044b \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0430\u0448\u0438\u043d: CPU, RAM, DISK,","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/analiz-proizvoditelnosti-virtualnoj-mashiny-v-vmware-vsphere-chast-1-cpu","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T18:57:43+00:00","article:modified_time":"2019-10-31T18:57:43+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"34335","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-21 18:48:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:23:17","updated":"2026-01-21 18:48:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/34335","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=34335"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/34335\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/25892"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=34335"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=34335"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=34335"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}