{"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 CPU-s\u00eb<\/a><\/noindex><\/p>\n

N\u00eb k\u00ebt\u00eb artikull, do t\u00eb flasim p\u00ebr numrat e performanc\u00ebs s\u00eb memories s\u00eb aksionit (RAM) n\u00eb vSphere.
\nDuket se me memorien gjith\u00e7ka \u00ebsht\u00eb m\u00eb e qart\u00eb sesa me procesorin: n\u00ebse VM ka probleme me performanc\u00ebn, \u00ebsht\u00eb e v\u00ebshtir\u00eb t'i shmangesh. Por, n\u00ebse ndodhin, \u00ebsht\u00eb shum\u00eb m\u00eb e v\u00ebshtir\u00eb t\u00eb merren n\u00eb kontroll. Por le t\u00eb fillojm\u00eb nga fillimi. <\/a><\/noindex><\/p>\n

Pak teori<\/h3>\n

\nMemoria aksionit e makinave virtuale merret nga memoria e server\u00ebve mbi t\u00eb cil\u00ebt operojn\u00eb VM-t\u00eb. Kjo \u00ebsht\u00eb krejt e qart\u00eb:). N\u00ebse nuk ka mjaft memorie t\u00eb serverit p\u00ebr t\u00eb gjith\u00eb ata q\u00eb k\u00ebrkojn\u00eb, ESXi fillon t\u00eb aplikoje teknikat e optimizimit t\u00eb konsumit t\u00eb memories (memory reclamation techniques). Ndryshe, sistemet operative t\u00eb VM-ve do t\u00eb binin me gabime n\u00eb qasje n\u00eb RAM. <\/p>\n

N\u00ebse cilat teknika t\u00eb p\u00ebrdor\u00eb ESXi varet nga ngarkesa e memories:<\/p>\n

Shteti i memories<\/b><\/p>\n

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

Veprime<\/b><\/p>\n

E Lart\u00eb<\/p>\n

400% nga minFree<\/p>\n

Pasi arrihet kufiri i sip\u00ebrm, faqe t\u00eb m\u00ebdha t\u00eb memories ndahen n\u00eb t\u00eb vogla (TPS funksionon n\u00eb modin 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 detyrim.<\/p>\n

E Zbutur<\/p>\n

64% nga minFree<\/p>\n

TPS + Balloon<\/p>\n

E Fort\u00eb<\/p>\n

32% e minFree<\/p>\n

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

I ul\u00ebt<\/p>\n

16% e minFree<\/p>\n

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

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

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

Derisa t\u00eb ESXi 4.1, minFree ishte n\u00eb p\u00ebrqindje fikse prej 6% t\u00eb volumit t\u00eb memorjes RAM t\u00eb serverit (p\u00ebrqindja mund t\u00eb ndryshohej p\u00ebrmes opsionit Mem.MinFreePct n\u00eb ESXi). N\u00eb versionet m\u00eb t\u00eb vonshme, p\u00ebr shkak t\u00eb rritjes s\u00eb volumit t\u00eb memories n\u00eb servera, minFree filloi t\u00eb llogaritej n\u00eb baz\u00eb t\u00eb volumit t\u00eb memories s\u00eb hostit dhe jo si nj\u00eb vler\u00eb p\u00ebrqindje fikse. <\/p>\n

Vlera minFree (n\u00eb p\u00ebrllogaritje t\u00eb default-it) llogaritet si m\u00eb posht\u00eb:<\/p>\n

P\u00ebrqindja e 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 jet\u00eb si m\u00eb posht\u00eb:
\nMinFree = 245,76 + 327,68 + 327,68 + 1024 = 1925,12 MB = 1,88 GB
\nVlera e v\u00ebrtet\u00eb mund t\u00eb ndryshoj\u00eb p\u00ebr disa qindra MB, kjo varet nga serveri dhe memoria RAM.<\/p>\n

P\u00ebrqindja e 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 ambientes produktiv, gjendja normale konsiderohet vet\u00ebm e lart\u00eb. P\u00ebr ambiente testi dhe zhvillimi, gjendjet e pastra ose t\u00eb buta mund t\u00eb jen\u00eb t\u00eb pranueshme. N\u00ebse kujtesa operative n\u00eb host ka mbetur m\u00eb pak se 64% MinFree, at\u00ebher\u00eb VM-t\u00eb q\u00eb funksionojn\u00eb mbi t\u00eb, me siguri do t\u00eb p\u00ebrjetojn\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, q\u00eb ka nj\u00eb ndikim praktikisht t\u00eb pap\u00ebrfillsh\u00ebm n\u00eb performanc\u00ebn e VM-ve, deri tek swapping. Do ta shpjegoj m\u00eb holl\u00ebsisht. <\/p>\n

Transparent Page Sharing (TPS).<\/b> TPS \u00ebsht\u00eb, n\u00eb thelb, deduplikimi i faqeve t\u00eb memories operative t\u00eb makinave virtuale n\u00eb server.<\/p>\n

ESXi k\u00ebrkon faqe t\u00eb nj\u00ebjta t\u00eb memories operative t\u00eb makinave virtuale, duke llogaritur dhe duke krahasuar hash-imazhet e faqeve, dhe i heq dublikimet e faqeve, duke i z\u00ebvend\u00ebsuar ato me lidhje n\u00eb nj\u00eb faqe t\u00eb vetme n\u00eb memories fizike t\u00eb serverit. Si rezultat, konsumimi i memories fizike ulet dhe \u00ebsht\u00eb e mundur t\u00eb arrihet nj\u00eb rip\u00ebrshkrim i caktuar t\u00eb memories thuajse pa ulje t\u00eb performanc\u00ebs.<\/p>\n

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

Ky ky mekaniz\u00ebm funksionon vet\u00ebm p\u00ebr faqet e memories me dimensionin 4 KB (faqet e vogla). Faqet me dimensionin 2 MB (faqet e m\u00ebdha) hiper-vizori nuk p\u00ebrpiqet t\u00eb deduplikoj\u00eb: shansi p\u00ebr t\u00eb gjetur faqe t\u00eb ngjashme t\u00eb k\u00ebtij p\u00ebrmas\u00eb nuk \u00ebsht\u00eb i lart\u00eb.<\/p>\n

N\u00eb m\u00ebnyr\u00eb t\u00eb paracaktuar, ESXi alokon memorie p\u00ebr faqet e m\u00ebdha. \u00c7ar\u00e7afimi i faqeve t\u00eb m\u00ebdha n\u00eb t\u00eb vogla fillon kur arrihet pragu i gjendjes High dhe ndodh me detyrim, kur arrihet gjendja Clear (shih tabel\u00ebn e gjendjeve t\u00eb hiper-vizorit).<\/p>\n

N\u00ebse d\u00ebshironi q\u00eb TPS t\u00eb filloj\u00eb pun\u00ebn pa pritur mbushjen e memories operuese t\u00eb hostit, n\u00eb Opsionet e Avancuara t\u00eb ESXi duhet t\u00eb vendosni vler\u00ebn \u201cMem.AllocGuestLargePage\u201d<\/i> n\u00eb 0 (p\u00ebr parazgjedhje \u00ebsht\u00eb 1). At\u00ebher\u00eb alokimi i faqeve t\u00eb m\u00ebdha t\u00eb memories p\u00ebr makinat virtuale do t\u00eb \u00e7aktivizohet.<\/p>\n

Q\u00eb nga dhjetori 2014, n\u00eb t\u00eb gjitha l\u00ebshimet e ESXi, TPS midis VM-ve \u00ebsht\u00eb \u00e7aktivizuar si parazgjedhje, pasi u gjet nj\u00eb dob\u00ebsi, e cila teorikisht lejon aksesin e memories operuese t\u00eb nj\u00eb VM-je nga nj\u00eb tjet\u00ebr VM. Detajet k\u00ebtu. Nuk kam hasur informacione mbi implementimin 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 faqet midis VM-ve;
\n1 \u2013 TPS p\u00ebr VM me vlera t\u00eb nj\u00ebjta \"sched.mem.pshare.salt\" n\u00eb VMX;
\n2 (n\u00eb m\u00ebnyr\u00eb default) \u2013 Intra-VM TPS. TPS funksionon p\u00ebr faqet brenda VM.<\/p>\n

Dhe sigurisht ka kuptim t\u00eb fikni faqet e m\u00ebdha dhe t\u00eb aktivizoni Inter-VM TPS n\u00eb ambientet testuese. Kjo gjithashtu mund t\u00eb p\u00ebrdoret p\u00ebr ambiente me shum\u00eb VM t\u00eb homogjene. P\u00ebr shembull, n\u00eb ambientet me VDI, kursimi i memories fizike mund t\u00eb arrij\u00eb dhjetra p\u00ebrqind. <\/p>\n

Memory Ballooning.<\/b> Ballooning nuk \u00ebsht\u00eb m\u00eb nj\u00eb teknik\u00eb kaq e pad\u00ebmshme dhe transparente p\u00ebr sistemin operativ t\u00eb VM-s\u00eb si TPS. Por me p\u00ebrdorim t\u00eb men\u00e7ur, mund t\u00eb jetosh dhe madje t\u00eb punosh me Ballooning.<\/p>\n

Bashk\u00eb me Vmware Tools, n\u00eb VM instalohet nj\u00eb drejtp\u00ebrdrejt\u00eb t\u00eb ve\u00e7ant\u00eb, e quajtur Balloon Driver (ose vmmemctl). Kur hypervisor-i fillon t\u00eb ket\u00eb munges\u00eb t\u00eb memories fizike dhe kalon n\u00eb gjendjen Soft, ESXi k\u00ebrkon nga VM t\u00eb kthej\u00eb memorin\u00eb e pacaktuar p\u00ebrmes k\u00ebtij Balloon Driver. Drejtp\u00ebrdrejt\u00eb, nga ana e tij, punon n\u00eb nivelin e sistemit operativ dhe k\u00ebrkon memori t\u00eb lir\u00eb prej tij. Hypervisor-i sheh se cilat faqe t\u00eb memories fizike jan\u00eb z\u00ebn\u00eb nga Balloon Driver, merr memorien nga makina virtuale dhe ia kthen hostit. Problemet me funksionimin e OS-s\u00eb nuk ndodhin, pasi n\u00eb nivelin e OS-s\u00eb memoria \u00ebsht\u00eb e z\u00ebn\u00eb nga Balloon Driver. Me default, Balloon Driver-i mund t\u00eb marr\u00eb deri n\u00eb 65% t\u00eb memories s\u00eb VM-s\u00eb.<\/p>\n

N\u00ebse n\u00eb VM nuk jan\u00eb instaluar VMware Tools ose \u00ebsht\u00eb \u00e7aktivizuar Ballooning (nuk e rekomandoj, por ka KB<\/a><\/noindex>:), hypervisor-i kalon menj\u00ebher\u00eb n\u00eb teknikat m\u00eb t\u00eb ashpra t\u00eb marrjes s\u00eb memories. P\u00ebrfundimi: sigurohuni 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

Memory Compression.<\/b> Kjo teknik\u00eb aplikohet kur ESXi arrin nj\u00eb gjendje Hard. Si\u00e7 e tregon emri, ESXi p\u00ebrpiqet t\u00eb comprimoj\u00eb nj\u00eb faqe prej 4 KB t\u00eb memories RAM n\u00eb 2 KB, duke \u00e7liruar k\u00ebshtu pak hap\u00ebsir\u00eb n\u00eb memorien fizike t\u00eb serverit. Kjo teknik\u00eb rrit ndjesh\u00ebm koh\u00ebn e qasjes n\u00eb p\u00ebrmbajtjen e faqeve t\u00eb memories s\u00eb VM, pasi faqa duhet t\u00eb shfletohet paraprakisht. Ndonj\u00ebher\u00eb, jo t\u00eb gjitha faqet mund t\u00eb comprimojn\u00eb dhe procesi merr disa koh\u00eb. Prandaj, kjo teknik\u00eb n\u00eb praktik\u00eb nuk \u00ebsht\u00eb shum\u00eb e efektshme.<\/p>\n

Memory Swapping.<\/b> Pas nj\u00eb faze t\u00eb shkurt\u00ebr t\u00eb Memory Compression, ESXi pothuajse pa p\u00ebrjashtim (n\u00ebse VM-t\u00eb nuk jan\u00eb transferuar n\u00eb hoste t\u00eb tjera ose nuk jan\u00eb fikur) kalon n\u00eb Swapping. Dhe n\u00ebse ka mbetur shum\u00eb pak memorie (gjendja Low), at\u00ebher\u00eb hipervizori gjithashtu ndalon ndarjen e faqeve t\u00eb memories p\u00ebr VM, gj\u00eb q\u00eb mund t\u00eb shkaktoj\u00eb probleme n\u00eb OS-t\u00eb mikprit\u00ebse t\u00eb VM.<\/p>\n

Ja si funksionon Swapping. Kur ndizet makina virtuale, krijohet nj\u00eb skedar me zgjatjen .vswp. Me madh\u00ebsi, ai \u00ebsht\u00eb i barabart\u00eb me memorien e papreanuar t\u00eb VM-s\u00eb: kjo \u00ebsht\u00eb diferenca midis memories t\u00eb konfiguruar dhe asaj t\u00eb rezervuar. Kur Swapping funksionon, ESXi shkarkon faqet e memories 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 memories fizike t\u00eb serverit. Natyrisht, kjo \u00abmemorie\u00bb \u00ebsht\u00eb disa her\u00eb m\u00eb e ngadalshme se e v\u00ebrteta, edhe n\u00ebse .vswp ndodhet n\u00eb nj\u00eb ruajtje t\u00eb shpejt\u00eb.<\/p>\n

Ndryshe nga Ballooning, kur VM-s\u00eb i ndahen faqet e p\u00ebrdorura, gjat\u00eb Swapping mund t\u00eb kalojn\u00eb n\u00eb disk faqet q\u00eb p\u00ebrdoren aktivisht nga OS ose aplikacionet brenda VM-s\u00eb. Si pasoj\u00eb, performanca e VM-s\u00eb bjen deri n\u00eb pezullim. VM-ja funksionon formalisht dhe ajo mund t\u00eb fiket sakt\u00ebsisht nga OS. N\u00ebse do t\u00eb shfaqni durim \ud83d\ude09<\/p>\n

N\u00ebse VM-t\u00eb kan\u00eb kaluar n\u00eb Swap \u2014 kjo \u00ebsht\u00eb nj\u00eb situat\u00eb jo t\u00eb zakonshme q\u00eb p\u00ebr t\u00eb \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb shmanget sa m\u00eb shum\u00eb t\u00eb jet\u00eb e mundur.<\/p>\n

Kontrollor\u00ebt kryesor\u00eb t\u00eb performanc\u00ebs s\u00eb memories s\u00eb makin\u00ebs virtuale<\/h3>\n

\nJa ku arrit\u00ebm n\u00eb t\u00eb r\u00ebnd\u00ebsishmen. P\u00ebr t\u00eb monitoruar gjendjen e memories n\u00eb VM, ka k\u00ebto kontrollor\u00eb:<\/p>\n

Aktiv<\/b> \u2014 tregon sasin e memories s\u00eb operativ\u00ebs (KB) q\u00eb VM ka pasur akses n\u00eb periudh\u00ebn e m\u00ebparshme t\u00eb matjes.<\/p>\n

P\u00ebrdorimi<\/b> \u2014 e nj\u00ebjt\u00eb si Active, por n\u00eb p\u00ebrqindje t\u00eb memories s\u00eb operativ\u00ebs s\u00eb konfiguruar t\u00eb VM. Llogaritet sipas formul\u00ebs: active \u00f7 madh\u00ebsia e memories s\u00eb konfiguruar t\u00eb makin\u00ebs virtuale.
\nNj\u00eb p\u00ebrdorim dhe aktiv t\u00eb lart\u00eb, p\u00ebrkat\u00ebsisht, nuk jan\u00eb gjithmon\u00eb tregues t\u00eb problemeve t\u00eb performanc\u00ebs s\u00eb VM. N\u00ebse VM p\u00ebrdor agresivisht memorjen (t\u00eb pakt\u00ebn, ka akses n\u00eb t\u00eb), kjo nuk do t\u00eb thot\u00eb se ka nevoj\u00eb p\u00ebr m\u00eb shum\u00eb memorie. M\u00eb tep\u00ebr, \u00ebsht\u00eb nj\u00eb arsye p\u00ebr t\u00eb par\u00eb se \u00e7far\u00eb po ndodh n\u00eb OS.
\nKa nj\u00eb Alarm standard p\u00ebr P\u00ebrdorimin e Memories p\u00ebr VM:<\/p>\n

\"Analiza
\n
\nShared<\/b> \u2014 sasia e memories s\u00eb operativ\u00ebs t\u00eb VM, e deduplicuar p\u00ebrmes TPS (brenda VM-\u00ebs ose midis VM-eve).<\/p>\n

E dh\u00ebn\u00eb<\/b> \u2014 sasia e memories fizike t\u00eb hostit (KB), e cila i \u00ebsht\u00eb dh\u00ebn\u00eb VM. P\u00ebrfshin t\u00eb Mirat e P\u00ebrbashk\u00ebta.<\/p>\n

E konsumuar<\/b> (E dh\u00ebn\u00eb \u2014 e p\u00ebrbashk\u00ebt) \u2014 sasia e memories fizike (KB), q\u00eb VM po e konsumon nga hosti. Nuk p\u00ebrfshin t\u00eb Mirat e P\u00ebrbashk\u00ebta.<\/p>\n

N\u00ebse nj\u00eb pjes\u00eb e memories s\u00eb VM i jepet jo nga memoria fizike e hostit, por nga skedari swap ose memoria merret nga VM p\u00ebrmes Balloon Driver, kjo sasi nuk merret parasysh n\u00eb E dh\u00ebn\u00eb dhe E konsumuar.
\nVlerat e larta t\u00eb Granted dhe Consumed jan\u00eb krejt normale. Sistemi operativ gradualisht merr kujtes\u00ebn nga hipervizori dhe nuk e kthen mbrapsht. Me kalimin e koh\u00ebs, p\u00ebr VM-t\u00eb q\u00eb funksionojn\u00eb aktivisht, vlerat e k\u00ebtyre numrave p\u00ebrafrohen me volumet e kujtes\u00ebs t\u00eb konfiguruar, dhe aty mbeten.<\/p>\n

Zero<\/b> \u2014 volumi i kujtes\u00ebs RAM t\u00eb VM (KB), i cili p\u00ebrmban zero. Kjo kujtes\u00eb konsiderohet nga hipervizori si e lir\u00eb dhe mund t'i jepet VM-ve t\u00eb tjera. Pasi sistemi operativ mik ka shkruar di\u00e7ka n\u00eb kujtes\u00ebn e nulizuar, ajo kalon n\u00eb Consumed dhe nuk kthehet m\u00eb mbrapsht.<\/p>\n

Reserved Overhead<\/b> \u2014 volumi i kujtes\u00ebs RAM t\u00eb VM (KB) t\u00eb rezervuar nga hipervizori p\u00ebr funksionimin e VM. Kjo \u00ebsht\u00eb nj\u00eb sasi e vog\u00ebl, por duhet t\u00eb jet\u00eb e pranishme n\u00eb host, p\u00ebrndryshe VM nuk do t\u00eb nis\u00eb.<\/p>\n

Balloon<\/b> \u2014 volumi i kujtes\u00ebs RAM (KB) t\u00eb hequr nga VM me an\u00eb t\u00eb Balloon Driver.<\/p>\n

Compressed<\/b> \u2014 volumi i kujtes\u00ebs RAM (KB) q\u00eb ka arritur t\u00eb kompresohet.<\/p>\n

Swapped<\/b> \u2014 volumi i kujtes\u00ebs RAM (KB) q\u00eb, 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 kujtes\u00ebs jan\u00eb t\u00eb barabart\u00eb me zero.<\/p>\n

K\u00ebshtu duket grafiku me numrat e Memories s\u00eb nj\u00eb VM q\u00eb punon normalisht me 150 GB RAM.<\/p>\n

\"Analiza
\n
\nN\u00eb grafikun m\u00eb posht\u00eb, VM ka probleme t\u00eb dukshme. N\u00ebn grafik, tregohet se p\u00ebr k\u00ebt\u00eb VM jan\u00eb p\u00ebrdorur t\u00eb gjitha teknikat e p\u00ebrshkruara p\u00ebr menaxhimin e memories. Balloon p\u00ebr k\u00ebt\u00eb VM \u00ebsht\u00eb ndjesh\u00ebm m\u00eb i madh se sa Consumed. N\u00eb fakt, VM \u00ebsht\u00eb m\u00eb shum\u00eb e vdekur se sa e gjall\u00eb. <\/p>\n

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

ESXTOP<\/h3>\n

\nSi me CPU, n\u00ebse duam t\u00eb vler\u00ebsojm\u00eb shpejt situat\u00ebn n\u00eb host, si dhe dinamik\u00ebn e saj me nj\u00eb interval deri n\u00eb 2 sekonda, duhet t\u00eb p\u00ebrdorim ESXTOP.<\/p>\n

Ekrani i ESXTOP p\u00ebr Memory thirret me tastin \"m\" dhe duket si n\u00eb vijim (jan\u00eb zgjedhur fushat B,D,H,J,K,L,O):<\/p>\n

\"Analiza
\n
\nParametrat q\u00eb na interesojn\u00eb jan\u00eb: <\/p>\n

Mem overcommit avg<\/b> \u2014 vlera mesatare e mbip\u00ebrshkrimit t\u00eb memories n\u00eb host p\u00ebr 1, 5 dhe 15 minuta. N\u00ebse \u00ebsht\u00eb mbi 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 radh\u00ebt PMEM\/MB<\/b> dhe VMKMEM\/MB<\/b> \u2014 informacion mbi memorien fizike t\u00eb serverit dhe memorien e disponueshme p\u00ebr VMkernel. Nga e ve\u00e7anta k\u00ebtu, mund t\u00eb shohim vler\u00ebn minfree (n\u00eb MB), gjendjen e hostit p\u00ebr memory (n\u00eb rastin ton\u00eb, e lart\u00eb).<\/p>\n

N\u00eb rreshtin NUMA\/MB<\/b> mund t\u00eb shihni shp\u00ebrndarjen e memories s\u00eb operativ\u00ebs sipas NUMA-nod\u00ebve (socket-eve). N\u00eb k\u00ebt\u00eb shembull, shp\u00ebrndarja \u00ebsht\u00eb e pabarabart\u00eb, e cila n\u00eb parim nuk \u00ebsht\u00eb shum\u00eb mir\u00eb.<\/p>\n

M\u00eb pas vjen statistika e p\u00ebrgjithshme p\u00ebr serverin n\u00eb lidhje me teknik\u00ebt e rikuperimit t\u00eb memories:<\/p>\n

PSHARE\/MB<\/b> \u2014 kjo \u00ebsht\u00eb statistika 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, mund t\u00eb na interesoj\u00eb informacioni n\u00eb vijim. Emrat e VM-ve i kam fshir\u00eb p\u00ebr t\u00eb mos tronditur audienc\u00ebn :). N\u00ebse metrika ESXTOP \u00ebsht\u00eb e ngjashme me num\u00ebruesin n\u00eb vSphere, jap num\u00ebruesin p\u00ebrkat\u00ebs. <\/p>\n

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

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

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

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

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

MCTLGT<\/b> \u2014 sasia e memories (MB) q\u00eb ESXi d\u00ebshiron t\u00eb t\u00ebrheq\u00eb nga VM p\u00ebrmes Balloon Driver (Memctl Target).<\/p>\n

MCTLMAX<\/b> \u2014 sasia maksimale e memories (MB) q\u00eb ESXi mund t\u00eb t\u00ebrheq\u00eb nga VM p\u00ebrmes Balloon Driver.<\/p>\n

SWCUR<\/b> \u2014 sasia aktuale e memories (MB) q\u00eb i \u00ebsht\u00eb dh\u00ebn\u00eb VM nga skedari Swap. <\/p>\n

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

Gjithashtu p\u00ebrmes ESXTOP mund t\u00eb shihni informacione m\u00eb t\u00eb detajuara rreth topologjis\u00eb NUMA t\u00eb VM-s\u00eb. P\u00ebr k\u00ebt\u00eb, duhet t\u00eb zgjidhni fushat D, G:<\/p>\n

\"Analiza
\n
\nNHN<\/b> \u2013 nyjet NUMA mbi t\u00eb cilat ndodhet VM-ja. K\u00ebtu mund t\u00eb v\u00ebreni menj\u00ebher\u00eb VM-t\u00eb e gj\u00ebra, t\u00eb cilat nuk hyjn\u00eb n\u00eb nj\u00eb nyje NUMA.<\/p>\n

NRMEM<\/b> \u2013 sa megabajt memorie merr VM-ja nga nyja NUMA e larg\u00ebt.<\/p>\n

NLMEM<\/b> \u2013 sa megabajt memorie merr VM-ja nga nyja NUMA lokale.<\/p>\n

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

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

\nN\u00ebse numrat e CPU-s\u00eb n\u00eb hipervizor zakonisht nuk p\u00ebrb\u00ebjn\u00eb interes t\u00eb ve\u00e7ant\u00eb, situata me memorien \u00ebsht\u00eb e kund\u00ebrta. P\u00ebrdorimi i lart\u00eb i memories n\u00eb VM nuk do t\u00eb thot\u00eb gjithmon\u00eb se ka nj\u00eb problem me performancen, por p\u00ebrdorimi i lart\u00eb i memories n\u00eb hipervizor, p\u00ebrkundrazi, aktivizon teknik\u00ebn e menaxhimit t\u00eb memories dhe shkakton probleme me performanc\u00ebn e VM-s\u00eb. Duhet t\u00eb monitoroni alarmin e P\u00ebrdorimit t\u00eb Memories s\u00eb Hostit dhe t\u00eb mos lejoni q\u00eb VM-ja t\u00eb kaloj\u00eb n\u00eb Swap.<\/p>\n

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

Unswap<\/h3>\n

\nN\u00ebse VM ka kaluar n\u00eb Swap, performanca e saj bie ndjesh\u00ebm. Shenjat e Ballooning-ut dhe kompresionit shpejt zhduken pas shfaqjes s\u00eb memories s\u00eb lir\u00eb n\u00eb host, por VM nuk nxitohet aspak t\u00eb kthehet nga Swap n\u00eb memorien e serverit.
\nDerisa t\u00eb arrihet versioni ESXi 6.0, m\u00ebnyra e vetme e besueshme dhe e shpejt\u00eb p\u00ebr t\u00eb nxjerr\u00eb VM nga Swap ishte ri-ngritja (n\u00ebse do t\u00eb sakt\u00ebsojm\u00eb, fikja\/rikthimi i kontejnerit). Duke filluar nga ESXi 6.0, u shfaq nj\u00eb m\u00ebnyr\u00eb, ndon\u00ebse jo plot\u00ebsisht zyrtare, por funksionale dhe e besueshme p\u00ebr t\u00eb nxjerr\u00eb VM nga Swap. N\u00eb nj\u00eb nga konferencat kam arritur t\u00eb bisedoj me nj\u00eb nga inxhinier\u00ebt e VMware, q\u00eb p\u00ebrgjigjej p\u00ebr CPU Scheduler. Ai konfirmoi q\u00eb m\u00ebnyra \u00ebsht\u00eb plot\u00ebsisht funksionale dhe e sigurt. N\u00eb p\u00ebrvoj\u00ebn ton\u00eb, nuk kemi v\u00ebrejtur probleme me t\u00eb.<\/p>\n

Faktikisht komandat p\u00ebr nxjerrjen e VM nga Swap spjegoi<\/a><\/noindex> Duncan Epping. Nuk do t\u00eb p\u00ebrs\u00ebris p\u00ebrshkrimin e detajuar, thjesht do t\u00eb jap nj\u00eb shembull t\u00eb p\u00ebrdorimit t\u00eb tij. Si\u00e7 shihet n\u00eb screenshot, pas nj\u00eb kohe pas ekzekutimit t\u00eb komand\u00ebs t\u00eb dh\u00ebn\u00eb, 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, dua t\u00eb jap disa k\u00ebshilla q\u00eb do t'ju ndihmojn\u00eb t\u00eb shmangni problemet me performanc\u00ebn e VM p\u00ebr shkak t\u00eb kujtes\u00ebs operuese:<\/p>\n