{"id":35292,"date":"2019-10-31T22:03:28","date_gmt":"2019-10-31T19:03:28","guid":{"rendered":"https:\/\/prohoster.info\/blog\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-2-memory\/"},"modified":"2019-10-31T22:03:28","modified_gmt":"2019-10-31T19:03:28","slug":"analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-2-memory","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-2-memory","title":{"rendered":"Anal\u00fdza v\u00fdkonu VM vo VMware vSphere. \u010cas\u0165 2: Pam\u00e4\u0165","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonu VM vo VMware vSphere. \u010cas\u0165 2: Pam\u00e4\u0165\" src=\"\/wp-content\/uploads\/be3cfe4d8ff6491b5e32a247b996ded3.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/452884\/\">\u010cas\u0165 1. O CPU<\/a><\/noindex><\/p>\n<p>V tomto \u010dl\u00e1nku sa budeme zaobera\u0165 po\u010d\u00edtadlami v\u00fdkonu pam\u00e4te RAM vo vSphere.<br \/>\nZatia\u013e \u010do pam\u00e4\u0165 je v porovnan\u00ed s procesorom jednozna\u010dnej\u0161ia: ak sa vo VM objavia probl\u00e9my s v\u00fdkonom, \u0165a\u017eko si ich nev\u0161imnete. Na druhej strane, ak sa objavia, je s nimi ove\u013ea \u0165a\u017e\u0161ie zaobch\u00e1dza\u0165. Ale po\u010fme po porad\u00ed. <noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Trochu te\u00f3rie<\/h3>\n<p>\nPam\u00e4\u0165 RAM virtu\u00e1lnych strojov sa berie z pam\u00e4te servera, na ktor\u00fdch VM be\u017eia. Je to celkom samozrejm\u00e9 :). Ak serveru ch\u00fdba pam\u00e4\u0165 pre v\u0161etky \u017eiadaj\u00face, ESXi za\u010dne uplat\u0148ova\u0165 techniky optimaliz\u00e1cie spotreby pam\u00e4te (techniky obnova pam\u00e4te). V opa\u010dnom pr\u00edpade by opera\u010dn\u00e9 syst\u00e9my VM padli s chybami pr\u00edstupu do RAM. <\/p>\n<p>Ak\u00e9 techniky aplikova\u0165, sa ESXi rozhoduje v z\u00e1vislosti od za\u0165a\u017eenia pam\u00e4te:<\/p>\n<p><b>Stav pam\u00e4te<\/b><\/p>\n<p><b>Hranica<\/b><\/p>\n<p><b>Akcie<\/b><\/p>\n<p>Vysok\u00e1<\/p>\n<p>400 % z minFree<\/p>\n<p>Po dosiahnut\u00ed hornej hranice s\u00fa ve\u013ek\u00e9 str\u00e1nky pam\u00e4te rozdelen\u00e9 na mal\u00e9 (TPS pracuje v \u0161tandardnom re\u017eime).<\/p>\n<p>Vymaza\u0165<\/p>\n<p>100 % z minFree<\/p>\n<p>Ve\u013ek\u00e9 str\u00e1nky pam\u00e4te s\u00fa rozdelen\u00e9 na mal\u00e9, TPS pracuje n\u00fatene.<\/p>\n<p>Soft<\/p>\n<p>64 % z minFree<\/p>\n<p>TPS + Balloon<\/p>\n<p>Hard<\/p>\n<p>32 % z minFree<\/p>\n<p>TPS + Compress + Swap<\/p>\n<p>N\u00edzka<\/p>\n<p>16 % z minFree<\/p>\n<p>Compress + Swap + Block<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2015\/03\/02\/what-happens-at-which-vsphere-memory-state\/\">Zdroj<\/a><\/noindex> <\/p>\n<p>minFree je pam\u00e4\u0165 RAM potrebn\u00e1 na fungovanie hyperv\u00edzora. <\/p>\n<p>Do verzie ESXi 4.1 vr\u00e1tane bola minFree predvolene fixn\u00e1 - 6 % z objemu pam\u00e4te servera (percento sa dalo zmeni\u0165 cez vo\u013ebu Mem.MinFreePct na ESXi). V nov\u0161\u00edch verzi\u00e1ch, vzh\u013eadom na n\u00e1rast objemov pam\u00e4te na serveroch, sa minFree za\u010dalo po\u010d\u00edta\u0165 na z\u00e1klade objemu pam\u00e4te hostite\u013ea, a nie ako fixn\u00e9 percentu\u00e1lne hodnotenie. <\/p>\n<p>Hodnota minFree (predvolene) sa po\u010d\u00edta nasleduj\u00facim sp\u00f4sobom:<\/p>\n<p><b>Percento pam\u00e4te vyhraden\u00e9 pre minFree<\/b><\/p>\n<p><b>Rozsah pam\u00e4te<\/b><\/p>\n<p>6%<\/p>\n<p>0-4 GB<\/p>\n<p>4%<\/p>\n<p>4-12 GB<\/p>\n<p>2%<\/p>\n<p>12-28 GB<\/p>\n<p>1%<\/p>\n<p>Zost\u00e1vaj\u00faca pam\u00e4\u0165<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2013\/06\/14\/how-does-mem-minfreepct-work-with-vsphere-5-0-and-up\/\">Zdroj<\/a><\/noindex><\/p>\n<p>Napr\u00edklad pre server s 128 GB RAM bude hodnota MinFree nasledovn\u00e1:<br \/>\nMinFree = 245,76 + 327,68 + 327,68 + 1024 = 1925,12 MB = 1,88 GB <br \/>\nSkuto\u010dn\u00e1 hodnota sa m\u00f4\u017ee l\u00ed\u0161i\u0165 o p\u00e1r stoviek MB, \u010do z\u00e1vis\u00ed od servera a pam\u00e4te RAM.<\/p>\n<p><b>Percento pam\u00e4te vyhraden\u00e9 pre minFree<\/b><\/p>\n<p><b>Rozsah pam\u00e4te<\/b><\/p>\n<p><b>Hodnota pre 128 GB<\/b><\/p>\n<p>6%<\/p>\n<p>0-4 GB<\/p>\n<p>245,76 MB<\/p>\n<p>4%<\/p>\n<p>4-12 GB<\/p>\n<p>327,68 MB<\/p>\n<p>2%<\/p>\n<p>12-28 GB<\/p>\n<p>327,68 MB<\/p>\n<p>1%<\/p>\n<p>Zost\u00e1vaj\u00faca pam\u00e4\u0165 (100 GB)<\/p>\n<p>1024 MB<\/p>\n<p>\nObvykle pre produk\u010dn\u00e9 pracovisk\u00e1 je norm\u00e1lne pova\u017eova\u0165 len stav Vysok\u00fd. Pre testovacie a v\u00fdvojov\u00e9 prostredia m\u00f4\u017eu by\u0165 prijate\u013en\u00e9 stavy Clear\/Soft. Ak na hostite\u013eovi zostane menej ako 64 % MinFree, potom s\u00fa na \u0148om be\u017eiace VM ur\u010dite pozorovan\u00e9 probl\u00e9my s v\u00fdkonom.<\/p>\n<p>V ka\u017edom stave sa aplikuj\u00fa ur\u010dit\u00e9 techniky uvo\u013e\u0148ovania pam\u00e4te, za\u010d\u00ednaj\u00fac TPS, ktor\u00fd prakticky neovplyv\u0148uje v\u00fdkon VM, a kon\u010diac swapovan\u00edm. Povediem v\u00e1s podrobnej\u0161ie o nich. <\/p>\n<p><b>Transparent Page Sharing (TPS).<\/b> TPS je v podstate deduplik\u00e1cia str\u00e1n opera\u010dnej pam\u00e4te virtu\u00e1lnych strojov na serveri.<\/p>\n<p>ESXi vyh\u013ead\u00e1va rovnak\u00e9 str\u00e1nky opera\u010dnej pam\u00e4te virtu\u00e1lnych strojov, po\u010d\u00edta a porovn\u00e1va hash hodnoty str\u00e1n a odstra\u0148uje duplicity str\u00e1n, nahr\u00e1dzaj\u00fac ich odkazmi na jednu a t\u00fa ist\u00fa str\u00e1nku v fyzickej pam\u00e4ti servera. V d\u00f4sledku toho sa zni\u017euje spotreba fyzickej pam\u00e4te a je mo\u017en\u00e9 dosiahnu\u0165 ur\u010dit\u00fa over-subscription pam\u00e4te takmer bez zn\u00ed\u017eenia v\u00fdkonu.<\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonu VM vo VMware vSphere. \u010cas\u0165 2: Pam\u00e4\u0165\" src=\"\/wp-content\/uploads\/c36972169fea245fd1298b03ebf471d2.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/www.vladan.fr\/vmware-transparent-page-sharing-tps-explained\/\">Zdroj<\/a><\/noindex><\/p>\n<p>Tento mechanizmus funguje len pre str\u00e1nky pam\u00e4te ve\u013ekosti 4 KB (mal\u00e9 str\u00e1nky). Hyperv\u00edzor sa ani nepok\u00fa\u0161a deduplikova\u0165 str\u00e1nky ve\u013ekosti 2 MB (ve\u013ek\u00e9 str\u00e1nky); \u0161anca na n\u00e1jdenie rovnak\u00fdch str\u00e1nok tejto ve\u013ekosti nie je ve\u013ek\u00e1.<\/p>\n<p>Predvolene ESXi pride\u013euje pam\u00e4\u0165 ve\u013ek\u00fdm str\u00e1nkam. Rozdelenie ve\u013ek\u00fdch str\u00e1nok na mal\u00e9 sa za\u010d\u00edna pri dosiahnut\u00ed prahu stavu High a vynucuje sa, ke\u010f sa dosiahne stav Clear (pozri tabu\u013eku stavov hyperv\u00edzora).<\/p>\n<p>Ak v\u0161ak chcete, aby TPS za\u010dal pracova\u0165, bez \u010dakania na zaplnenie opera\u010dnej pam\u00e4te hostite\u013ea, je potrebn\u00e9 v Pokro\u010dil\u00fdch mo\u017enostiach ESXi nastavi\u0165 hodnotu <i>\u201cMem.AllocGuestLargePage\u201d<\/i> na 0 (predvolene 1). T\u00fdmto sa deaktivuje pride\u013eovanie ve\u013ek\u00fdch str\u00e1nok pam\u00e4te pre virtu\u00e1lne stroje.<\/p>\n<p>Od decembra 2014 je vo v\u0161etk\u00fdch verzi\u00e1ch ESXi TPS medzi VM predvolene vypnut\u00fd, preto\u017ee bola objaven\u00e1 zranite\u013enos\u0165, ktor\u00e1 teoreticky umo\u017e\u0148uje z\u00edska\u0165 pr\u00edstup z jedn\u00e9ho VM k opera\u010dnej pam\u00e4ti in\u00e9ho VM. Podrobnosti tu. Inform\u00e1cie o praktickej realiz\u00e1cii zneu\u017eitia zranite\u013enosti TPS som nezaznamenal.<\/p>\n<p>Politika TPS sa riadi prostredn\u00edctvom pokro\u010dilej mo\u017enosti <i>\u201cMem.ShareForceSalting\u201d<\/i> na ESXi:<br \/>\n0 \u2014 Inter-VM TPS. TPS pracuje pre str\u00e1nky r\u00f4znych VM;<br \/>\n1 \u2013 TPS pre VM s rovnakou hodnotou \u201csched.mem.pshare.salt\u201d v VMX;<br \/>\n2 (predvolene) \u2013 Intra-VM TPS. TPS pracuje pre str\u00e1nky vo vn\u00fatri VM.<\/p>\n<p>Rozhodne m\u00e1 zmysel vypn\u00fa\u0165 ve\u013ek\u00e9 str\u00e1nky a zapn\u00fa\u0165 Inter-VM TPS na testovac\u00edch staniciach. To sa d\u00e1 tie\u017e pou\u017ei\u0165 pre stanice s v\u00e4\u010d\u0161\u00edm mno\u017estvom rovnak\u00fdch VM. Napr\u00edklad na staniciach s VDI m\u00f4\u017ee \u00faspora fyzickej pam\u00e4te dosiahnu\u0165 desiatky percent. <\/p>\n<p><b>Memory Ballooning.<\/b> Ballooning u\u017e nie je tak\u00e1 bezprobl\u00e9mov\u00e1 a pre opera\u010dn\u00fd syst\u00e9m VM technika ako TPS. Ale pri spr\u00e1vnom pou\u017eit\u00ed s Ballooningom je mo\u017en\u00e9 \u017ei\u0165 a dokonca pracova\u0165.<\/p>\n<p>Spolu s Vmware Tools sa na VM in\u0161taluje \u0161peci\u00e1lny ovl\u00e1da\u010d naz\u00fdvan\u00fd Balloon Driver (takisto vmmemctl). Ke\u010f hyperv\u00edzor za\u010dne ma\u0165 nedostatok fyzickej pam\u00e4te a prejde do stavu Soft, ESXi po\u017eiada VM, aby vr\u00e1tila nepou\u017e\u00edvan\u00fa RAM cez tento Balloon Driver. Ovl\u00e1da\u010d na svoju stranu pracuje na \u00farovni opera\u010dn\u00e9ho syst\u00e9mu a \u017eiada vo\u013en\u00fa pam\u00e4\u0165 od neho. Hyperv\u00edzor vid\u00ed, ktor\u00e9 str\u00e1nky fyzickej pam\u00e4te zaber\u00e1 Balloon Driver, zoberie pam\u00e4\u0165 od virtu\u00e1lnej ma\u0161iny a vr\u00e1ti ju hostite\u013eovi. Probl\u00e9my s fungovan\u00edm OS nevznikaj\u00fa, preto\u017ee na \u00farovni OS je pam\u00e4\u0165 obsaden\u00e1 Balloon Driverom. Pod\u013ea predvolen\u00fdch nastaven\u00ed m\u00f4\u017ee Balloon Driver vzia\u0165 a\u017e 65% pam\u00e4te VM.<\/p>\n<p>Ak na VM nie s\u00fa nain\u0161talovan\u00e9 VMware Tools alebo je Ballooning vypnut\u00e9 (neodpor\u00fa\u010dam, ale existuje <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1002586\">KB<\/a><\/noindex>:), hyperv\u00edzor okam\u017eite prech\u00e1dza k pr\u00edsnej\u0161\u00edm technik\u00e1m odoberania pam\u00e4te. Z\u00e1ver: dbajte na to, aby VMware Tools boli na VM.<\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonu VM vo VMware vSphere. \u010cas\u0165 2: Pam\u00e4\u0165\" src=\"\/wp-content\/uploads\/884df6a7f5610d9bb372a7c34558f280.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Funkciu Balloon Drivera m\u00f4\u017eete skontrolova\u0165 z OS cez VMware Tools<\/i>.<\/p>\n<p><b>Memory Compression.<\/b> T\u00e1to technika sa aplikuje, ke\u010f ESXi dosiahne stav Hard. Ako vypl\u00fdva z n\u00e1zvu, ESXi sa sna\u017e\u00ed komprimova\u0165 4 KByte str\u00e1nky opera\u010dnej pam\u00e4te na 2 KByte a t\u00fdm uvo\u013eni\u0165 trochu miesta v fyzickej pam\u00e4ti servera. T\u00e1to technika v\u00fdrazne zvy\u0161uje \u010das pr\u00edstupu k obsahu str\u00e1nok opera\u010dnej pam\u00e4te VM, preto\u017ee str\u00e1nku je potrebn\u00e9 najprv dekomprimova\u0165. Niekedy sa nepodar\u00ed skomprimova\u0165 v\u0161etky str\u00e1nky a samotn\u00fd proces si zaberie ur\u010dit\u00fd \u010das. Preto t\u00e1to technika v praxi nie je ve\u013emi efekt\u00edvna.<\/p>\n<p><b>Memory Swapping.<\/b> Po kr\u00e1tkej f\u00e1ze Memory Compression ESXi takmer nevyhnutne (ak VM neodi\u0161li na in\u00e9 hosty alebo sa nevypnuli) prech\u00e1dza k Swappingu. A ak sa pam\u00e4\u0165 takmer vy\u010derp\u00e1 (stav Low), hyperv\u00edzor taktie\u017e prestane pride\u013eova\u0165 VM str\u00e1nky pam\u00e4te, \u010do m\u00f4\u017ee sp\u00f4sobi\u0165 probl\u00e9my v hos\u0165uj\u00facich OS VM.<\/p>\n<p>Takto funguje Swapping. Po zapnut\u00ed virtu\u00e1lneho stroja sa vytvor\u00ed s\u00fabor s pr\u00edponou .vswp. Jeho ve\u013ekos\u0165 zodpoved\u00e1 nevyhradenej RAM virtu\u00e1lneho stroja: to je rozdiel medzi nakonfigurovanou a vyhradenou pam\u00e4\u0165ou. Pri pr\u00e1ci Swappingu ESXi uvo\u013e\u0148uje str\u00e1nky pam\u00e4te virtu\u00e1lneho stroja do tohto s\u00faboru a za\u010d\u00edna s n\u00edm pracova\u0165 namiesto fyzickej pam\u00e4te servera. Samozrejme, tak\u00e1to \"opera\u010dn\u00e1\" pam\u00e4\u0165 je nieko\u013eko poriadkov pomal\u0161ia ako skuto\u010dn\u00e1, aj ke\u010f sa .vswp nach\u00e1dza na r\u00fdchlom \u00falo\u017eisku.<\/p>\n<p>Na rozdiel od Ballooningu, pri ktorom sa virtu\u00e1lnemu stroju odoberaj\u00fa nevyu\u017e\u00edvan\u00e9 str\u00e1nky, m\u00f4\u017eu pri Swappingu na disk prejs\u0165 aj str\u00e1nky, ktor\u00e9 akt\u00edvne pou\u017e\u00edvaj\u00fa opera\u010dn\u00fd syst\u00e9m alebo aplik\u00e1cie vo virtu\u00e1lnom stroji. V d\u00f4sledku toho sa v\u00fdkon virtu\u00e1lneho stroja zni\u017euje a\u017e do \u00fapln\u00e9ho zamrznutia. Virtu\u00e1lny stroj form\u00e1lne pracuje a je mo\u017en\u00e9 ho aspo\u0148 spr\u00e1vne vypn\u00fa\u0165 z opera\u010dn\u00e9ho syst\u00e9mu. Ak budete trpezliv\u00ed \ud83d\ude09<\/p>\n<p>Ak virtu\u00e1lne stroje pre\u0161li do Swap \u2014 ide o nepriazniv\u00fa situ\u00e1ciu, ktorej sa rad\u0161ej treba vyhn\u00fa\u0165.<\/p>\n<h3>Hlavn\u00e9 ukazovatele v\u00fdkonu pam\u00e4te virtu\u00e1lneho stroja<\/h3>\n<p>\nTu sme sa dostali k podstatn\u00e9mu. Na monitorovanie stavu pam\u00e4te vo virtu\u00e1lnom stroji existuj\u00fa nasleduj\u00face ukazovatele:<\/p>\n<p><b>Akt\u00edvne<\/b> \u2014 ukazuje objem opera\u010dnej pam\u00e4te (KB), ku ktor\u00e9mu virtu\u00e1lny stroj z\u00edskal pr\u00edstup v predch\u00e1dzaj\u00facom meracom obdob\u00ed.<\/p>\n<p><b>Pou\u017eitie<\/b> \u2014 to ist\u00e9 ako Active, ale v percent\u00e1ch z nakonfigurovanej opera\u010dnej pam\u00e4te virtu\u00e1lneho stroja. Vypo\u010d\u00edtava sa pod\u013ea nasleduj\u00faceho vzorca: active \u00f7 ve\u013ekos\u0165 nakonfigurovanej pam\u00e4te virtu\u00e1lneho stroja.<br \/>\nVysok\u00e9 Usage a Active preto nie v\u017edy znamen\u00e1, \u017ee v\u00fdkon virtu\u00e1lneho stroja je probl\u00e9mov\u00fd. Ak virtu\u00e1lny stroj agres\u00edvne vyu\u017e\u00edva pam\u00e4\u0165 (aspo\u0148 k nej z\u00edskava pr\u00edstup), neznamen\u00e1 to, \u017ee je nedostatok pam\u00e4te. Sk\u00f4r je to d\u00f4vod, aby sme sa pozreli, \u010do sa deje v opera\u010dnom syst\u00e9me.<br \/>\nExistuje \u0161tandardn\u00fd Alarm na Memory Usage pre virtu\u00e1lne stroje:<\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonu VM vo VMware vSphere. \u010cas\u0165 2: Pam\u00e4\u0165\" src=\"\/wp-content\/uploads\/073132b332da79be15e3bedf2c66cf94.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Zdie\u013ean\u00fd<\/b> \u2014 objem opera\u010dnej pam\u00e4te virtu\u00e1lneho stroja, deduplikovanej pomocou TPS (vo virtu\u00e1lnom stroji alebo medzi virtu\u00e1lnymi strojmi).<\/p>\n<p><b>Granted<\/b> \u2014 objem fyzickej pam\u00e4te hostite\u013ea (KB), ktor\u00fd bol pridelen\u00fd virtu\u00e1lnemu stroju. Zoh\u013ead\u0148uje Shared.<\/p>\n<p><b>Consumed<\/b> (Granted \u2014 Shared) \u2014 objem fyzickej pam\u00e4te (KB), ktor\u00fa virtu\u00e1lny stroj vyu\u017e\u00edva z hostite\u013ea. Nezoh\u013ead\u0148uje Shared.<\/p>\n<p>Ak \u010das\u0165 pam\u00e4te virtu\u00e1lneho stroja nie je poskytovan\u00e1 z fyzickej pam\u00e4te hostite\u013ea, ale zo swap s\u00faboru alebo pam\u00e4\u0165 je odobran\u00e1 virtu\u00e1lnemu stroju prostredn\u00edctvom Balloon Driver, tento objem sa nezoh\u013ead\u0148uje v Granted a Consumed.<br \/>\nVysok\u00e9 hodnoty Granted a Consumed s\u00fa \u00faplne norm\u00e1lne. Opera\u010dn\u00fd syst\u00e9m postupne berie pam\u00e4\u0165 od hyperv\u00edzora a nevracia ju sp\u00e4\u0165. S \u010dasom sa pri akt\u00edvne funguj\u00facej VM hodnoty t\u00fdchto \u010d\u00edta\u010dov bl\u00ed\u017eia objemu konfigurovanej pam\u00e4te, a tam zost\u00e1vaj\u00fa.<\/p>\n<p><b>Nula<\/b> \u2014 objem RAM VM (kB), ktor\u00fd obsahuje nuly. Tak\u00e1 pam\u00e4\u0165 je pova\u017eovan\u00e1 hyperv\u00edzorom za vo\u013en\u00fa a m\u00f4\u017ee by\u0165 poskytnut\u00e1 in\u00fdm virtu\u00e1lnym strojom. Po tom, \u010do hos\u0165ovsk\u00fd OS zap\u00ed\u0161e nie\u010do do nulovanej pam\u00e4te, prech\u00e1dza do stavu Consumed a sp\u00e4\u0165 sa u\u017e nevracia.<\/p>\n<p><b>Reserved Overhead<\/b> \u2014 objem RAM VM (kB) rezervovanej hyperv\u00edzorom pre fungovanie VM. Je to mal\u00fd objem, ale mus\u00ed by\u0165 dostupn\u00fd na hoste, inak VM nenastartuje.<\/p>\n<p><b>Balloon<\/b> \u2014 objem RAM (kB), ktor\u00fd bol odobrat\u00fd VM pomocou Balloon Driver.<\/p>\n<p><b>Compressed<\/b> \u2014 objem RAM (kB), ktor\u00fd sa podarilo komprimova\u0165.<\/p>\n<p><b>Swapped<\/b> \u2014 objem RAM (kB), ktor\u00fd sa z nedostatku fyzickej pam\u00e4te na serveri presunul na disk.<br \/>\nBalloon a ostatn\u00e9 \u010d\u00edta\u010de memory reclamation techniques s\u00fa rovn\u00e9 nule.<\/p>\n<p>Takto vyzer\u00e1 graf so \u010d\u00edta\u010dmi Memory norm\u00e1lne funguj\u00facej VM s 150 GB RAM.<\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonu VM vo VMware vSphere. \u010cas\u0165 2: Pam\u00e4\u0165\" src=\"\/wp-content\/uploads\/4c361a407581b24fc042c91a6d76aa68.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNa grafe ni\u017e\u0161ie m\u00e1 VM jasn\u00e9 probl\u00e9my. Pod grafom je vidie\u0165, \u017ee pre t\u00fato VM boli pou\u017eit\u00e9 v\u0161etky op\u00edsan\u00e9 techniky pr\u00e1ce s RAM. Balloon pre t\u00fato VM je zna\u010dne v\u00e4\u010d\u0161\u00ed ne\u017e Consumed. V skuto\u010dnosti je VM sk\u00f4r m\u0155tva ne\u017e \u017eiv\u00e1. <\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonu VM vo VMware vSphere. \u010cas\u0165 2: Pam\u00e4\u0165\" src=\"\/wp-content\/uploads\/fcc8f196fc7d158e82de4737c5ebe776.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>ESXTOP<\/h3>\n<p>\nRovnako ako s CPU, ak chceme r\u00fdchlo zhodnoti\u0165 situ\u00e1ciu na hoste, ako aj jej dynamiku s intervalom do 2 sek\u00fand, stoj\u00ed za to vyu\u017ei\u0165 ESXTOP.<\/p>\n<p>Obrazovka ESXTOP pre Memory sa vyvol\u00e1va kl\u00e1vesou \u201em\u201c a vyzer\u00e1 nasledovne (vybran\u00e9 polia B,D,H,J,K,L,O):<\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonu VM vo VMware vSphere. \u010cas\u0165 2: Pam\u00e4\u0165\" src=\"\/wp-content\/uploads\/27383c357fb351bbe8353abf3b08171e.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nZauj\u00edmav\u00e9 pre n\u00e1s bud\u00fa nasleduj\u00face parametre: <\/p>\n<p><b>Mem overcommit avg<\/b> \u2014 priemern\u00e1 hodnota pre overcommit pam\u00e4te na hoste za 1, 5 a 15 min\u00fat. Ak je nad nulou, je to d\u00f4vod pozrie\u0165 sa, \u010do sa deje, ale nie v\u017edy nazna\u010duje pr\u00edtomnos\u0165 probl\u00e9mov.<\/p>\n<p>V riadkoch <b>PMEM\/MB<\/b> a <b>VMKMEM\/MB<\/b> \u2014 inform\u00e1cie o fyzickej pam\u00e4ti servera a pam\u00e4ti dostupnej VMkernel. Zauj\u00edmav\u00e9 je tu vidie\u0165 hodnotu minfree (v MB), stav hosta z h\u013eadiska pam\u00e4te (v na\u0161om pr\u00edpade, high).<\/p>\n<p>V riadku <b>NUMA\/MB<\/b> je mo\u017en\u00e9 vidie\u0165 rozdelenie RAM medzi NUMA-n\u00f3dmi (sockety). V tomto pr\u00edklade je rozdelenie nerovnomern\u00e9, \u010do nie je ve\u013emi dobr\u00e9.<\/p>\n<p>Nasleduje celkov\u00e1 \u0161tatistika servera oh\u013eadom techn\u00edk uvo\u013e\u0148ovania pam\u00e4te:<\/p>\n<p><b>PSHARE\/M\u0411<\/b> \u2014 \u0161tatistika TPS;<\/p>\n<p><b>SWAP\/M\u0411<\/b> \u2014 \u0161tatistika vyu\u017eitia Swap;<\/p>\n<p><b>ZIP\/M\u0411<\/b> \u2014 \u0161tatistika kompresie str\u00e1nok pam\u00e4te;<\/p>\n<p><b>MEMCTL\/M\u0411<\/b> \u2014 \u0161tatistika vyu\u017eitia ovl\u00e1da\u010da Balloon.<\/p>\n<p>Pre jednotliv\u00e9 VM n\u00e1s m\u00f4\u017ee zauj\u00edma\u0165 nasledovn\u00e1 inform\u00e1cia. Men\u00e1 VM som skryl, aby som neur\u00e1\u017eal publikum:). Ak je metrika ESXTOP podobn\u00e1 \u010d\u00edta\u010du vo vSphere, uv\u00e1dzam zodpovedaj\u00faci \u010d\u00edta\u010d. <\/p>\n<p><b>MEMSZ<\/b> \u2014 objem pam\u00e4te, nakonfigurovan\u00fd na VM (MB).<br \/>\nMEMSZ = GRANT + MCTLSZ + SWCUR + untouched.<\/p>\n<p><b>GRANT<\/b> \u2014 Grantovan\u00e9 v MB.<\/p>\n<p><b>TCHD<\/b> \u2014 Akt\u00edvne v MB.<\/p>\n<p><b>MCTL?<\/b> \u2014 je na VM nain\u0161talovan\u00fd ovl\u00e1da\u010d Balloon.<\/p>\n<p><b>MCTLSZ<\/b> \u2014 Balloon v MB.<\/p>\n<p><b>MCTLGT<\/b> \u2014 objem RAM (MB), ktor\u00fd chce ESXi z\u00edska\u0165 od VM prostredn\u00edctvom ovl\u00e1da\u010da Balloon (Memctl Target).<\/p>\n<p><b>MCTLMAX<\/b> \u2014 maxim\u00e1lny objem RAM (MB), ktor\u00fd m\u00f4\u017ee ESXi z\u00edska\u0165 od VM prostredn\u00edctvom ovl\u00e1da\u010da Balloon.<\/p>\n<p><b>SWCUR<\/b> \u2014 aktu\u00e1lny objem RAM (MB), ktor\u00fd bol VM pridelen\u00fd zo Swap s\u00faboru. <\/p>\n<p><b>SWGT<\/b> \u2014 objem RAM (MB), ktor\u00fd chce ESXi prideli\u0165 VM zo Swap s\u00faboru (Swap Target).<\/p>\n<p>Cez ESXTOP je tie\u017e mo\u017en\u00e9 z\u00edska\u0165 podrobnej\u0161ie inform\u00e1cie o NUMA topol\u00f3gii VM. Na to je potrebn\u00e9 vybra\u0165 polia D,G:<\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonu VM vo VMware vSphere. \u010cas\u0165 2: Pam\u00e4\u0165\" src=\"\/wp-content\/uploads\/3fde4ab9d54c709f66313020437255c2.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>NHN<\/b> \u2013 NUMA uzly, na ktor\u00fdch sa nach\u00e1dza VM. Tu si m\u00f4\u017eete okam\u017eite v\u0161imn\u00fa\u0165 \u201ewide\u201c VM, ktor\u00e9 sa nezmestia na jeden NUMA uzol.<\/p>\n<p><b>NRMEM<\/b> \u2013 ko\u013eko megabajtov pam\u00e4te VM berie z vzdialen\u00e9ho NUMA uzla.<\/p>\n<p><b>NLMEM<\/b> \u2013 ko\u013eko megabajtov pam\u00e4te VM berie z lok\u00e1lneho NUMA uzla.<\/p>\n<p><b>N%L<\/b> \u2013 percento pam\u00e4te VM na lok\u00e1lnom NUMA uzle (ak je menej ako 80% \u2014 m\u00f4\u017eu sa vyskytn\u00fa\u0165 probl\u00e9my s v\u00fdkonom).<\/p>\n<h3>Pam\u00e4\u0165 na hyperv\u00edzore<\/h3>\n<p>\nAk s\u00fa \u010d\u00edta\u010de CPU na hyperv\u00edzore zvy\u010dajne bez ve\u013ek\u00e9ho z\u00e1ujmu, situ\u00e1cia s pam\u00e4\u0165ou je opa\u010dn\u00e1. Vysok\u00e1 spotreba pam\u00e4te na VM neznamen\u00e1 v\u017edy probl\u00e9m s v\u00fdkonom, ale vysok\u00e1 spotreba pam\u00e4te na hyperv\u00edzore sp\u00fa\u0161\u0165a techniky spr\u00e1vy pam\u00e4te a sp\u00f4sobuje probl\u00e9my s v\u00fdkonom VM. Je potrebn\u00e9 sledova\u0165 upozornenia na vyu\u017eitie pam\u00e4te hostite\u013ea a zabr\u00e1ni\u0165, aby sa VM dostala do Swap.<\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonu VM vo VMware vSphere. \u010cas\u0165 2: Pam\u00e4\u0165\" src=\"\/wp-content\/uploads\/27931f9a8607000dc9a7ca483c03ad68.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonu VM vo VMware vSphere. \u010cas\u0165 2: Pam\u00e4\u0165\" src=\"\/wp-content\/uploads\/4a1c0d6199a340dd62e5c923611ddd6e.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Unswap<\/h3>\n<p>\nAk sa VM dostane do Swap, jej v\u00fdkon sa v\u00fdrazne zni\u017euje. Stopy Ballooningu a kompresie r\u00fdchlo mizn\u00fa po tom, \u010do je na hostite\u013eovi op\u00e4\u0165 dostatok vo\u013enej pam\u00e4te, av\u0161ak vraca\u0165 sa zo Swap do pam\u00e4te servera sa virtu\u00e1lna ma\u0161ina nesn\u00e1\u017ei. <br \/>\nA\u017e do verzie ESXi 6.0 bol jedin\u00fdm spo\u013eahliv\u00fdm a r\u00fdchlym sp\u00f4sobom, ako vy\u0148a\u0165 VM zo Swap, re\u0161tart (presnej\u0161ie vypnutie a zapnutie kontajnera). Od verzie ESXi 6.0 sa objavil s\u00edce neofici\u00e1lny, ale funk\u010dn\u00fd a spo\u013eahliv\u00fd sp\u00f4sob, ako vy\u0148a\u0165 VM zo Swap. Na jednej z konferenci\u00ed som mal mo\u017enos\u0165 komunikova\u0165 s jedn\u00fdm z in\u017einierov VMware, ktor\u00fd zodpovedal za CPU Scheduler. Potvrdil, \u017ee t\u00e1to met\u00f3da je plne funk\u010dn\u00e1 a bezpe\u010dn\u00e1. V na\u0161ich sk\u00fasenostiach sme \u017eiadne probl\u00e9my s \u0148ou nezaznamenali.<\/p>\n<p>Vlastne pr\u00edkazy na vy\u0148atie VM zo Swap <noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2016\/06\/02\/memory-pages-swapped-can-unswap\/\">pop\u00edsal<\/a><\/noindex> Duncan Epping. Nebudem opakova\u0165 podrobnosti, len uvediem pr\u00edklad jej pou\u017eitia. Ako je vidie\u0165 na screenshotu, po ur\u010ditom \u010dase po vykonan\u00ed uveden\u00e9ho pr\u00edkazu sa Swap na VM vytrat\u00ed.<\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonu VM vo VMware vSphere. \u010cas\u0165 2: Pam\u00e4\u0165\" src=\"\/wp-content\/uploads\/c60d03c59e115d48b209dadc25081c1e.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Tipy na spr\u00e1vu opera\u010dnej pam\u00e4te na ESXi<\/h3>\n<p>\nNa z\u00e1ver uvediem nieko\u013eko tipov, ktor\u00e9 v\u00e1m pom\u00f4\u017eu vyhn\u00fa\u0165 sa probl\u00e9mom s v\u00fdkonom VM z d\u00f4vodu opera\u010dnej pam\u00e4te:<\/p>\n<ul>\n<li>Nedovo\u013ete prepisovanie opera\u010dnej pam\u00e4te v produk\u010dn\u00fdch klastroch. Odpor\u00fa\u010da sa ma\u0165 v\u017edy pribli\u017ene 20-30 % vo\u013enej pam\u00e4te v klastri, aby mal DRS (a administr\u00e1tor) priestor na man\u00e9vrovanie, a po\u010das migr\u00e1cie VM nepre\u0161li do Swap. Nezab\u00fadajte tie\u017e na rezervu pre vysok\u00fa dostupnos\u0165. Je nepr\u00edjemn\u00e9, ke\u010f pri zlyhan\u00ed jedn\u00e9ho servera a re\u0161tarte VM pomocou HA s\u00fa niektor\u00e9 stroje e\u0161te aj v Swap.<\/li>\n<li>V infra\u0161trukt\u00farach s vysokou konsolid\u00e1ciou sa sna\u017ete NEROBI\u0164 VM s pam\u00e4\u0165ou v\u00e4\u010d\u0161ou ako polovica pam\u00e4te hostite\u013ea. To op\u00e4\u0165 pom\u00f4\u017ee DRS bez probl\u00e9mov rozde\u013eova\u0165 virtu\u00e1lne stroje medzi servery klastra. Toto pravidlo nie je univerz\u00e1lne :).<\/li>\n<li>Sledujte Alarm o vyu\u017eit\u00ed pam\u00e4te hostite\u013ea.<\/li>\n<li>Nezab\u00fadajte nain\u0161talova\u0165 na VM VMware Tools a nevyp\u00ednajte Ballooning.<\/li>\n<li>Zv\u00e1\u017ete mo\u017enos\u0165 zapn\u00fa\u0165 Inter-VM TPS a vypn\u00fa\u0165 Large Pages v prostrediach s VDI a testovac\u00edch prostrediach.<\/li>\n<li>Ak m\u00e1 VM probl\u00e9my s v\u00fdkonom, skontrolujte, \u010di nepou\u017e\u00edva pam\u00e4\u0165 z dia\u013ekovej NUMA nody.<\/li>\n<li>Vyberte VM zo Swap \u010do najr\u00fdchlej\u0161ie! Okrem in\u00e9ho, ak je VM v Swape, z o\u010dividn\u00fdch d\u00f4vodov trp\u00ed aj SCSI.<\/li>\n<\/ul>\n<p>\nT\u00fdmto kon\u010d\u00edm t\u00e9mu opera\u010dnej pam\u00e4te. Ni\u017e\u0161ie s\u00fa \u010dl\u00e1nky na t\u00e9mu pre t\u00fdch, ktor\u00ed sa chc\u00fa hlb\u0161ie ponori\u0165 do detailov. Nasleduj\u00faci \u010dl\u00e1nok bude venovan\u00fd \u00falo\u017eisku.<\/p>\n<p><b class=\"spoiler_title\">U\u017eito\u010dn\u00e9 odkazy<\/b><noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2015\/03\/02\/what-happens-at-which-vsphere-memory-state\/\">http:\/\/www.yellow-bricks.com\/2015\/03\/02\/what-happens-at-which-vsphere-memory-state\/<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2013\/06\/14\/how-does-mem-minfreepct-work-with-vsphere-5-0-and-up\/\">http:\/\/www.yellow-bricks.com\/2013\/06\/14\/how-does-mem-minfreepct-work-with-vsphere-5-0-and-up\/<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/www.vladan.fr\/vmware-transparent-page-sharing-tps-explained\/\">https:\/\/www.vladan.fr\/vmware-transparent-page-sharing-tps-explained\/<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2016\/06\/02\/memory-pages-swapped-can-unswap\/\">http:\/\/www.yellow-bricks.com\/2016\/06\/02\/memory-pages-swapped-can-unswap\/<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1002586\">https:\/\/kb.vmware.com\/s\/article\/1002586<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/www.vladan.fr\/what-is-vmware-memory-ballooning\/\">https:\/\/www.vladan.fr\/what-is-vmware-memory-ballooning\/<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2080735\">https:\/\/kb.vmware.com\/s\/article\/2080735<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2017642\">https:\/\/kb.vmware.com\/s\/article\/2017642<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/labs.vmware.com\/vmtj\/vmware-esx-memory-resource-management-swap\">https:\/\/labs.vmware.com\/vmtj\/vmware-esx-memory-resource-management-swap<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/blogs.vmware.com\/vsphere\/2013\/10\/understanding-vsphere-active-memory.html\">https:\/\/blogs.vmware.com\/vsphere\/2013\/10\/understanding-vsphere-active-memory.html<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/www.vmware.com\/support\/developer\/converter-sdk\/conv51_apireference\/memory_counters.html#overhead\">https:\/\/www.vmware.com\/support\/developer\/converter-sdk\/conv51_apireference\/memory_counters.html<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/6.5\/vsphere-esxi-vcenter-server-65-monitoring-performance-guide.pdf\">https:\/\/docs.vmware.com\/en\/VMware-vSphere\/6.5\/vsphere-esxi-vcenter-server-65-monitoring-performance-guide.pdf<\/a><\/noindex><\/p>\n<p>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/455820\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0427\u0430\u0441\u0442\u044c 1. \u041f\u0440\u043e CPU \u0412 \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043f\u0440\u043e \u0441\u0447\u0435\u0442\u0447\u0438\u043a\u0438 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u043e\u043f\u0435\u0440\u0430\u0442\u0438\u0432\u043d\u043e\u0439 \u043f\u0430\u043c\u044f\u0442\u0438 (RAM) \u0432 vSphere. \u0412\u0440\u043e\u0434\u0435 \u0431\u044b \u0441 \u043f\u0430\u043c\u044f\u0442\u044c\u044e \u0432\u0441\u0435 \u0431\u043e\u043b\u0435\u0435 \u043e\u0434\u043d\u043e\u0437\u043d\u0430\u0447\u043d\u043e, \u0447\u0435\u043c \u0441 \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u043e\u0440\u043e\u043c: \u0435\u0441\u043b\u0438 \u043d\u0430 \u0412\u041c \u0432\u043e\u0437\u043d\u0438\u043a\u0430\u044e\u0442 \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, \u0438\u0445 \u0441\u043b\u043e\u0436\u043d\u043e \u043d\u0435 \u0437\u0430\u043c\u0435\u0442\u0438\u0442\u044c. \u0417\u0430\u0442\u043e \u0435\u0441\u043b\u0438 \u043e\u043d\u0438 \u043f\u043e\u044f\u0432\u043b\u044f\u044e\u0442\u0441\u044f, \u0441\u043f\u0440\u0430\u0432\u0438\u0442\u044c\u0441\u044f \u0441 \u043d\u0438\u043c\u0438 \u0433\u043e\u0440\u0430\u0437\u0434\u043e \u0441\u043b\u043e\u0436\u043d\u0435\u0435. \u041d\u043e \u043e\u0431\u043e \u0432\u0441\u0435\u043c \u043f\u043e \u043f\u043e\u0440\u044f\u0434\u043a\u0443. \u041d\u0435\u043c\u043d\u043e\u0433\u043e \u0442\u0435\u043e\u0440\u0438\u0438 \u041e\u043f\u0435\u0440\u0430\u0442\u0438\u0432\u043d\u0430\u044f \u043f\u0430\u043c\u044f\u0442\u044c [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-35292","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5 - aioseo.com -->\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\/sk\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-2-memory\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5\" \/>\n\t\t<meta property=\"og:locale\" content=\"sk_SK\" \/>\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 \u0412\u041c \u0432 VMware vSphere. \u0427\u0430\u0441\u0442\u044c 2: Memory | ProHoster\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-2-memory\" \/>\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-31T19:03:28+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:03:28+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\udd47Anal\u00fdza v\u00fdkonu VM v VMware vSphere. \u010cas\u0165 2: Pam\u00e4\u0165 | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-2-memory","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","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 \u0412\u041c \u0432 VMware vSphere. \u0427\u0430\u0441\u0442\u044c 2: Memory | ProHoster","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-2-memory","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-31T19:03:28+00:00","article:modified_time":"2019-10-31T19:03:28+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"35292","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 22:41:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 11:01:22","updated":"2026-01-21 22:41:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/35292","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=35292"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/35292\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=35292"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=35292"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=35292"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}