{"id":36486,"date":"2019-10-31T22:11:54","date_gmt":"2019-10-31T19:11:54","guid":{"rendered":"https:\/\/prohoster.info\/blog\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage\/"},"modified":"2019-10-31T22:11:54","modified_gmt":"2019-10-31T19:11:54","slug":"analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","status":"publish","type":"post","link":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","title":{"rendered":"Virtuaalmasinate j\u00f5udluse anal\u00fc\u00fcs VMware vSphere'is. Osa 3: Salvestamine","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Virtuaalmasinate j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 3: Salvestamine\" src=\"\/wp-content\/uploads\/2019\/07\/8f3ffe4a8666f3c2f7126d8fecfa1e3a.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/452884\/\">Osa 1. CPU-st<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/455820\/\">Osa 2. M\u00e4lu<\/a><\/noindex><\/p>\n<p>T\u00e4na vaatleme vSphere'i kettaaluste s\u00fcsteemide m\u00f5\u00f5dikuid. Probleemid salvestusruumiga on k\u00f5ige sagedamad p\u00f5hjused, miks virtuaalne masin t\u00f6\u00f6tab aeglaselt. Kui CPU ja RAM-i t\u00f5rkeotsing l\u00f5petatakse h\u00fcperviisoritasemel, siis ketta probleemidega v\u00f5ib osutuda vajalikuks vaadata ka andmeedastuse ja SAN-i poole.<\/p>\n<p>Teemat k\u00e4sitlen blokitaolise juurdep\u00e4\u00e4su n\u00e4itel SAN-ile, kuigi failip\u00f5hise juurdep\u00e4\u00e4su korral on loendurid enam-v\u00e4hem samad.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Veidi teooriat<\/h3>\n<p>\nKui r\u00e4\u00e4gitakse virtuaalmasinate kettaaluste s\u00fcsteemide j\u00f5udlustest, p\u00f6\u00f6ratakse tavaliselt t\u00e4helepanu kolmele omavahel seotud parameetrile:<\/p>\n<ul>\n<li>sisendi\/v\u00e4ljundi operatsioonide arv (Input\/Output Operations Per Second, IOPS);<\/li>\n<li>l\u00e4bivool (Throughput);<\/li>\n<li>sisendi\/v\u00e4ljundi operatsioonide latentsus (Latency).<\/li>\n<\/ul>\n<p>\n<b>IOPS arvu<\/b> on tavaliselt oluline juhuslike koormuste puhul: juurdep\u00e4\u00e4s ketta plokkidele, mis asuvad erinevates kohtades. N\u00e4iteks v\u00f5ivad sellised koormused olla andmebaasid, \u00e4ritarkvara (ERP, CRM) jne.<\/p>\n<p><b>L\u00e4bivusv\u00f5ime<\/b> on oluline j\u00e4rjestikuste koormuste puhul: juurdep\u00e4\u00e4s plokkidele, mis asuvad \u00fcksteise j\u00e4rel. N\u00e4iteks v\u00f5ivad selliseid koormusi genereerida failiserverid (kuid mitte alati) ja videovalves\u00fcsteemid.<\/p>\n<p>L\u00e4bivool on seotud sisendi\/v\u00e4ljundi operatsioonide arvuga j\u00e4rgmiselt:<\/p>\n<p><i>Throughput = IOPS * Bloki suurus<\/i>, kus Bloki suurus on ploki suurus.<\/p>\n<p>Ploki suurus on \u00fcsna oluline omadus. Praegused ESXi versioonid l\u00e4bivad plokid, mille suurus on kuni 32 767 KB. Kui plokk on veel suurem, jagatakse see mitmele osale. Mitte k\u00f5ik SAN-id ei suuda t\u00f5husalt t\u00f6\u00f6tada nii suurte plokkidega, seet\u00f5ttu on ESXi-l H\u00e4sti Seaded parameeter DiskMaxIOSize. Sellega saab v\u00e4hendada h\u00fcperviisori poolt l\u00e4bivat maksimaalset ploki suurust (lisaks <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1003469\">siin<\/a><\/noindex>). Soovitan enne selle parameetri muutmist konsulteerida SAN-i tootjaga v\u00f5i v\u00e4hemalt katsetada muudatusi laboratoorses keskkonnas.\u00a0<\/p>\n<p>Suure ploki suurus v\u00f5ib negatiivselt m\u00f5jutada SAN-i j\u00f5udlust. Isegi kui IOPS ja l\u00e4bi voolu arv on suhteliselt madalad, v\u00f5ivad suure ploki korral esineda k\u00f5rged latentsused. Seet\u00f5ttu p\u00f6\u00f6rake sellele parameetrile t\u00e4helepanu.<\/p>\n<p><b>Latency<\/b> on k\u00f5ige huvitavam j\u00f5udlusparameeter. Virtuaalse masina sisendi\/v\u00e4ljundi operatsioonide latentsus koosneb:<\/p>\n<ul>\n<li>latentsusest h\u00fcperviisorisse (KAVG, Average Kernel MilliSec\/Read);<\/li>\n<li>viivitused, mida pakuvad andmeedastusv\u00f5rk ja SAN (DAVG, keskmine draiveri millisekund\/k\u00e4sk).<\/li>\n<\/ul>\n<p>\nKoguviiit, mida on n\u00e4ha k\u00fclalise operatsioonis\u00fcsteemis (GAVG, keskmine k\u00fclalise millisekund\/k\u00e4sk), on KAVG ja DAVG summa.<\/p>\n<p>GAVG ja DAVG m\u00f5\u00f5detakse, KAVG arvutatakse: GAVG\u2013DAVG.<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasinate j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 3: Salvestamine\" src=\"\/wp-content\/uploads\/2019\/07\/729f519b4fb72b3fbb74237847a05baa.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n <noindex><a rel=\"nofollow\" href=\"https:\/\/www.codyhosterman.com\/2018\/03\/what-is-the-latency-stat-qavg\/\"><i>Allikas<\/i><\/a><\/noindex><\/p>\n<p>Vaatame l\u00e4hemalt <b>KAVG<\/b>. Normaalses t\u00f6\u00f6s peaks KAVG p\u00fc\u00fcdma nulli v\u00f5i v\u00e4hemalt olema palju v\u00e4iksem kui DAVG. Ainus teadaolev juhtum, kus KAVG on ootusp\u00e4raselt k\u00f5rge, on VM ketta IOPS piirang. Sel juhul KAVG suureneb, kui \u00fcritate piiri \u00fcletada.<\/p>\n<p>KAVG k\u00f5ige olulisem koostisosa on QAVG \u2013 t\u00f6\u00f6tluse ooteaeg h\u00fcperviisoris. \u00dclej\u00e4\u00e4nud KAVG komponendid on ebaolulised.<\/p>\n<p>Kettaadapteri draiveris ja lunide j\u00e4rjekorrad on fikseeritud suurusega. Suure koormusega keskkondades on selles suuruses kasulik vajadusel suurendada. <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1267\">Siin<\/a><\/noindex> Kirjeldatakse, kuidas suurendada adapteri draiveri j\u00e4rjekordi (samuti suureneb lunide j\u00e4rjekord). See seadistus t\u00f6\u00f6tab, kui luniga t\u00f6\u00f6tab ainult \u00fcks VM, mis on haruldane. Kui lunil on mitu VM-i, tuleb samuti suurendada parameetrit <i>Disk.SchedNumReqOutstanding<\/i> (juhis\u00a0 <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1268\">siin<\/a><\/noindex>). J\u00e4rjekorra suurendamine v\u00e4hendab QAVG-d ja KAVG-d vastavalt.<\/p>\n<p>Kuid enne tehke tutvust tootja HBA dokumentatsiooniga ja testige muudatusi laboris. <\/p>\n<p>Lunide j\u00e4rjekorra suurusele v\u00f5ib m\u00f5ju avaldada SIOC (Storage I\/O Control) mehhanismi sissel\u00fclitamine. See tagab \u00fchtlase juurdep\u00e4\u00e4su lunile k\u00f5igi klastriserverite poolt, muutes d\u00fcnaamiliselt lunide j\u00e4rjekorda serverites. See t\u00e4hendab, et kui m\u00f5nes hostis t\u00f6\u00f6tab VM, mis n\u00f5uab proportsionaalselt suurt t\u00f6\u00f6tlemisv\u00f5imet (noisy neighbor VM), siis SIOC v\u00e4hendab selle hosti lunide j\u00e4rjekorra pikkust (DQLEN). Rohkem teavet <noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2019\/03\/05\/dqlen-changes-what-is-going-on\/\">siin<\/a><\/noindex>.<\/p>\n<p>Oleme KAVG-st aru saanud, n\u00fc\u00fcd natuke <b>DAVG<\/b>. Siin on k\u00f5ik lihtne: DAVG on viivitus, mille toob sisse v\u00e4line keskkond (andmeedastusv\u00f5rk ja SAN). Igas kaasaegses ja v\u00e4hem kaasaegses SAN-is on oma j\u00f5udluse loendurid. DAVG probleemide anal\u00fc\u00fcsimiseks on m\u00f5istlik neid vaadata. Kui ESXi ja SAN-i pool on k\u00f5ik korras, kontrollige andmeedastusv\u00f5rku.<\/p>\n<p>Selleks, et v\u00e4ltida j\u00f5udlusprobleeme, valige oma salvestusruumi teede valimise poliitika (PSP) \u00f5igesti. Peaaegu k\u00f5ik kaasaegsed salvestusruumid toetavad PSP Round-Robin (kas koos ALUA-ga, as\u00fcmmeetrilise loogilise \u00fcksuse juurdep\u00e4\u00e4suga, v\u00f5i ilma). See poliitika v\u00f5imaldab kasutada k\u00f5iki saadaval olevaid teid salvestusruumile. ALUA korral kasutatakse ainult teid kontrollile, mis omab LUN-i. K\u00f5ikidel salvestusruumidel ESXi-s ei pruugi olla vaikimisi reegleid, mis m\u00e4\u00e4ravad Round-Robini poliitika. Kui teie salvestusruumi jaoks reeglit ei ole, kasutage salvestusruumi tootja pluginat, mis loob vastava reegli k\u00f5igi klastrihostide jaoks, v\u00f5i looge reegel ise. \u00dcksikasjad <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2053628\">siin<\/a><\/noindex>.\u00a0<\/p>\n<p>Samuti soovitavad m\u00f5ned salvestusruumi tootjad muuta IOPS-i arvu teel vaikes\u00e4ttest 1000-1. Meie praktikas on see v\u00f5imaldanud salvestusruumilt rohkem j\u00f5udlust \"v\u00e4lja pigistada\" ning oluliselt v\u00e4hendada aega, mis on vajalik rikkest taastumiseks v\u00f5i kontrollide uuendamiseks. Kontrollige tootja soovitusi ja kui vastun\u00e4idustusi pole, proovige seda parameetrit muuta. \u00dcksikasjad <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2069356\">siin<\/a><\/noindex>.<\/p>\n<h3>Virtuaalse masina kettas\u00fcsteemi peamised j\u00f5udluse n\u00e4itajad<\/h3>\n<p>\nvCenteris kogutud kettas\u00fcsteemi j\u00f5udluse n\u00e4itajad on jagatud jaotistele Datastore, Disk, Virtual Disk:<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasinate j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 3: Salvestamine\" src=\"\/wp-content\/uploads\/2019\/07\/ae852a6a128914a7aff36f461c5f0721.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n <br \/>\nJaotises <b>Datastore<\/b> sisaldavad vSphere (datastore) kettahoidlate meetrikaid, kus paiknevad VM-i kettad. Siit leiate standardseid n\u00e4itajaid:<\/p>\n<ul>\n<li>IOPS-i (keskmised lugemis-\/kirjutamise p\u00e4ringud sekundis),\u00a0<\/li>\n<li>l\u00e4bivoolu (lugemise\/kirjutamise kiirus),\u00a0<\/li>\n<li>latentsuse (lugemise\/kirjutamise\/k\u00f5rgeim latentsus).<\/li>\n<\/ul>\n<p>\nNimekirjadest on p\u00f5him\u00f5tteliselt k\u00f5ik arusaadav. Kordan veel, et siin statistika ei kehti konkreetse VM-i (v\u00f5i VM-i kettad) kohta, vaid on \u00fcldine kogu datastore'i kohta. Minu arvates on seda statistikat mugavam vaadata ESXTOP-is, arvestades, et seal on minimaalne m\u00f5\u00f5tmise aeg 2 sekundit.<\/p>\n<p>Jaotises <b>Ketas<\/b> sisaldavad blokkseadmestike metrikaid, mida VM kasutab. Siin on n\u00e4itajad IOPS-i t\u00fc\u00fcbi summatsioon (sisend-\/v\u00e4ljundoperatsioonide arv m\u00f5\u00f5tmise perioodi jooksul) ja mitmeid n\u00e4itajaid, mis on seotud plokkjuurdep\u00e4\u00e4suga (Commands aborted, Bus resets). Minu arvates on ka seda teavet mugavam vaadata ESXTOP-is.<\/p>\n<p>Jaotis <b>Virtuaalne ketas<\/b> \u2013 k\u00f5ige kasulikum t\u00f6\u00f6riist, et tuvastada virtuaalmasina ketas\u00fcsteemi j\u00f5udlusprobleeme. Siit on v\u00f5imalik vaadata j\u00f5udlust iga virtuaalse ketta l\u00f5ikes. Just seda teavet on vaja, et m\u00f5ista, kas konkreetse virtuaalmasinaga on probleem. Lisaks standardsetele sisenemise\/sisenemisoperatsioonide, lugemise\/kirjutamise mahu ja latentsuse m\u00f5\u00f5dikutele on sellesse jao lisatud ka kasulikud m\u00f5\u00f5dikud, mis n\u00e4itavad ploki suurust: lugemise\/kirjutamise p\u00e4ringu suurus.<\/p>\n<p>Alloleval pildil on virtuaalmasina ketta j\u00f5udluse graafik, kus on n\u00e4ha IOPS, latentsus ja ploki suurus.\u00a0<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasinate j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 3: Salvestamine\" src=\"\/wp-content\/uploads\/2019\/07\/36d2a4d006d2c1bfd4d9961c745f26b6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKuna SIOC on sisse l\u00fclitatud, saab j\u00f5udlusm\u00f5\u00f5dikuid vaadata ka kogu andmehoidlas. Siin on esitatud p\u00f5hiteave keskmise latentsuse ja IOPS-ide kohta. Vaikimisi saab seda teavet vaadata ainult reaalajas.<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasinate j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 3: Salvestamine\" src=\"\/wp-content\/uploads\/2019\/07\/7872dd131008dfdae09141553b4e42f6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>ESXTOP<\/h3>\n<p>\nESXTOP-is on mitu ekraani, mis n\u00e4itavad hosti ketas\u00fcsteemi, eraldi virtuaalmasinate ja nende ketaste teavet.<\/p>\n<p>Alustame virtuaalmasinate teabest. Ekraani \"Disk VM\" avatakse klahvi \"v\" abil:<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasinate j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 3: Salvestamine\" src=\"\/wp-content\/uploads\/2019\/07\/793273e19fca1e4f19b96204202019fb.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>NVDISK<\/b> \u2013 see on virtuaalmasinate kettaste arv. Iga ketta teabe vaatamiseks vajutage \"e\" ja sisestage huvipakkuva virtuaalmasina GID.<\/p>\n<p>\u00dclej\u00e4\u00e4nud parameetrite t\u00e4hendused selles ekraanil on selged nende nimedest.<\/p>\n<p>Veel \u00fcks kasulik ekraan probleemide tuvastamiseks on Disk adapter. See avatakse klahvi \"d\" abil (alloleval pildil on valitud v\u00e4ljad A, B, C, D, E, G):<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasinate j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 3: Salvestamine\" src=\"\/wp-content\/uploads\/2019\/07\/71a7f1e3f1e40f3dbacf61385a3c07cc.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>NPTH<\/b> \u2013 n\u00e4htavate teede arv lunadele, mis on n\u00e4htavad antud adapterilt. Iga tee teabe saamiseks adapteril vajutage \"e\" ja sisestage adapteri nimi:<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasinate j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 3: Salvestamine\" src=\"\/wp-content\/uploads\/2019\/07\/12661003ce8be542ed4c5e262da77d90.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>AQLEN<\/b> \u2013 maksimaalne j\u00e4rjekorra suurus adapteril.<\/p>\n<p>Samuti on selles ekraanil esitatud latentsuse m\u00f5\u00f5dikud, millest ma eespool r\u00e4\u00e4kisin: <b>KAVG\/cmd, GAVG\/cmd, DAVG\/cmd, QAVG\/cmd<\/b>. <\/p>\n<p>Disk device ekraanil, mille avamine k\u00e4ib klahvi \"u\" abil, on esitatud andmed eraldiseisvate plokkseadmete \u2013 lunade (alloleval pildil on valitud v\u00e4ljad A, B, F, G, I) kohta. Siit on v\u00f5imalik n\u00e4ha lunade j\u00e4rjekorra olekut. <\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasinate j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 3: Salvestamine\" src=\"\/wp-content\/uploads\/2019\/07\/6331ee64398fe7057c0eec015165f0a5.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>DQLEN<\/b> \u2013 plokkseadmest tulev j\u00e4rjekorra suurus.<br \/>\n<b>ACTV<\/b> \u2013 andmeedastusoperatsioonide arv ESXi tuumas.<br \/>\n<b>QUED<\/b> \u2013 j\u00e4rjekorras olevate andmeedastusoperatsioonide arv.<br \/>\n<b>%USD<\/b> \u2013 ACTV \/ DQLEN \u00d7 100%.<br \/>\n<b>LOAD<\/b> \u2013 (ACTV + QUED) \/ DQLEN.<\/p>\n<p>Kui %USD on k\u00f5rge, tuleks kaaluda j\u00e4rjekorra suurendamise v\u00f5imalust. Mida rohkem k\u00e4ske on j\u00e4rjekorras, seda k\u00f5rgem on QAVG ja seega ka KAVG.<\/p>\n<p>Samuti saab Disk device ekraanilt vaadata, kas VAAI (vStorage API for Array Integration) t\u00f6\u00f6tab SCSI-l. Selleks tuleb valida v\u00e4ljad A ja O. <\/p>\n<p>VAAI mehhanism v\u00f5imaldab osa t\u00f6\u00f6st viia h\u00fcperviisoritelt otse SCSI-le, n\u00e4iteks nullimine, plokkide kopeerimine v\u00f5i lukustamine.<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasinate j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 3: Salvestamine\" src=\"\/wp-content\/uploads\/2019\/07\/131342d74e69af9c0898a1b350e883c8.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNagu \u00fclaltoodud pildilt n\u00e4ha, t\u00f6\u00f6tab antud SCSI-l VAAI: aktiivselt kasutatakse Zero ja ATS primitiive.<\/p>\n<h3>Soovitused diskialt s\u00fcsteemi optimeerimiseks ESXi-l<\/h3>\n<p><\/p>\n<ul>\n<li>P\u00f6\u00f6rake t\u00e4helepanu ploki suurusele.<\/li>\n<li>Seadke HBA jaoks optimaalne j\u00e4rjekorra suurus.<\/li>\n<li>\u00c4rge unustage aktiveerida SIOC andmestoodetes.<\/li>\n<li>Valige PSP vastavalt SCSI tootja soovitustele.<\/li>\n<li>Veenduge, et VAAI t\u00f6\u00f6tab.<\/li>\n<\/ul>\n<p>\n<b class=\"spoiler_title\">Kasulikud artiklid teema kohta:<\/b><noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2011\/06\/23\/disk-schednumreqoutstanding-the-story\/\">http:\/\/www.yellow-bricks.com\/2011\/06\/23\/disk-schednumreqoutstanding-the-story\/<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2009\/09\/29\/whats-that-alua-exactly\/\">http:\/\/www.yellow-bricks.com\/2009\/09\/29\/whats-that-alua-exactly\/<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2019\/03\/05\/dqlen-changes-what-is-going-on\/\">http:\/\/www.yellow-bricks.com\/2019\/03\/05\/dqlen-changes-what-is-going-on\/<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/www.codyhosterman.com\/2017\/02\/understanding-vmware-esxi-queuing-and-the-flasharray\/\">https:\/\/www.codyhosterman.com\/2017\/02\/understanding-vmware-esxi-queuing-and-the-flasharray\/<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/www.codyhosterman.com\/2018\/03\/what-is-the-latency-stat-qavg\/\">https:\/\/www.codyhosterman.com\/2018\/03\/what-is-the-latency-stat-qavg\/<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1267\">https:\/\/kb.vmware.com\/s\/article\/1267<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1268\">https:\/\/kb.vmware.com\/s\/article\/1268<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1027901\">https:\/\/kb.vmware.com\/s\/article\/1027901<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2069356\">https:\/\/kb.vmware.com\/s\/article\/2069356<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2053628\">https:\/\/kb.vmware.com\/s\/article\/2053628<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1003469\">https:\/\/kb.vmware.com\/s\/article\/1003469<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/www.vmware.com\/content\/dam\/digitalmarketing\/vmware\/en\/pdf\/techpaper\/performance\/vsphere-esxi-vcenter-server-67-performance-best-practices.pdf\">https:\/\/www.vmware.com\/content\/dam\/digitalmarketing\/vmware\/en\/pdf\/techpaper\/performance\/vsphere-esxi-vcenter-server-67-performance-best-practices.pdf<\/a><\/noindex><\/p>\n<p>Allikas: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/461127\/\">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 \u0427\u0430\u0441\u0442\u044c 2. \u041f\u0440\u043e Memory \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u0440\u0430\u0437\u0431\u0435\u0440\u0435\u043c \u043c\u0435\u0442\u0440\u0438\u043a\u0438 \u0434\u0438\u0441\u043a\u043e\u0432\u043e\u0439 \u043f\u043e\u0434\u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0432 vSphere. \u041f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0441\u043e \u0441\u0442\u043e\u0440\u0430\u0434\u0436\u0435\u043c \u2013 \u0441\u0430\u043c\u0430\u044f \u0447\u0430\u0441\u0442\u0430\u044f \u043f\u0440\u0438\u0447\u0438\u043d\u0430 \u043c\u0435\u0434\u043b\u0435\u043d\u043d\u043e\u0439 \u0440\u0430\u0431\u043e\u0442\u044b \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0439 \u043c\u0430\u0448\u0438\u043d\u044b. \u0415\u0441\u043b\u0438 \u0432 \u0441\u043b\u0443\u0447\u0430\u044f\u0445 \u0441 CPU \u0438 RAM \u0442\u0440\u0430\u0431\u043b\u0448\u0443\u0442\u0438\u043d\u0433 \u0437\u0430\u043a\u0430\u043d\u0447\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 \u0433\u0438\u043f\u0435\u0440\u0432\u0438\u0437\u043e\u0440\u0430, \u0442\u043e \u043f\u0440\u0438 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430\u0445 \u0441 \u0434\u0438\u0441\u043a\u043e\u043c, \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e, \u043f\u0440\u0438\u0434\u0435\u0442\u0441\u044f \u0440\u0430\u0437\u0431\u0438\u0440\u0430\u0442\u044c\u0441\u044f \u0441 \u0441\u0435\u0442\u044c\u044e \u043f\u0435\u0440\u0435\u0434\u0430\u0447\u0438 \u0434\u0430\u043d\u043d\u044b\u0445 \u0438 \u0421\u0425\u0414. \u0422\u0435\u043c\u0443 \u0431\u0443\u0434\u0443 \u0440\u0430\u0437\u0431\u0438\u0440\u0430\u0442\u044c [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":27306,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-36486","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.1.1 - 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\/et\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.1.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"et_EE\" \/>\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 3: Storage | ProHoster\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage\" \/>\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:11:54+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:11:54+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\udd47VM-i j\u00f5udluse anal\u00fc\u00fcs VMware vSphere'is. Osa 3: Storage | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"et_EE","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 3: Storage | ProHoster","og:url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","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:11:54+00:00","article:modified_time":"2019-10-31T19:11:54+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"36486","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-22 03:31:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:44:22","updated":"2026-01-22 03:31:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/36486","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/comments?post=36486"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/36486\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media\/27306"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=36486"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=36486"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=36486"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}