{"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\/lv\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-2-memory","title":{"rendered":"VM veiktsp\u0113jas anal\u012bze VMware vSphere. 2. da\u013ca: Atmi\u0146a","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"VM
\n
\n1. Da\u013ca. Par CPU<\/a><\/noindex><\/p>\n

\u0160aj\u0101 rakst\u0101 run\u0101sim par RAM (operat\u012bv\u0101s atmi\u0146as) veiktsp\u0113jas skait\u012bt\u0101jiem vSphere.
\nIzskat\u0101s, ka ar atmi\u0146u viss ir skaidr\u0101k nek\u0101 ar procesoru: ja VM ir veiktsp\u0113jas probl\u0113mas, t\u0101s ir gr\u016bti nepaman\u012bt. Tom\u0113r, ja t\u0101s rodas, ar t\u0101m tikt gal\u0101 ir daudz gr\u016bt\u0101k. Bet par visu p\u0113c k\u0101rtas. <\/a><\/noindex><\/p>\n

Nedaudz teorijas<\/h3>\n

\nVirtu\u0101lo ma\u0161\u012bnu operat\u012bv\u0101 atmi\u0146a tiek \u0146emta no servera atmi\u0146as, kur\u0101 darbojas VM. Tas ir visai ac\u012bmredzami:). Ja serverim nepietiek operat\u012bv\u0101s atmi\u0146as visiem, kam t\u0101 nepiecie\u0161ama, ESXi s\u0101k izmantot operat\u012bv\u0101s atmi\u0146as pat\u0113ri\u0146a optimiz\u0101cijas tehnikas (memory reclamation techniques). Pret\u0113j\u0101 gad\u012bjum\u0101 oper\u0113t\u0101jsist\u0113mas VM sabrukt ar piek\u013cuves k\u013c\u016bd\u0101m. <\/p>\n

K\u0101das tehnikas izmantot, ESXi lemj atkar\u012bb\u0101 no operat\u012bv\u0101s atmi\u0146as noslodzes:<\/p>\n

Atmi\u0146as st\u0101voklis<\/b><\/p>\n

Robe\u017ea<\/b><\/p>\n

Darb\u012bbas<\/b><\/p>\n

High<\/p>\n

400% no minFree<\/p>\n

P\u0113c aug\u0161\u0113j\u0101s robe\u017eas sasnieg\u0161anas liel\u0101s atmi\u0146as lapas tiek sadal\u012btas maz\u0101k\u0101s (TPS darbojas standarta re\u017e\u012bm\u0101).<\/p>\n

Clear<\/p>\n

100% no minFree<\/p>\n

Liel\u0101s atmi\u0146as lapas tiek sadal\u012btas maz\u0101k\u0101s, TPS darbojas piespiedu k\u0101rt\u0101.<\/p>\n

M\u012bksts<\/p>\n

64% no minFree<\/p>\n

TPS + Balloon<\/p>\n

Ciets<\/p>\n

32% no minFree<\/p>\n

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

Zems<\/p>\n

16% no minFree<\/p>\n

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

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

minFree \u2014 t\u0101 ir operat\u012bv\u0101 atmi\u0146a, kas nepiecie\u0161ama hipervizora darb\u012bbai. <\/p>\n

L\u012bdz ESXi 4.1 ieskaitot minFree p\u0113c noklus\u0113juma bija fiks\u0113ts \u2014 6% no servera operat\u012bv\u0101s atmi\u0146as apjoma (procentu var\u0113ja main\u012bt, izmantojot opciju Mem.MinFreePct ESXi). V\u0113l\u0101kaj\u0101s versij\u0101s, palielinoties servera atmi\u0146as apjomiem, minFree s\u0101ka apr\u0113\u0137in\u0101t, pamatojoties uz hosta atmi\u0146as apjomu, nevis k\u0101 fiks\u0113tu procentu v\u0113rt\u012bbu. <\/p>\n

MinFree (p\u0113c noklus\u0113juma) v\u0113rt\u012bba tiek apr\u0113\u0137in\u0101ta \u0161\u0101di:<\/p>\n

Atmi\u0146as procents, kas rezerv\u0113ts minFree<\/b><\/p>\n

Atmi\u0146as diapazons<\/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

Atlikus\u012b atmi\u0146a<\/p>\n

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

Piem\u0113ram, serverim ar 128 GB RAM minFree v\u0113rt\u012bba b\u016bs \u0161\u0101da:
\nMinFree = 245,76 + 327,68 + 327,68 + 1024 = 1925,12 MB = 1,88 GB
\nFaktisk\u0101 v\u0113rt\u012bba var at\u0161\u0137irties par p\u0101ris simtiem MB, tas atkar\u012bgs no servera un operat\u012bv\u0101s atmi\u0146as.<\/p>\n

Atmi\u0146as procents, kas rezerv\u0113ts minFree<\/b><\/p>\n

Atmi\u0146as diapazons<\/b><\/p>\n

V\u0113rt\u012bba 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

Atlikus\u012b atmi\u0146a (100 GB)<\/p>\n

1024 MB<\/p>\n

\nParasti Augsta st\u0101vok\u013ca sasnieg\u0161ana ir norm\u0101la pras\u012bba produkt\u012bviem stendiem. Test\u0113\u0161anas un att\u012bst\u012bbas stendiem pie\u0146emami var b\u016bt Clear\/Soft st\u0101vok\u013ci. Ja host\u0101 ir palicis maz\u0101k par 64% MinFree operat\u012bv\u0101s atmi\u0146as, tad VM, kas uz t\u0101 darbojas, noteikti nov\u0113ros veiktsp\u0113jas probl\u0113mas.<\/p>\n

Katram st\u0101voklim tiek izmantotas noteiktas atmi\u0146as atbr\u012bvo\u0161anas tehnikas, s\u0101kot ar TPS, gandr\u012bz neradot ietekmi uz VM veiktsp\u0113ju, un beidzot ar Swapping. Par to past\u0101st\u012b\u0161u s\u012bk\u0101k. <\/p>\n

Transparent Page Sharing (TPS).<\/b> TPS b\u016bt\u012bb\u0101 ir virtu\u0101lo ma\u0161\u012bnu operat\u012bv\u0101s atmi\u0146as lapu deduplic\u0113\u0161ana uz servera.<\/p>\n

ESXi mekl\u0113 identiskas virtu\u0101lo ma\u0161\u012bnu operat\u012bv\u0101s atmi\u0146as lapas, apr\u0113\u0137inot un sal\u012bdzinot lapu hash summas, un izdz\u0113\u0161 dublik\u0101tus, aizst\u0101jot tos ar atsauc\u0113m uz vienu un to pa\u0161u fizisk\u0101s atmi\u0146as lapu server\u012b. Rezult\u0101t\u0101 fizisk\u0101s atmi\u0146as pat\u0113ri\u0146\u0161 samazin\u0101s, un ir iesp\u0113jams sasniegt zin\u0101mu p\u0101rmaksu attiec\u012bb\u0101 uz atmi\u0146u praktiski bez veiktsp\u0113jas samazin\u0101\u0161an\u0101s.<\/p>\n

\"VM
\nAvots<\/a><\/noindex><\/p>\n

\u0160is meh\u0101nisms darbojas tikai 4 KB (mazo lapu) atmi\u0146as lap\u0101m. 2 MB (lielo lapu) izm\u0113ra lapas hipervizors pat necen\u0161as deduplic\u0113t: iesp\u0113ja atrast identiskas lapas \u0161\u0101da izm\u0113ra ir zema.<\/p>\n

P\u0113c noklus\u0113juma ESXi pie\u0161\u0137ir atmi\u0146u lielaj\u0101m lap\u0101m. Lielo lapu sadal\u012b\u0161ana mazaj\u0101s s\u0101kas, sasniedzot augsto st\u0101vok\u013ca slieksni, un notiek piespiedu k\u0101rt\u0101, kad tiek sasniegts Clear st\u0101voklis (skat\u012bt hipervizora st\u0101vok\u013cu tabulu).<\/p>\n

Ja v\u0113laties, lai TPS uzs\u0101ktu darbu, negaidot, kad hosta operat\u012bv\u0101 atmi\u0146a tiks piln\u012bb\u0101 aizpild\u012bta, Advanced Options ESXi j\u0101iestata v\u0113rt\u012bba \u201cMem.AllocGuestLargePage\u201d<\/i> uz 0 (noklus\u0113jums 1). Tad lielo atmi\u0146as lapu pie\u0161\u0137ir\u0161ana virtu\u0101laj\u0101m ma\u0161\u012bn\u0101m tiks atsp\u0113jota.<\/p>\n

Kop\u0161 2014. gada decembra vis\u0101s ESXi laidiena versij\u0101s TPS starp VM p\u0113c noklus\u0113juma ir atsp\u0113jota, jo tika atrasta ievainojam\u012bba, kas teor\u0113tiski \u013cauj piek\u013c\u016bt vienas VM operat\u012bvajai atmi\u0146ai no citas VM. S\u012bk\u0101ka inform\u0101cija \u0161eit. Inform\u0101cija par praktisko TPS ievainojam\u012bbas izmanto\u0161anu man nav bijusi pieejama.<\/p>\n

TPS politika tiek kontrol\u0113ta, izmantojot papildu opciju \u201cMem.ShareForceSalting\u201d<\/i> ESXi:
\n0 \u2014 Inter-VM TPS. TPS darbojas da\u017e\u0101du VM lap\u0101m;
\n1 \u2013 TPS VM ar vien\u0101du \u201csched.mem.pshare.salt\u201d v\u0113rt\u012bbu VMX;
\n2 (noklus\u0113jums) \u2013 Intra-VM TPS. TPS darbojas lap\u0101m VM iek\u0161ien\u0113.<\/p>\n

Noteikti ir j\u0113ga izsl\u0113gt lielas lapas un iesl\u0113gt Inter-VM TPS test\u0113\u0161anas stendos. To var izmantot ar\u012b stendos ar lielu vienveid\u012bgu VM skaitu. Piem\u0113ram, stendos ar VDI fizisk\u0101s atmi\u0146as ietaup\u012bjums var sasniegt desmitiem procentu. <\/p>\n

Atmi\u0146as balon\u0113\u0161ana.<\/b> Balon\u0113\u0161ana vairs nav tik nekait\u012bga un caursp\u012bd\u012bga VM oper\u0113t\u0101jsist\u0113mai k\u0101 TPS. Bet ar pareizu piem\u0113ro\u0161anu balon\u0113\u0161ana var b\u016bt dro\u0161i lietojama un pat str\u0101d\u0101t.<\/p>\n

Kop\u0101 ar VMware Tools VM tiek instal\u0113ts \u012bpa\u0161s draiveris, ko sauc par Balloon Driver (t\u0101pat k\u0101 vmmemctl). Kad hipervizoram s\u0101k tr\u016bkt fizisk\u0101s atmi\u0146as un tas non\u0101k Soft st\u0101vokl\u012b, ESXi l\u016bdz VM atgriezt neizmantoto RAM caur \u0161o Balloon Driver. Draiveris darbojas oper\u0113t\u0101jsist\u0113mas l\u012bmen\u012b un pieprasa br\u012bvo atmi\u0146u no t\u0101s. Hipervizors redz, kuras fizisk\u0101s atmi\u0146as lapas ir aiz\u0146\u0113mis Balloon Driver, at\u0146em atmi\u0146u no virtu\u0101l\u0101s ma\u0161\u012bnas un atgrie\u017e to viesu sist\u0113mai. Probl\u0113mas ar OS darb\u012bbu nerodas, jo oper\u0113t\u0101jsist\u0113mas l\u012bmen\u012b atmi\u0146a tiek aiz\u0146emta ar Balloon Driver. Noklus\u0113juma iestat\u012bjumos Balloon Driver var at\u0146emt l\u012bdz 65% no VM atmi\u0146as.<\/p>\n

Ja VM nav uzst\u0101d\u012bti VMware Tools vai balon\u0113\u0161ana ir atsp\u0113jota (neiesaku, bet ir ar\u012b t\u0101da iesp\u0113ja KB<\/a><\/noindex>:), hipervizors nekav\u0113joties p\u0101riet pie stingr\u0101k\u0101m atmi\u0146as at\u0146em\u0161anas tehnik\u0101m. Secin\u0101jums: p\u0101rliecinieties, ka VMware Tools VM ir uzst\u0101d\u012bti.<\/p>\n

\"VM
\nBalon\u0113\u0161anas draivera darb\u012bbu var p\u0101rbaud\u012bt no OS caur VMware Tools.<\/i>.<\/p>\n

Atmi\u0146as saspie\u0161ana.<\/b> \u0160\u012b tehnika tiek izmantota, kad ESXi non\u0101k Hard st\u0101vokl\u012b. K\u0101 nor\u0101d\u012bts nosaukum\u0101, ESXi cen\u0161as saspiest 4 Kb atmi\u0146as lapas l\u012bdz 2 Kb, t\u0101d\u0113j\u0101di atbr\u012bvojot nedaudz vietas fiziskaj\u0101 atmi\u0146\u0101. \u0160\u012b tehnika iev\u0113rojami palielina piek\u013cuves laiku atmi\u0146as lapu saturam, jo lapa iepriek\u0161 j\u0101sasprindzina. Da\u017ereiz nav iesp\u0113jams saspiest visas lapas, un pats process prasa zin\u0101mu laiku. T\u0101d\u0113\u013c \u0161\u012b tehnika praks\u0113 nav \u013coti efekt\u012bva.<\/p>\n

Atmi\u0146as apmai\u0146a.<\/b> P\u0113c \u012bsa atmi\u0146as saspie\u0161anas f\u0101zes ESXi praktiski neizb\u0113gami (ja VM nav p\u0101rvietoti uz cit\u0101m viesu sist\u0113m\u0101m vai nav izsl\u0113gti) p\u0101riet pie apmai\u0146as. Un, ja atmi\u0146as palicis \u013coti maz (zems st\u0101voklis), hipervizors ar\u012b p\u0101rst\u0101j pie\u0161\u0137irt VM atmi\u0146as lapas, kas var rad\u012bt probl\u0113mas viesu OS VM.<\/p>\n

\u0160\u0101di darbojas Swapping. Iesl\u0113dzot virtu\u0101lo ma\u0161\u012bnu, tiek izveidots fails ar papla\u0161in\u0101jumu .vswp. T\u0101 izm\u0113rs ir vien\u0101ds ar virtu\u0101l\u0101s ma\u0161\u012bnas neietekm\u0113to operat\u012bvo atmi\u0146u: tas ir starp\u012bba starp konfigur\u0113to un rezerv\u0113to atmi\u0146u. Darbojoties Swapping proces\u0101, ESXi izn\u0101k atmi\u0146as lapas no virtu\u0101l\u0101s ma\u0161\u012bnas \u0161aj\u0101 fail\u0101 un s\u0101k str\u0101d\u0101t ar to viet\u0113jo servera fizisko atmi\u0146u. Protams, \u0161\u0101da 'operat\u012bv\u0101' atmi\u0146a ir vair\u0101kas reizes l\u0113n\u0101ka par \u012bsto, pat ja .vswp atrodas uz \u0101tr\u0101s kr\u0101tuves.<\/p>\n

At\u0161\u0137ir\u012bb\u0101 no Ballooning, kad VM iz\u0146em neizmantot\u0101s lapas, Swapping proces\u0101 uz diska var p\u0101rvietoties lapas, kuras akt\u012bvi izmanto oper\u0113t\u0101jsist\u0113ma vai lietojumprogrammas iek\u0161 VM. Rezult\u0101t\u0101 VM veiktsp\u0113ja samazin\u0101s l\u012bdz pat sasal\u0161anai. VM form\u0101li darbojas, un to vismaz var pareizi izsl\u0113gt no OS. Ja esat paciet\u012bgs \ud83d\ude09<\/p>\n

Ja VM ir devies Swap \u2014 tas ir neparasts st\u0101voklis, kuru lab\u0101k nov\u0113rst.<\/p>\n

Galvenie virtu\u0101l\u0101s ma\u0161\u012bnas atmi\u0146as veiktsp\u0113jas skait\u012bt\u0101ji<\/h3>\n

\nT m\u0113s esam non\u0101ku\u0161i pie galven\u0101. Lai uzraudz\u012btu atmi\u0146as st\u0101vokli VM, ir \u0161\u0101di skait\u012bt\u0101ji:<\/p>\n

Akt\u012bvs<\/b> \u2014 r\u0101da operat\u012bv\u0101s atmi\u0146as apjomu (KB), uz kuru VM ir piek\u013cuvis iepriek\u0161\u0113j\u0101 m\u0113r\u012bjumu period\u0101.<\/p>\n

Usage<\/b> \u2014 tas pats, kas Active, bet procentos no konfigur\u0113t\u0101s virtu\u0101l\u0101s ma\u0161\u012bnas operat\u012bv\u0101s atmi\u0146as. Apr\u0113\u0137in\u0101ts p\u0113c \u0161\u0101das formulas: active \u00f7 virtu\u0101l\u0101s ma\u0161\u012bnas konfigur\u0113t\u0101s atmi\u0146as izm\u0113rs.
\nAugsts Usage un Active, attiec\u012bgi, ne vienm\u0113r nor\u0101da uz VM veiktsp\u0113jas probl\u0113m\u0101m. Ja VM akt\u012bvi izmanto atmi\u0146u (k\u0101 minimums, piek\u013c\u016bst tai), tas nenoz\u012bm\u0113, ka atmi\u0146a tr\u016bkst. Dr\u012bz\u0101k tas ir pamats apl\u016bkot, kas notiek OS.
\nIr standarta trauksme par atmi\u0146as izmanto\u0161anu VM:<\/p>\n

\"VM
\n
\nKoplietojamais<\/b> \u2014 virtu\u0101l\u0101s ma\u0161\u012bnas operat\u012bv\u0101s atmi\u0146as apjoms, kas ir deduplic\u0113ts ar TPS (iek\u0161 VM vai starp VM).<\/p>\n

Granted<\/b> \u2014 fizisk\u0101s atmi\u0146as apjoms uz saimniekdatortehnika (KB), kas ir pie\u0161\u0137irts VM. Ietver Shared.<\/p>\n

Consumed<\/b> (Granted \u2014 Shared) \u2014 fizisk\u0101s atmi\u0146as apjoms (KB), ko VM pat\u0113r\u0113 no saimniekdatortehnika. Neietver Shared.<\/p>\n

Ja da\u013ca no VM atmi\u0146as tiek pie\u0161\u0137irta ne no fizisk\u0101s atmi\u0146as saimniekdatortehnika, bet no swap faila vai atmi\u0146a tiek iz\u0146emta no VM caur Balloon Driver, \u0161is apjoms nav iek\u013cauts Granted un Consumed.
\nAugsti Granted un Consumed r\u0101d\u012bt\u0101ji ir pavisam norm\u0101li. Oper\u0113t\u0101jsist\u0113ma pak\u0101peniski atbr\u012bvo atmi\u0146u no hipervizora un neatgrie\u017e to atpaka\u013c. Laika gait\u0101 akt\u012bv\u0101s VM r\u0101d\u012bt\u0101ju v\u0113rt\u012bbas tuvojas konfigur\u0113t\u0101s atmi\u0146as apjomam un tur paliek.<\/p>\n

Nulle<\/b> \u2014 VM operat\u012bv\u0101s atmi\u0146as apjoms (KB), kur\u0161 satur nulles. \u0160\u0101da atmi\u0146a tiek uzskat\u012bta par br\u012bvu hipervizora un var tikt pie\u0161\u0137irta cit\u0101m virtu\u0101laj\u0101m ma\u0161\u012bn\u0101m. P\u0113c tam, kad viesu OS ir pierakst\u012bjusi kaut ko nos\u0113din\u0101taj\u0101 atmi\u0146\u0101, t\u0101 p\u0101riet uz Consumed un vairs neatgrie\u017eas.<\/p>\n

Rezerv\u0113ta papildu atmi\u0146a<\/b> \u2014 VM operat\u012bv\u0101s atmi\u0146as apjoms (KB), ko hipervizors rezerv\u0113jis, lai nodro\u0161in\u0101tu VM darb\u012bbu. Tas ir neliels apjoms, bet tam oblig\u0101ti j\u0101b\u016bt pieejamam host\u0101, cit\u0101di VM nes\u0101ksies.<\/p>\n

Balloon<\/b> \u2014 operat\u012bv\u0101s atmi\u0146as apjoms (KB), kas at\u0146emts no VM, izmantojot Balloon Driver.<\/p>\n

Saspiests<\/b> \u2014 operat\u012bv\u0101s atmi\u0146as apjoms (KB), kuru izdev\u0101s saspiest.<\/p>\n

Mijlocin\u0101ts<\/b> \u2014 operat\u012bv\u0101s atmi\u0146as apjoms (KB), kur\u0161 fizisk\u0101s atmi\u0146as tr\u016bkuma d\u0113\u013c p\u0101rc\u0113lies uz disku.
\nBalloon un p\u0101r\u0113jie atmi\u0146as atg\u016b\u0161anas r\u0101d\u012bt\u0101ji ir vien\u0101di ar nulli.<\/p>\n

T\u0101 izskat\u0101s grafika ar r\u0101d\u012bt\u0101jiem par norm\u0101li str\u0101d\u0101jo\u0161u VM ar 150 GB operat\u012bvo atmi\u0146u.<\/p>\n

\"VM
\n
\n\u0160aj\u0101 grafik\u0101 VM ir ac\u012bmredzamas probl\u0113mas. Apak\u0161\u0101 redzams, ka \u0161ai VM tika izmantotas visas aprakst\u012bt\u0101s operat\u012bv\u0101s atmi\u0146as tehnikas. Balloon \u0161ai VM ir daudz liel\u0101ks nek\u0101 Consumed. Paties\u012bb\u0101 VM ir dr\u012bz\u0101k mirusi nek\u0101 dz\u012bva. <\/p>\n

\"VM
\n<\/p>\n

ESXTOP<\/h3>\n

\nT\u0101pat k\u0101 ar CPU, ja v\u0113lamies \u0101tri nov\u0113rt\u0113t situ\u0101ciju host\u0101, k\u0101 ar\u012b t\u0101s dinamiku ar interv\u0101lu l\u012bdz 2 sekund\u0113m, ir v\u0113rts izmantot ESXTOP.<\/p>\n

ESXTOP ekr\u0101ns par atmi\u0146u tiek izsaukts, nospie\u017eot tausti\u0146u \u201em\u201d un izskat\u0101s \u0161\u0101di (izv\u0113l\u0113ti B,D,H,J,K,L,O lauki):<\/p>\n

\"VM
\n
\nMums interes\u0113jo\u0161ie parametri b\u016bs \u0161\u0101di: <\/p>\n

Mem overcommit avg<\/b> \u2014 vid\u0113jais atmi\u0146as p\u0101rrakst\u012b\u0161anas l\u012bmenis uz hosta p\u0113d\u0113j\u0101s 1, 5 un 15 min\u016bt\u0113s. Ja tas ir virs nulles, tas ir iemesls, lai paskat\u012btos, kas notiek, bet ne vienm\u0113r liecina par probl\u0113m\u0101m.<\/p>\n

Rind\u0101s PMEM\/MB<\/b> un VMKMEM\/MB<\/b> \u2014 inform\u0101cija par servera fizisko atmi\u0146u un VMkernel pieejamo atmi\u0146u. Interesant\u0101kais \u0161eit ir minfree v\u0113rt\u012bba (MB), k\u0101 ar\u012b st\u0101voklis atmi\u0146\u0101 (m\u016bsu gad\u012bjum\u0101 augsts).<\/p>\n

Rind\u0101 NUMA\/MB<\/b> var redz\u0113t operat\u012bv\u0101s atmi\u0146as sadal\u012bjumu pa NUMA mezgliem (soketiem). \u0160aj\u0101 piem\u0113r\u0101 sadal\u012bjums nav vienm\u0113r\u012bgs, kas princip\u0101 nav \u013coti labi.<\/p>\n

T\u0101l\u0101k ir sniegta visp\u0101r\u0113j\u0101 statistika par serveri, izmantojot atmi\u0146as atg\u016b\u0161anas tehnolo\u0123ijas:<\/p>\n

PSHARE\/MB<\/b> \u2014 \u0161\u012b ir TPS statistika;<\/p>\n

SWAP\/MB<\/b> \u2014 Swap lieto\u0161anas statistika;<\/p>\n

ZIP\/MB<\/b> \u2014 atmi\u0146as lapu saspie\u0161anas statistika;<\/p>\n

MEMCTL\/MB<\/b> \u2014 Balloon Driver lieto\u0161anas statistika.<\/p>\n

M\u016bs var interes\u0113t \u0161\u0101da inform\u0101cija par atsevi\u0161\u0137\u0101m VM. VM nosaukumus esmu nosl\u0113pis, lai neman\u012btu auditoriju :). Ja ESXTOP metrika ir l\u012bdz\u012bga skait\u012bt\u0101jam vSphere, sniedzu attiec\u012bgo skait\u012bt\u0101ju. <\/p>\n

MEMSZ<\/b> \u2014 atmi\u0146as apjoms, kas konfigur\u0113ts VM (MB).
\nMEMSZ = GRANT + MCTLSZ + SWCUR + untouched.<\/p>\n

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

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

MCTL?<\/b> \u2014 vai VM ir uzst\u0101d\u012bts Balloon Driver.<\/p>\n

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

MCTLGT<\/b> \u2014 operat\u012bv\u0101s atmi\u0146as apjoms (MB), ko ESXi v\u0113las iz\u0146emt no VM, izmantojot Balloon Driver (Memctl Target).<\/p>\n

MCTLMAX<\/b> \u2014 maksim\u0101lais operat\u012bv\u0101s atmi\u0146as apjoms (MB), ko ESXi var iz\u0146emt no VM, izmantojot Balloon Driver.<\/p>\n

SWCUR<\/b> \u2014 pa\u0161reiz\u0113jais operat\u012bv\u0101s atmi\u0146as apjoms (MB), kas pie\u0161\u0137irts VM no Swap faila. <\/p>\n

SWGT<\/b> \u2014 operat\u012bv\u0101s atmi\u0146as apjoms (MB), ko ESXi v\u0113las pie\u0161\u0137irt VM no Swap faila (Swap Target).<\/p>\n

Ar\u012b, izmantojot ESXTOP, var skat\u012bt detaliz\u0113t\u0101ku inform\u0101ciju par VM NUMA topolo\u0123iju. Lai to izdar\u012btu, j\u0101izv\u0113las lauki D,G:<\/p>\n

\"VM
\n
\nNHN<\/b> \u2013 NUMA mezgli, kur atrodas VM. \u0160eit ir uzreiz paman\u0101mas platas VM, kuras neietilpst vien\u0101 NUMA mezgl\u0101.<\/p>\n

NRMEM<\/b> \u2013 cik megabaitus atmi\u0146as VM \u0146em no att\u0101l\u0101 NUMA mezgla.<\/p>\n

NLMEM<\/b> \u2013 cik megabaitus atmi\u0146as VM \u0146em no viet\u0113j\u0101 NUMA mezgla.<\/p>\n

N%L<\/b> \u2013 procentu\u0101lais VM atmi\u0146as apjoms viet\u0113j\u0101 NUMA mezgl\u0101 (ja maz\u0101k par 80%, var rasties veiktsp\u0113jas probl\u0113mas).<\/p>\n

Atmi\u0146a hipervizor\u0101<\/h3>\n

\nJa CPU skait\u012bt\u0101ji hipervizor\u0101 parasti nesniedz \u012bpa\u0161u interesi, tad ar atmi\u0146u situ\u0101cija ir pret\u0113ja. Augsta atmi\u0146as izmanto\u0161ana VM ne vienm\u0113r nor\u0101da uz veiktsp\u0113jas probl\u0113mu, bet augsta atmi\u0146as izmanto\u0161ana hipervizor\u0101 tie\u0161i aktiviz\u0113 atmi\u0146as p\u0101rvald\u012b\u0161anas tehnikas un izraisa VM veiktsp\u0113jas probl\u0113mas. J\u0101uzman\u0101s par Host Memory Usage trauksm\u0113m un j\u0101r\u016bp\u0113jas, lai VM nenon\u0101ktu Swap.<\/p>\n

\"VM
\n
\n\"VM
\n<\/p>\n

Unswap<\/h3>\n

\nJa VM non\u0101k Swap, t\u0101s veiktsp\u0113ja strauji samazin\u0101s. Ballooning un saspie\u0161anas p\u0113das \u0101tri izz\u016bd, kad uz hosta par\u0101d\u0101s br\u012bva operat\u012bv\u0101 atmi\u0146a, ta\u010du virtualiz\u0101cijas ma\u0161\u012bna pavisam nesteidzas atgriezties no Swap uz servera operat\u012bvo atmi\u0146u.
\nL\u012bdz ESXi 6.0 versijai vien\u012bgais uzticamais un \u0101trais veids, k\u0101 izvest VM no Swap, bija restart\u0113\u0161ana (ja prec\u012bz\u0101k, konteineru izsl\u0113g\u0161ana\/iesl\u0113g\u0161ana). S\u0101kot ar ESXi 6.0, par\u0101d\u012bj\u0101s, kaut ar\u012b ne pavisam ofici\u0101ls, tom\u0113r darboties sp\u0113j\u012bgs un uzticams veids, k\u0101 izvest VM no Swap. Vien\u0101 no konferences man izdev\u0101s sazin\u0101ties ar vienu no VMware in\u017eenieriem, kur\u0161 atbild par CPU Scheduler. Vi\u0146\u0161 apstiprin\u0101ja, ka \u0161is veids ir pavisam funkcion\u0101ls un dro\u0161s. M\u016bsu pieredz\u0113 ar to nav konstat\u0113tas probl\u0113mas.<\/p>\n

Faktiski komandas VM izve\u0161anai no Swap aprakst\u012bja<\/a><\/noindex> Duncan Epping. Negribu atk\u0101rtot detaliz\u0113tu aprakstu, vienk\u0101r\u0161i snieg\u0161u piem\u0113ru t\u0101s izmanto\u0161anai. K\u0101 redzams ekr\u0101n\u0161\u0101vi\u0146\u0101, p\u0113c noteikt\u0101 komandu izpildes k\u0101du laiku p\u0113c tam Swap uz VM paz\u016bd.<\/p>\n

\"VM
\n<\/p>\n

Padomi operat\u012bv\u0101s atmi\u0146as p\u0101rvald\u012bbai ESXi<\/h3>\n

\nP\u0113d\u0113j\u0101 br\u012bd\u012b snieg\u0161u da\u017eus padomus, kas pal\u012bdz\u0113s jums izvair\u012bties no VM veiktsp\u0113jas probl\u0113m\u0101m saist\u012bb\u0101 ar operat\u012bvo atmi\u0146u:<\/p>\n