{"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\/sq\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-2-memory","title":{"rendered":"Analiza e performanc\u00ebs s\u00eb VM n\u00eb VMware vSphere. Pjesa 2: Memoria","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Analiza
\n
\nPjesa 1. Rreth procesorit<\/a><\/noindex><\/p>\n

N\u00eb k\u00ebt\u00eb artikull do t\u00eb flasim p\u00ebr numrat e performanc\u00ebs s\u00eb memories RAM n\u00eb vSphere.
\nDuket se p\u00ebr memorien gjith\u00e7ka \u00ebsht\u00eb m\u00eb e qart\u00eb sesa p\u00ebr procesorin: n\u00ebse ka probleme me performanc\u00ebn n\u00eb VM, ato jan\u00eb t\u00eb v\u00ebshtira p\u00ebr t'u humbur. Por n\u00ebse ato ndodhin, \u00ebsht\u00eb shum\u00eb m\u00eb e v\u00ebshtir\u00eb t\u00eb merremi me to. Ndaj, le t\u00eb fillojm\u00eb nga fillimi. <\/a><\/noindex><\/p>\n

Pak teori<\/h3>\n

\nMemoria e p\u00ebrkohshme e virtual machines merret nga memoria e serverit ku punojn\u00eb VM-t\u00eb. Kjo \u00ebsht\u00eb mjaft e qart\u00eb :). N\u00ebse memoria e serverit nuk \u00ebsht\u00eb e mjaftueshme p\u00ebr t\u00eb gjith\u00eb ata q\u00eb duan ta p\u00ebrdorin, ESXi fillon t\u00eb aplikoj\u00eb teknika optimizimi t\u00eb konsumit t\u00eb memories (memory reclamation techniques). N\u00eb t\u00eb kund\u00ebrt, sistemet operative t\u00eb VM-s\u00eb do t\u00eb shkonin n\u00eb crash p\u00ebr shkak t\u00eb gabimeve n\u00eb qasje n\u00eb RAM. <\/p>\n

Cilat teknika do t\u00eb aplikoj\u00eb ESXi vendoset n\u00eb var\u00ebsi t\u00eb ngarkes\u00ebs s\u00eb memories:<\/p>\n

Gjendja e memories<\/b><\/p>\n

Kufiri<\/b><\/p>\n

Veprimet<\/b><\/p>\n

I Lart\u00eb<\/p>\n

400% nga minFree<\/p>\n

Pasi arrihet kufiri i sip\u00ebrm, faqet e m\u00ebdha t\u00eb memories ndahen n\u00eb t\u00eb vogla (TPS punon n\u00eb modalitetin standard).<\/p>\n

Pastroni<\/p>\n

100% nga minFree<\/p>\n

Faqet e m\u00ebdha t\u00eb memories ndahen n\u00eb t\u00eb vogla, TPS punon me forc\u00eb.<\/p>\n

But\u00eb<\/p>\n

64% nga minFree<\/p>\n

TPS + Balloon<\/p>\n

Hard<\/p>\n

32% nga minFree<\/p>\n

TPS + Compress + Swap<\/p>\n

I Ul\u00ebt<\/p>\n

16% nga minFree<\/p>\n

Compress + Swap + Block<\/p>\n

Burimi<\/a><\/noindex> <\/p>\n

minFree \u00ebsht\u00eb memoria e nevojshme p\u00ebr funksionimin e hipervizorit. <\/p>\n

Derisa ESXi 4.1 p\u00ebrfshihej, minFree nga default ishte fiksuar n\u00eb 6% t\u00eb volumit t\u00eb memories s\u00eb serverit (procenti mund t\u00eb ndryshohej p\u00ebrmes opsionit Mem.MinFreePct n\u00eb ESXi). N\u00eb versionet m\u00eb t\u00eb fundit, p\u00ebr shkak t\u00eb rritjes s\u00eb volumit t\u00eb memories n\u00eb server\u00eb, minFree filloi t\u00eb llogaritej n\u00eb baz\u00eb t\u00eb volumit t\u00eb memories s\u00eb hostit, n\u00eb vend t\u00eb nj\u00eb vler\u00eb t\u00eb fiksuar procentuale. <\/p>\n

Vlera e minFree (nga default) llogaritet si m\u00eb posht\u00eb:<\/p>\n

Procenti i memories e rezervuar p\u00ebr minFree<\/b><\/p>\n

Shtrirja e memories<\/b><\/p>\n

6%<\/p>\n

0-4 GB<\/p>\n

4%<\/p>\n

4-12 GB<\/p>\n

2%<\/p>\n

12-28 GB<\/p>\n

1%<\/p>\n

Memoria e mbetur<\/p>\n

Burimi<\/a><\/noindex><\/p>\n

P\u00ebr shembull, p\u00ebr nj\u00eb server me 128 GB RAM, vlera MinFree do t\u00eb ishte si vijon:
\nMinFree = 245.76 + 327.68 + 327.68 + 1024 = 1925.12 MB = 1.88 GB
\nVlera reale mund t\u00eb ndryshoj\u00eb p\u00ebr disa qindra MB, kjo varet nga serveri dhe memoria e p\u00ebrkohshme.<\/p>\n

Procenti i memories e rezervuar p\u00ebr minFree<\/b><\/p>\n

Shtrirja e memories<\/b><\/p>\n

Vlera p\u00ebr 128 GB<\/b><\/p>\n

6%<\/p>\n

0-4 GB<\/p>\n

245.76 MB<\/p>\n

4%<\/p>\n

4-12 GB<\/p>\n

327.68 MB<\/p>\n

2%<\/p>\n

12-28 GB<\/p>\n

327.68 MB<\/p>\n

1%<\/p>\n

Memoria e mbetur (100 GB)<\/p>\n

1024 MB<\/p>\n

\nP\u00ebr zakonisht, p\u00ebr mjediset prodhuese, gjendja normale \u00ebsht\u00eb vet\u00ebm ajo e Lart\u00eb. P\u00ebr ambientet e testimit dhe zhvillimit, gjendjet e Qarta\/But\u00eb jan\u00eb t\u00eb pranueshme. N\u00ebse memoria e operativ\u00ebs n\u00eb host ka mbetur m\u00eb pak se 64% MinFree, at\u00ebher\u00eb pajisjet Virtuale (VM) q\u00eb funksionojn\u00eb mbi t\u00eb, patjet\u00ebr do t\u00eb ken\u00eb probleme me performanc\u00ebn.<\/p>\n

N\u00eb \u00e7do gjendje aplikohen teknika t\u00eb caktuara t\u00eb rikuperimit t\u00eb memories duke filluar nga TPS, e cila ka ndikim t\u00eb vog\u00ebl n\u00eb performanc\u00ebn e VM, deri te Swapping. Do t'ju tregoj m\u00eb shum\u00eb p\u00ebr to. <\/p>\n

Transparent Page Sharing (TPS).<\/b> TPS \u00ebsht\u00eb, thjesht, deduplication e faqeve t\u00eb memories s\u00eb operativ\u00ebs s\u00eb makinave virtuale n\u00eb server.<\/p>\n

ESXi k\u00ebrkon faqe t\u00eb nj\u00ebjta t\u00eb memories s\u00eb operativ\u00ebs s\u00eb makinave virtuale, duke llogaritur dhe krahasuar hash-in e faqeve, dhe heq kopjet e faqeve, duke i z\u00ebvend\u00ebsuar ato me reference n\u00eb t\u00eb nj\u00ebjt\u00ebn faqe n\u00eb memorien fizike t\u00eb serverit. Si rezultat, konsumimi i memories fizike reduktohet dhe \u00ebsht\u00eb e mundur t\u00eb arrihet nj\u00eb p\u00ebrshkall\u00ebzim i caktuar i memories praktikisht pa ulje t\u00eb performanc\u00ebs.<\/p>\n

\"Analiza
\nBurimi<\/a><\/noindex><\/p>\n

Ky mekaniz\u00ebm funksionon vet\u00ebm p\u00ebr faqe memories me madh\u00ebsi 4 KByte (faqe t\u00eb vogla). Hypervizori nuk p\u00ebrpiqet madje p\u00ebr t\u00eb deduplicuar faqet me madh\u00ebsi 2 MByte (faqe t\u00eb m\u00ebdha): shansi p\u00ebr t\u00eb gjetur faqe t\u00eb nj\u00ebjta t\u00eb till\u00eb nuk \u00ebsht\u00eb i lart\u00eb.<\/p>\n

N\u00eb m\u00ebnyr\u00eb t\u00eb paracaktuar, ESXi cakton memorien p\u00ebr faqet e m\u00ebdha. Shk\u00ebputja e faqeve t\u00eb m\u00ebdha n\u00eb t\u00eb vogla fillon kur arrihet pragu i gjendjes Lart\u00eb dhe ndodh forc\u00ebrisht kur arrihet gjendja Qart\u00eb (shih tabel\u00ebn e gjendjeve t\u00eb hypervizorit).<\/p>\n

N\u00ebse d\u00ebshironi q\u00eb TPS t\u00eb filloj\u00eb pun\u00ebn, pa pritur mbushjen e memories s\u00eb operativ\u00ebs s\u00eb hostit, n\u00eb mund\u00ebsit\u00eb e avancuara t\u00eb ESXi duhet t\u00eb vendosni vler\u00ebn \u201cMem.AllocGuestLargePage\u201d<\/i> n\u00eb 0 (e cila \u00ebsht\u00eb parazgjedhja 1). At\u00ebher\u00eb, caktimi i faqeve t\u00eb m\u00ebdha t\u00eb memories p\u00ebr makinat virtuale do t\u00eb jet\u00eb i \u00e7aktivizuar.<\/p>\n

Q\u00eb nga dhjetori 2014, n\u00eb t\u00eb gjitha l\u00ebshimet e ESXi, TPS midis VM-ve \u00ebsht\u00eb parazgjedhur e \u00e7aktivizuar, pasi u gjet nj\u00eb dob\u00ebsi, e cila teorikisht mund t\u00eb lejoj\u00eb p\u00ebr t\u00eb aksesuar nga nj\u00eb VM memorien e operativ\u00ebs s\u00eb nj\u00eb VM tjet\u00ebr. Detajet k\u00ebtu. Nuk kam hasur informacion p\u00ebr realizimin praktik t\u00eb shfryt\u00ebzimit t\u00eb dob\u00ebsis\u00eb TPS.<\/p>\n

Politika TPS kontrollohet p\u00ebrmes opsionit t\u00eb avancuar \u201cMem.ShareForceSalting\u201d<\/i> n\u00eb ESXi:
\n0 \u2014 Inter-VM TPS. TPS funksionon p\u00ebr faqe t\u00eb ndryshme VM;
\n1 \u2013 TPS p\u00ebr VM me vler\u00ebn e nj\u00ebjt\u00eb \u201csched.mem.pshare.salt\u201d n\u00eb VMX;
\n2 (parazgjedhja) \u2013 Intra-VM TPS. TPS funksionon p\u00ebr faqe brenda VM.<\/p>\n

Padyshmja e jo\u0308neve ka qene\u0301 e nevojshme per te\u0308 fikur faqet e medha dhe te\u0308 aktivizohet Inter-VM TPS ne\u0308 gethet e testimit. Kjo mund te\u0308 perdoret gjithashtu per gethet me numra te\u0308 madh te VM-ve te njejte. Per shembull, ne gethet me VDI, kursimi i memories fizike mund te\u0308 arrije disa dhjete perqind. <\/p>\n

Memoria Ballooning.<\/b> Ballooning nuk eshte me nje teknike e padukur dhe transparente per sistemin operativ te VM-ve si TPS. Por me aplikuar te\u0308 menqur, mund te\u0308 banohet dhe madje te\u0308 punohet me Ballooning.<\/p>\n

Se bashku me VMware Tools, ne VM instalohen nje drejtuese e ve\u00e7ante, e njohur si Balloon Driver (po ashtu dhe vmmemctl). Kur hypervisor-i fillon te\u0308 kete problemin e mungeses se memories fizike dhe kalon ne gjendjen Soft, ESXi i kerkon VM-se te ktheje memorien operativ te pane\u0308p\u00ebrdorur permes ketij Balloon Driver. Drejtuesi, n\u00eb an\u00ebn tjet\u00ebr, funksionon ne nivelin e sistemit operativ dhe kerkon memorien e lir\u00eb nga ai. Hypervisor-i sheh se cilat faqe te memories fizike ka zene Balloon Driver, merr memorien nga makina virtuale dhe ia kthen hostit. Probleme me funksionimin e sistemit operativ nuk ndodhin, pasi ne nivelin e sistemit operativ memoria \u00ebsht\u00eb e zene nga Balloon Driver. N\u00eb m\u00ebnyr\u00eb t\u00eb paracaktuar, Balloon Driver mund t\u00eb marr\u00eb deri n\u00eb 65% t\u00eb memories s\u00eb VM-s\u00eb.<\/p>\n

N\u00ebse VMware Tools nuk jan\u00eb instaluar n\u00eb VM ose Ballooning \u00ebsht\u00eb \u00e7aktivizuar (nuk e rekomandoj, por ka KB<\/a><\/noindex>:), hypervisor-i kalon menj\u00ebher\u00eb n\u00eb teknika m\u00eb t\u00eb rrepta p\u00ebr t\u00eb marr\u00eb memorien. P\u00ebrfundimi: siguroni q\u00eb VMware Tools t\u00eb jen\u00eb n\u00eb VM.<\/p>\n

\"Analiza
\nFunksionimin e Balloon Driver-it mund ta kontrolloni nga OS p\u00ebrmes VMware Tools.<\/i>.<\/p>\n

Kompresimi i Memories.<\/b> Kjo teknik\u00eb aplikohet kur ESXi arrin n\u00eb gjendjen Hard. Si\u00e7 dallohet nga emri, ESXi p\u00ebrpiqet t\u00eb comprimoj\u00eb nj\u00eb faqe 4 KB t\u00eb memories operativ n\u00eb 2 KB dhe n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb t\u00eb liroj\u00eb pak hap\u00ebsir\u00eb n\u00eb memorien fizike t\u00eb serverit. Kjo teknik\u00eb ndjesh\u00ebm rrit koh\u00ebn e qasjes n\u00eb p\u00ebrmbajtjen e faqeve t\u00eb memories operativ t\u00eb VM-s\u00eb, pasi faqeja duhet t\u00eb dekompresohet paraprakisht. Ndonj\u00ebher\u00eb nuk arrin t\u00eb comprimoj\u00eb t\u00eb gjitha faqe dhe vet\u00eb procesi merr disa koh\u00eb. K\u00ebshtu q\u00eb kjo teknik\u00eb nuk \u00ebsht\u00eb shum\u00eb efektive n\u00eb praktik\u00eb.<\/p>\n

Ndryshimi i Memories.<\/b> Pas nj\u00eb faze t\u00eb shpejt\u00eb t\u00eb Kompresimit t\u00eb Memories, ESXi pothuajse pa p\u00ebrjashtim (n\u00ebse VM-t\u00eb nuk jan\u00eb zhvendosur n\u00eb host t\u00eb tjer\u00eb ose nuk jan\u00eb fikur) kalon n\u00eb Ndryshim. Dhe n\u00ebse mbetet shum\u00eb pak memorje (gjendja e Ul\u00ebt), at\u00ebher\u00eb hypervisor-i gjithashtu ndalon akordimin e faqeve t\u00eb memories p\u00ebr VM, e cila mund t\u00eb shkaktoj\u00eb probleme n\u00eb sistemet operative mikprit\u00ebse t\u00eb VM-s\u00eb.<\/p>\n

K\u00ebtu \u00ebsht\u00eb si funksionon Swapping. Kur aktivizohet makina virtuale, krijohet nj\u00eb skedar me zgjerimin .vswp. Sip\u00ebrfaqja e tij \u00ebsht\u00eb e barabart\u00eb me memorien e pap\u00ebrdorur RAM t\u00eb VM-s\u00eb: kjo \u00ebsht\u00eb diferenca midis memorjes s\u00eb konfiguruar dhe asaj t\u00eb rezervuar. Kur funksionon Swapping, ESXi shkarkon faqet e memorjes s\u00eb makin\u00ebs virtuale n\u00eb k\u00ebt\u00eb skedar dhe fillon t\u00eb punoj\u00eb me t\u00eb n\u00eb vend t\u00eb memorjes fizike t\u00eb serverit. Natyrisht, nj\u00eb memorie e till\u00eb \u201caktive\u201d \u00ebsht\u00eb disa her\u00eb m\u00eb e ngadalshme se e v\u00ebrteta, edhe n\u00ebse .vswp ndodhet n\u00eb nj\u00eb magazin\u00eb t\u00eb shpejt\u00eb.<\/p>\n

N\u00eb dallim nga Ballooning, kur VM-s\u00eb i nd\u00ebrpriten faqet e panjohura, gjat\u00eb Swapping-ut mund t\u00eb kalojn\u00eb n\u00eb disk faqet q\u00eb p\u00ebrdoren aktivisht nga OS ose aplikacionet brenda VM-s\u00eb. Si rezultat, performanca e VM-s\u00eb bie deri n\u00eb ngecje. VM-ja operon formalisht dhe mund t\u00eb \u00e7\u2019aktivizohet si\u00e7 duhet nga OS. N\u00ebse jeni t\u00eb duruesh\u00ebm \ud83d\ude09<\/p>\n

N\u00ebse VM-t\u00eb kalojn\u00eb n\u00eb Swap \u2014 kjo \u00ebsht\u00eb nj\u00eb situat\u00eb e papast\u00ebr q\u00eb duhet t\u00eb shmanget sa m\u00eb shum\u00eb t\u00eb jet\u00eb e mundur.<\/p>\n

Numrat kryesor\u00eb t\u00eb performanc\u00ebs s\u00eb memorjes s\u00eb makin\u00ebs virtuale<\/h3>\n

\nK\u00ebtu erdh\u00ebm n\u00eb t\u00ebr\u00ebsin\u00eb. P\u00ebr monitorimin e gjendjes s\u00eb memorjes n\u00eb VM ka k\u00ebta numra:<\/p>\n

Aktiv<\/b> \u2014 tregon v\u00ebllimin e memorjes RAM (Kbyte), t\u00eb cil\u00ebs VM-ja i kishte qasje n\u00eb periudh\u00ebn e m\u00ebparshme t\u00eb matjes.<\/p>\n

P\u00ebrdorimi<\/b> \u2014 e nj\u00ebjta si Aktiv, por n\u00eb p\u00ebrqindje t\u00eb memorjes s\u00eb konfiguruar t\u00eb VM-s\u00eb. Llogaritet me formul\u00ebn e m\u00ebposhtme: aktiv \u00f7 madh\u00ebsia e memorie t\u00eb konfiguruar t\u00eb makin\u00ebs virtuale.
\nNj\u00eb Usage dhe Aktiv t\u00eb larta, p\u00ebrkat\u00ebsisht, nuk jan\u00eb gjithmon\u00eb tregues t\u00eb problemeve t\u00eb performanc\u00ebs s\u00eb VM-s\u00eb. N\u00ebse VM-ja p\u00ebrdor agresivisht memorjen (t\u00eb pakt\u00ebn ka qasje n\u00eb t\u00eb), kjo nuk do t\u00eb thot\u00eb se ka munges\u00eb memorjeje. M\u00eb tep\u00ebr, kjo \u00ebsht\u00eb nj\u00eb mund\u00ebsi p\u00ebr t\u00eb par\u00eb se \u00e7far\u00eb ndodh n\u00eb OS.
\nKa nj\u00eb Alarm standard p\u00ebr P\u00ebrdorimin e Memorjes p\u00ebr VM:<\/p>\n

\"Analiza
\n
\nShared<\/b> \u2014 v\u00ebllimi i memorjes RAM t\u00eb VM-s\u00eb, e cila \u00ebsht\u00eb e deduplicuar me ndihm\u00ebn e TPS (brenda VM-s\u00eb ose nd\u00ebrmjet VM-ve).<\/p>\n

E dh\u00ebn\u00eb<\/b> \u2014 v\u00ebllimi i memorjes fizike t\u00eb hostit (Kbyte), e cila iu dha VM-s\u00eb. P\u00ebrfshin t\u00eb ndar\u00eb.<\/p>\n

E konsumuar<\/b> (E dh\u00ebn\u00eb \u2014 E ndar\u00eb) \u2014 v\u00ebllimi i memorjes fizike (Kbyte), q\u00eb VM-ja e konsumon nga hosti. Nuk p\u00ebrfshin t\u00eb ndar\u00eb.<\/p>\n

N\u00ebse nj\u00eb pjes\u00eb e memorjes s\u00eb VM-s\u00eb jepet jo nga memoria fizike e hostit, por nga skedari swap ose memorja merret nga VM-ja p\u00ebrmes Balloon Driver, ky v\u00ebllim nuk merret parasysh n\u00eb E dh\u00ebn\u00eb dhe t\u00eb konsumuar.
\nVlerat e larta t\u00eb Granted dhe Consumed jan\u00eb krejt\u00ebsisht normale. Sistemi operativ gradualisht merr kujtes\u00ebn nga hiper-vizori dhe nuk e kthen at\u00eb p\u00ebrs\u00ebri. Me kalimin e koh\u00ebs, p\u00ebr VM-n\u00eb e cila punon aktivisht, vlerat e k\u00ebtyre numrit afroheshin me volumet e memorjes s\u00eb konfiguruar, dhe aty mbeten.<\/p>\n

Zero<\/b> \u2014 volumi i memorjes RAM t\u00eb VM-s\u00eb (KB), e cila p\u00ebrmban zero. Kjo memorie konsiderohet nga hiper-vizori si e lir\u00eb dhe mund t\u00eb jepet p\u00ebr VM t\u00eb tjera. Pasi sistemi operativ mik i ka shkruar di\u00e7ka n\u00eb memorjen e z\u00ebvend\u00ebsuar, kalon n\u00eb Consumed dhe nuk kthehet m\u00eb.<\/p>\n

Reserved Overhead<\/b> \u2014 volumi i memorjes RAM t\u00eb VM-s\u00eb (KB) i rezervuar nga hiper-vizori p\u00ebr operimin e VM-s\u00eb. Ky \u00ebsht\u00eb nj\u00eb volum i vog\u00ebl, por duhet patjet\u00ebr t\u00eb jet\u00eb n\u00eb dispozicion n\u00eb host, nd otherwise VM nuk do t\u00eb nis.<\/p>\n

Balloon<\/b> \u2014 volumi i memorjes RAM (KB) e cila \u00ebsht\u00eb marr\u00eb nga VM p\u00ebrmes Balloon Driver.<\/p>\n

Compressed<\/b> \u2014 volumi i memorjes RAM (KB) q\u00eb arriti t\u00eb kompresohej.<\/p>\n

Swapped<\/b> \u2014 volumi i memorjes RAM (KB) e cila p\u00ebr shkak t\u00eb munges\u00ebs s\u00eb kujtes\u00ebs fizike n\u00eb server \u00ebsht\u00eb transferuar n\u00eb disk.
\nBalloon dhe numrat e tjer\u00eb t\u00eb teknikave t\u00eb rikuperimit t\u00eb memories jan\u00eb t\u00eb barabart\u00eb me zero.<\/p>\n

K\u00ebtu \u00ebsht\u00eb si duket grafiku me numrat e memories p\u00ebr nj\u00eb VM t\u00eb pun\u00ebs normale me 150 GB RAM.<\/p>\n

\"Analiza
\n
\nN\u00eb grafikun m\u00eb posht\u00eb, VM ka probleme t\u00eb dukshme. N\u00ebn grafik shikohet se p\u00ebr k\u00ebt\u00eb VM jan\u00eb p\u00ebrdorur t\u00eb gjitha teknik\u00ebs e p\u00ebrshkruara n\u00eb lidhje me kujtes\u00ebn. Balloon p\u00ebr k\u00ebt\u00eb VM \u00ebsht\u00eb shum\u00eb m\u00eb i madh se Consumed. N\u00eb fakt, VM \u00ebsht\u00eb m\u00eb shum\u00eb e vdekur sesa e gjall\u00eb. <\/p>\n

\"Analiza
\n<\/p>\n

ESXTOP<\/h3>\n

\nSi me CPU-n\u00eb, n\u00ebse duam t\u00eb vler\u00ebsojm\u00eb situat\u00ebn n\u00eb host menj\u00ebher\u00eb dhe gjithashtu dinamik\u00ebn e saj me intervale deri n\u00eb 2 sekonda, \u00ebsht\u00eb mir\u00eb t\u00eb p\u00ebrdorim ESXTOP.<\/p>\n

Ekrani ESXTOP p\u00ebr Memory thirret me \u00e7el\u00ebsin 'm' dhe duket si m\u00eb posht\u00eb (k\u00ebtu jan\u00eb zgjedhur fushat B,D,H,J,K,L,O):<\/p>\n

\"Analiza
\n
\nParametrat m\u00eb t\u00eb r\u00ebnd\u00ebsish\u00ebm p\u00ebr ne do t\u00eb jen\u00eb si m\u00eb posht\u00eb: <\/p>\n

Mem overcommit avg<\/b> \u2014 vlera mesatare e mbishkruar e memories n\u00eb host p\u00ebr 1, 5 dhe 15 minuta. N\u00ebse \u00ebsht\u00eb m\u00eb e lart\u00eb se zero, kjo \u00ebsht\u00eb nj\u00eb arsye p\u00ebr t\u00eb par\u00eb se \u00e7far\u00eb po ndodh, por nuk \u00ebsht\u00eb gjithmon\u00eb tregues i problemeve.<\/p>\n

N\u00eb rreshtat PMEM\/MB<\/b> dhe VMKMEM\/MB<\/b> \u2014 informacion rreth memories fizike t\u00eb serverit dhe memories t\u00eb disponueshme p\u00ebr VMkernel. Nga e r\u00ebnd\u00ebsishmja k\u00ebtu mund t\u00eb shikohet vlera minfree (n\u00eb MB), gjendja e hostit p\u00ebr kujtes\u00ebn (n\u00eb rastin ton\u00eb, e lart\u00eb).<\/p>\n

N\u00eb rreshtin NUMA\/MB<\/b> mund t\u00eb shikohet shp\u00ebrndarja e memories RAM sipas NUMA-nodave (socket\u00ebve). N\u00eb k\u00ebt\u00eb shembull, shp\u00ebrndarja \u00ebsht\u00eb e pabarabart\u00eb, q\u00eb n\u00eb thelb nuk \u00ebsht\u00eb shum\u00eb mir\u00eb.<\/p>\n

M\u00eb posht\u00eb jan\u00eb statistikat e p\u00ebrgjithshme p\u00ebr serverin mbi teknikat e rikuperimit t\u00eb memories:<\/p>\n

PSHARE\/MB<\/b> \u2014 kjo \u00ebsht\u00eb statistika e TPS;<\/p>\n

SWAP\/MB<\/b> \u2014 statistika e p\u00ebrdorimit t\u00eb Swap;<\/p>\n

ZIP\/MB<\/b> \u2014 statistika e kompresionit t\u00eb faqeve t\u00eb memories;<\/p>\n

MEMCTL\/MB<\/b> \u2014 statistika e p\u00ebrdorimit t\u00eb Balloon Driver.<\/p>\n

P\u00ebr \u00e7do VM t\u00eb ve\u00e7ant\u00eb, mund t\u00eb na interesoj\u00eb informacioni n\u00eb vijim. Emrat e VM-s\u00eb i kam fshhur, p\u00ebr t\u00eb mos e shqet\u00ebsuar audienc\u00ebn :). N\u00ebse metrika ESXTOP \u00ebsht\u00eb e ngjashme me num\u00ebruesin n\u00eb vSphere, po sjell num\u00ebruesin p\u00ebrkat\u00ebs. <\/p>\n

MEMSZ<\/b> \u2014 sasia e memories, e konfiguruar n\u00eb VM (MB).
\nMEMSZ = GRANT + MCTLSZ + SWCUR + untouched.<\/p>\n

GRANT<\/b> \u2014 Granted n\u00eb megabajt.<\/p>\n

TCHD<\/b> \u2014 Active n\u00eb megabajt.<\/p>\n

MCTL?<\/b> \u2014 a \u00ebsht\u00eb e instaluar Balloon Driver n\u00eb VM.<\/p>\n

MCTLSZ<\/b> \u2014 Balloon n\u00eb megabajt.<\/p>\n

MCTLGT<\/b> \u2014 sasia e memories RAM (megabajt), e cila ESXi do t\u00eb d\u00ebshiroj\u00eb ta t\u00ebrheq\u00eb nga VM p\u00ebrmes Balloon Driver (Memctl Target).<\/p>\n

MCTLMAX<\/b> \u2014 sasia maksimale e memories RAM (megabajt), e cila ESXi mund ta t\u00ebrheq\u00eb nga VM p\u00ebrmes Balloon Driver.<\/p>\n

SWCUR<\/b> \u2014 sasia aktuale e memories RAM (megabajt), e dh\u00ebn\u00eb VM nga skedari Swap. <\/p>\n

SWGT<\/b> \u2014 sasia e memories RAM (megabajt), e cila ESXi d\u00ebshiron t\u00eb jap\u00eb VM nga skedari Swap (Swap Target).<\/p>\n

Gjithashtu p\u00ebrmes ESXTOP mund t\u00eb shihni m\u00eb shum\u00eb informacion mbi topologjin\u00eb NUMA t\u00eb VM. P\u00ebr k\u00ebt\u00eb \u00ebsht\u00eb e nevojshme t\u00eb zgjidhen fushat D,G:<\/p>\n

\"Analiza
\n
\nNHN<\/b> \u2013 nyjat NUMA, n\u00eb t\u00eb cilat ndodhet VM. K\u00ebtu mund ta vini re VM t\u00eb gj\u00ebr\u00eb q\u00eb nuk i p\u00ebrputhen nj\u00eb nyje NUMA.<\/p>\n

NRMEM<\/b> \u2013 sa megabajt memories VM merr nga nj\u00eb nyj\u00eb NUMA t\u00eb distancuar.<\/p>\n

NLMEM<\/b> \u2013 sa megabajt memories VM merr nga nj\u00eb nyj\u00eb NUMA lokale.<\/p>\n

N%L<\/b> \u2013 p\u00ebrqindja e memories VM n\u00eb nyj\u00ebn NUMA lokale (n\u00ebse \u00ebsht\u00eb m\u00eb pak se 80% \u2014 mund t\u00eb ket\u00eb probleme me performanc\u00ebn).<\/p>\n

Memoria n\u00eb hypervisor<\/h3>\n

\nN\u00ebse num\u00ebruesit e CPU-s\u00eb n\u00eb hypervisor zakonisht nuk paraqesin interes t\u00eb ve\u00e7ant\u00eb, situata me memory \u00ebsht\u00eb e kund\u00ebrt. P\u00ebrdorimi i Lart\u00eb i Memories n\u00eb VM nuk tregon gjithmon\u00eb p\u00ebr nj\u00eb problem me performanc\u00ebn, por nj\u00eb P\u00ebrdorim i Lart\u00eb i Memories n\u00eb hypervisor, n\u00eb fakt aktivizon teknikat e menaxhimit t\u00eb memories dhe shkakton probleme me performanc\u00ebn e VM. Duhet t\u00eb monitoroni alarmin e P\u00ebrdorimit t\u00eb Memories n\u00eb Host dhe t\u00eb mos lejoni q\u00eb VM t\u00eb kaloj\u00eb n\u00eb Swap.<\/p>\n

\"Analiza
\n
\n\"Analiza
\n<\/p>\n

Unswap<\/h3>\n

\nN\u00ebse VM kalon n\u00eb Swap, performanca e saj zvog\u00eblohet ndjesh\u00ebm. Shkall\u00ebt e Ballooning dhe kompresionit shuhen shpejt pas shfaqjes s\u00eb memories RAM t\u00eb lir\u00eb n\u00eb host, por VM nuk nxiton aspak t\u00eb kthehet nga Swap n\u00eb memories RAM t\u00eb serverit.
\nDeri n\u00eb versionin ESXi 6.0, m\u00ebnyra e vetme e besueshme dhe e shpejt\u00eb p\u00ebr t\u00eb nxjerr\u00eb VM nga Swap ishte rinisja (n\u00ebse jemi m\u00eb t\u00eb sakt\u00eb, fikja\/nisja e kontejnerit). Q\u00eb nga ESXi 6.0 ka dal\u00eb nj\u00eb m\u00ebnyr\u00eb, edhe pse jo plot\u00ebsisht zyrtare, por e punueshme dhe e besueshme p\u00ebr t\u00eb nxjerr\u00eb VM nga Swap. N\u00eb nj\u00eb nga konferencat, pata mund\u00ebsin\u00eb t\u00eb bisedoj me nj\u00eb nga inxhinier\u00ebt e VMware q\u00eb ishte p\u00ebrgjegj\u00ebs p\u00ebr CPU Scheduler. Ai konfirmoi se m\u00ebnyra \u00ebsht\u00eb me t\u00eb v\u00ebrtet\u00eb funksionale dhe e sigurt. N\u00eb p\u00ebrvoj\u00ebn ton\u00eb, nuk kemi v\u00ebn\u00eb re probleme me t\u00eb.<\/p>\n

Komandat p\u00ebr t\u00eb nxjerr\u00eb VM nga Swap p\u00ebrshkroi<\/a><\/noindex> Duncan Epping. Nuk do t\u00eb p\u00ebrs\u00ebris p\u00ebrshkrimin e detajuar, thjesht do t'ju jap nj\u00eb shembull t\u00eb p\u00ebrdorimit t\u00eb saj. Si\u00e7 shihet n\u00eb screenshot, pas nj\u00eb periudhe pas ekzekutimit t\u00eb komand\u00ebs t\u00eb cituar, Swap n\u00eb VM zhduket.<\/p>\n

\"Analiza
\n<\/p>\n

K\u00ebshilla p\u00ebr menaxhimin e memories n\u00eb ESXi<\/h3>\n

\nN\u00eb fund, do t\u00eb jap disa k\u00ebshilla q\u00eb do t'ju ndihmojn\u00eb t\u00eb shmangni probleme me performanc\u00ebn e VM p\u00ebr shkak t\u00eb memories:<\/p>\n