{"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":"VM-i j\u00f5udluse anal\u00fc\u00fcs VMware vSphere\u2019s. Osa 3: Salvestus","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"VM-i j\u00f5udluse anal\u00fc\u00fcs VMware vSphere\u2019s. Osa 3: Salvestus\" 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\/\">Jagamisosa 2. M\u00e4lust<\/a><\/noindex><\/p>\n<p>T\u00e4na arutame vSphere'i kettas\u00fcsteemi m\u00f5\u00f5dikuid. Probleemideks salvestusseadmest on k\u00f5ige sagedasem p\u00f5hjus virtuaalmasina aeglane t\u00f6\u00f6tamine. Kui CPU ja RAM-i probleemide t\u00f5rgete lahendamine l\u00f5ppeb h\u00fcperviisori tasemel, siis ketta probleemide korral v\u00f5ib-olla tuleb uurida andmeside v\u00f5rku ja SAN-i.<\/p>\n<p>Teemat hakkan k\u00e4sitlema plokkjuurdep\u00e4\u00e4su SAN-ile, kuigi juhul, kui on tegemist failijuurdep\u00e4\u00e4suga, on m\u00f5\u00f5dikud enam-v\u00e4hem samad.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Natuke teooriat<\/h3>\n<p>\nKui r\u00e4\u00e4gitakse virtuaalmasinate kettas\u00fcsteemi j\u00f5udlusest, p\u00f6\u00f6ratakse tavaliselt t\u00e4helepanu kolmele omavahel seotud parameetrile:<\/p>\n<ul>\n<li>sisse-\/v\u00e4ljemisse operatsioonide arv (Input\/Output Operations Per Second, IOPS);<\/li>\n<li>l\u00e4bivool (Throughput);<\/li>\n<li>sisse-\/v\u00e4ljeoperatsioonide latentsus (Latency).<\/li>\n<\/ul>\n<p>\n<b>IOPS-i arv<\/b> on tavaliselt oluline juhuslikult jaotatud koormuste jaoks: juurdep\u00e4\u00e4s kettablokkidele, mis asuvad erinevates kohtades. N\u00e4iteks v\u00f5ivad sellised koormused olla andmebaasid, \u00e4rirakendused (ERP, CRM) jne.<\/p>\n<p><b>L\u00e4bivool<\/b> j\u00e4rgnevad koormused on olulised: juurdep\u00e4\u00e4s j\u00e4rjestikku paigutatud blokile. N\u00e4iteks v\u00f5ivad sellist koormust genereerida failiserverid (kuigi mitte alati) ja videovalves\u00fcsteemid.<\/p>\n<p>L\u00e4bilaskev\u00f5ime on seotud sisend-\/v\u00e4ljundoperatsioonide arvuga j\u00e4rgmiselt:<\/p>\n<p><i>L\u00e4bilaskev\u00f5ime = IOPS * Bloki suurus<\/i>, kus Bloki suurus \u2013 see on bloki suurus.<\/p>\n<p>Bloki suurus on \u00fcsna oluline omadus. Kaasaegsed ESXi versioonid lubavad blokke suurusega kuni 32 767 KB. Kui blokk on veelgi suurem, jagatakse see mitmeks. Mitte k\u00f5ik andmesalvestuss\u00fcsteemid ei saa t\u00f5husalt t\u00f6\u00f6tada nii suurte blokkidega, seet\u00f5ttu on ESXi T\u00e4iendavates Seadetes parameeter DiskMaxIOSize. Selle abil saab v\u00e4hendada maksimaalset bloki suurust, mida h\u00fcperviisor lubab (rohkem <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1003469\">siit<\/a><\/noindex>). Soovitan enne selle parameetri muutmist konsulteerida andmesalvestuss\u00fcsteemi tootjaga v\u00f5i v\u00e4hemalt testida muudatusi laboris.\u00a0<\/p>\n<p>Boksi suurus v\u00f5ib negatiivselt m\u00f5jutada salvestusseadmestiku j\u00f5udlust. Isegi kui IOPS ja l\u00e4bilaskev\u00f5ime on suhteliselt madalad, v\u00f5ivad suure boksi puhul tekkida suured latentsused. Seega j\u00e4lgige seda parameetrit.<\/p>\n<p><b>Ooteaeg<\/b> \u2013 k\u00f5ige huvitavam j\u00f5udluse parameeter. Virtuaalmasina sisend-v\u00e4ljundoperatsioonide latentsus jaguneb j\u00e4rgnevateks elementideks:<\/p>\n<ul>\n<li>latentsus h\u00fcperviisorisse (KAVG, Average Kernel MilliSec\/Read);<\/li>\n<li>latentsus, mida annavad andmesidev\u00f5rk ja salvestusseade (DAVG, Average Driver MilliSec\/Command).<\/li>\n<\/ul>\n<p>\nK\u00fclastatavas operatsioonis\u00fcsteemis n\u00e4htav kogulatentsus (GAVG, Average Guest MilliSec\/Command) on KAVG ja DAVG summa.<\/p>\n<p>GAVG ja DAVG m\u00f5\u00f5detakse, KAVG aga arvutatakse: GAVG\u2013DAVG.<\/p>\n<p><img decoding=\"async\" alt=\"VM-i j\u00f5udluse anal\u00fc\u00fcs VMware vSphere\u2019s. Osa 3: Salvestus\" 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>R\u00e4\u00e4gime l\u00e4hemalt <b>KAVG<\/b>. Normaalsetes tingimustes peab KAVG p\u00fc\u00fcdlema nulli poole v\u00f5i v\u00e4hemalt olema palju v\u00e4iksem kui DAVG. Ainus juhtum, kus KAVG on ootusp\u00e4raselt k\u00f5rge, on virtuaalmasina kettal IOPS-i piirang. Sellisel juhul KAVG suureneb, kui p\u00fc\u00fctakse \u00fcletada limiiti.<\/p>\n<p>KAVG k\u00f5ige olulisem komponent on QAVG \u2013 ooteaeg h\u00fcperviisoris t\u00f6\u00f6tlemiseks. \u00dclej\u00e4\u00e4nud KAVG komponendid on ebaolulised.<\/p>\n<p>Kett draiveri kett ja lunade j\u00e4rjekorra suurus on fikseeritud. Suure koormusega keskkondades v\u00f5ib osutuda kasulikuks seda suurendada. <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1267\">Siit<\/a><\/noindex> Kirjeldatakse, kuidas suurendada adapteri draiveri j\u00e4rjekordi (samuti suureneb j\u00e4rjekord lunade puhul). See seadistus t\u00f6\u00f6tab, kui lunaga t\u00f6\u00f6tab ainult \u00fcks VM, mida juhtub harva. Kui lunaga t\u00f6\u00f6tab mitu VM-i, tuleb ka parameetrit suurendada <i>Disk.SchedNumReqOutstanding<\/i> (juhend\u00a0 <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1268\">siit<\/a><\/noindex>). J\u00e4rjekorra suurendamine v\u00e4hendab vastavalt QAVG ja KAVG.<\/p>\n<p>Kuid, tutvuge esmalt HBA tootja dokumentatsiooniga ja testige muudatusi laboritingimustes. <\/p>\n<p>Luna j\u00e4rjekorra suurusele v\u00f5ib m\u00f5jutada SIOC (Storage I\/O Control) mehhanismi aktiveerimine. See tagab, et k\u00f5ikide klastriserverite juurdep\u00e4\u00e4s lunale on \u00fchtlane, muutes d\u00fcnaamiliselt lunade j\u00e4rjekorda serverites. See t\u00e4hendab, et kui m\u00f5nel hostil t\u00f6\u00f6tab VM, mis n\u00f5uab proportsionaalselt palju ressursse (m\u00fcrarikka naabri VM), v\u00e4hendab SIOC selle hosti lunade j\u00e4rjekorra pikkust (DQLEN). Lisainfot <noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2019\/03\/05\/dqlen-changes-what-is-going-on\/\">siit<\/a><\/noindex>.<\/p>\n<p>KAVG on selge, n\u00fc\u00fcd r\u00e4\u00e4gime 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 mitte nii kaasaegses SAN-is on oma j\u00f5udlusm\u00f5\u00f5turid. DAVG probleemide anal\u00fc\u00fcsimisel on m\u00f5istlik neid vaadata. Kui ESXi ja SAN-i pool on k\u00f5ik korras, uurige andmeedastusv\u00f5rku.<\/p>\n<p>Kuna teie j\u00f5udlusprobleemide v\u00e4ltimiseks valige oma SAN-i jaoks \u00f5ige teede valiku poliitika (PSP). Praktiselt k\u00f5ik kaasaegsed SAN-id toetavad PSP Round-Robin (kas ALUA, as\u00fcmmeetriline loogiline \u00fcksus v\u00f5i ilma). See poliitika v\u00f5imaldab kasutada k\u00f5iki SAN-i k\u00e4tte saadavaid teid. ALUA puhul kasutatakse ainult tee kontrollijani, kes omab LUN-i. K\u00f5igile SAN-idele, mis t\u00f6\u00f6tavad ESXi-s, ei ole vaikereegleid, mis seataks Round-Robin poliitika. Kui teie SAN-i jaoks ei ole reeglit, kasutage tootja lisandmoodulit, mis loob vastava reegli k\u00f5igil klastrihostidel, v\u00f5i looge reegel ise. \u00dcksikasjad <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2053628\">siit<\/a><\/noindex>.\u00a0<\/p>\n<p>Samuti soovitavad m\u00f5ned andmesalvestusseadmete tootjad muuta IOPS-i v\u00e4\u00e4rtust tavalisest 1000 1-ks. Meie praktikas on see v\u00f5imaldanud andmesalvestusseadmest rohkem j\u00f5udlust \u201ev\u00e4lja pigistada\u201d ja oluliselt v\u00e4hendada aega, mis on vajalik failoveri jaoks juhul, kui kontrollereid tuleb v\u00e4lja vahetada v\u00f5i v\u00e4rskendada. Kontrollige tootja soovitusi ja kui vastun\u00e4idustusi ei ole, proovige seda parameetrit muuta. \u00dcksikasjad <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2069356\">siit<\/a><\/noindex>.<\/p>\n<h3>Virtuaalkonfiguratsiooni kettaaluste j\u00f5udluse peamised m\u00f5\u00f5dikud<\/h3>\n<p>\nvCenteris on kettaaluste j\u00f5udluse m\u00f5\u00f5dikud koondatud sektsioonidesse Datastore, Disk, Virtual Disk:<\/p>\n<p><img decoding=\"async\" alt=\"VM-i j\u00f5udluse anal\u00fc\u00fcs VMware vSphere\u2019s. Osa 3: Salvestus\" src=\"\/wp-content\/uploads\/2019\/07\/ae852a6a128914a7aff36f461c5f0721.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n <br \/>\nJaotises <b>Datastore<\/b> sisaldab vSphere'i (andmesalvestuse) kettaaluste m\u00f5\u00f5dikuid, millel asuvad VM-i ketad. Siit leiate standardm\u00f5\u00f5dikud:<\/p>\n<ul>\n<li>IOPS (Keskmised lugemis-\/kirjutamisv\u00f5imekused sekundis),\u00a0<\/li>\n<li>l\u00e4bilaskev\u00f5ime (Lugemis-\/kirjutamiskiirus),\u00a0<\/li>\n<li>viivitused (Lugemis-\/kirjutamis-\/k\u00f5rgeim viivitus).<\/li>\n<\/ul>\n<p>\nM\u00f5\u00f5dikute nimed on p\u00f5him\u00f5tteliselt arusaadavad. T\u00f5stan veelkord esile, et siin on statistika mitte konkreetse VM-i (v\u00f5i VM-i ketta) kohta, vaid kogu datastori kohta. Minu arvates on neid statistikameetreid mugavam vaadata ESXTOP-is, arvestades, et seal on minimaalne m\u00f5\u00f5teperiood 2 sekundit.<\/p>\n<p>Jaotises <b>Disk<\/b> siis on olemas m\u00f5\u00f5dikud plokkseadmete kohta, mida VM-id kasutavad. Siin on IOPS t\u00fc\u00fcpide summaarne (sisse-\/v\u00e4ljundoperatsioonide arv m\u00f5\u00f5tmisperioodi jooksul) ja mitu m\u00f5\u00f5dikut, mis on seotud plokki ligip\u00e4\u00e4suga (Commands aborted, Bus resets). Selle teabe j\u00e4lgimine on minu arvates mugavam vaadata ka ESXTOP-is.<\/p>\n<p>Jaotis <b>Virtuaalne ketas<\/b> on k\u00f5ige kasulikum, kui vaadata probleemide leidmisel, mis on seotud diskis\u00fcsteemi j\u00f5udlusega. Siit saab vaadata iga virtuaalse ketta tulemuslikkust. Just see teave on vajalik, et m\u00f5ista, kas konkreetse virtuaalmasina puhul on probleem. Lisaks standardm\u00f5\u00f5dikutele nagu sisse-\/v\u00e4ljundoperatsioonide arv, lugemise\/kirjutamise maht ja viivitused, on selles jaotises kasulikud m\u00f5\u00f5dikud, mis n\u00e4itavad ploki suurust: Read\/Write request size.<\/p>\n<p>Alloleval pildil on virtuaalse ketta j\u00f5udluse graafik, kus on n\u00e4ha IOPS, viivitused ja ploki suurus.\u00a0<\/p>\n<p><img decoding=\"async\" alt=\"VM-i j\u00f5udluse anal\u00fc\u00fcs VMware vSphere\u2019s. Osa 3: Salvestus\" src=\"\/wp-content\/uploads\/2019\/07\/36d2a4d006d2c1bfd4d9961c745f26b6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nSamuti v\u00f5id j\u00e4lgida j\u00f5udlust k\u00f5igi andmesalvestite kohta, kui SIOC on sisse l\u00fclitatud. Siin on esitatud p\u00f5hiteave keskmise Latency ja IOPS'ide kohta. Vaikimisi on seda teavet v\u00f5imalik vaadata ainult reaalajas.<\/p>\n<p><img decoding=\"async\" alt=\"VM-i j\u00f5udluse anal\u00fc\u00fcs VMware vSphere\u2019s. Osa 3: Salvestus\" 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, kus esitatakse teave hosti diskialli s\u00fcsteemi, eraldi virtuaalsete masinate ja nende diskide kohta.<\/p>\n<p>Alustame teabest virtuaalsete masinate kohta. Ekraan \"Disk VM\" k\u00e4ivitatakse klahviga \"v\":<\/p>\n<p><img decoding=\"async\" alt=\"VM-i j\u00f5udluse anal\u00fc\u00fcs VMware vSphere\u2019s. Osa 3: Salvestus\" src=\"\/wp-content\/uploads\/2019\/07\/793273e19fca1e4f19b96204202019fb.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>NVDISK<\/b> \u2013 see on VM-ide ketaste arv. Iga ketta teabe n\u00e4gemiseks vajuta \"e\" ja sisesta huvipakkuva VM-i GID.<\/p>\n<p>\u00dclej\u00e4\u00e4nud parameetrite v\u00e4\u00e4rtused sellel ekraanil on selged nende nimetustest.<\/p>\n<p>Veel \u00fcks kasulik ekraan probleemide otsimiseks on Disk adapter. Selle kutsub esile klahv \"d\" (alloleval pildil on valitud v\u00e4ljad A, B, C, D, E, G):<\/p>\n<p><img decoding=\"async\" alt=\"VM-i j\u00f5udluse anal\u00fc\u00fcs VMware vSphere\u2019s. Osa 3: Salvestus\" src=\"\/wp-content\/uploads\/2019\/07\/71a7f1e3f1e40f3dbacf61385a3c07cc.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>NPTH<\/b> \u2013 teede arv lunadele, mis on n\u00e4htavad antud adaptriga. Iga tee teabe saamiseks adaptril vajuta \"e\" ja sisesta adaptri nimi:<\/p>\n<p><img decoding=\"async\" alt=\"VM-i j\u00f5udluse anal\u00fc\u00fcs VMware vSphere\u2019s. Osa 3: Salvestus\" 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 adaptris.<\/p>\n<p>Samuti on sellel ekraanil esitatud viivituse loendurid, millest ma varem r\u00e4\u00e4kisin: <b>KAVG\/cmd, GAVG\/cmd, DAVG\/cmd, QAVG\/cmd<\/b>. <\/p>\n<p>Disk device ekraanil, millele p\u00e4\u00e4seb ligi klahviga \"u\", on esitatud teave \u00fcksikute plokkseadmete - lunade kohta (alloleval pildil on valitud v\u00e4ljad A, B, F, G, I). Siit on n\u00e4ha, milline on j\u00e4rjekorra seisund lunade jaoks. <\/p>\n<p><img decoding=\"async\" alt=\"VM-i j\u00f5udluse anal\u00fc\u00fcs VMware vSphere\u2019s. Osa 3: Salvestus\" src=\"\/wp-content\/uploads\/2019\/07\/6331ee64398fe7057c0eec015165f0a5.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>DQLEN<\/b> \u2013 plokkseadmestiku j\u00e4rjekorra suurus.<br \/>\n<b>ACTV<\/b> \u2013 k\u00e4skude\/andmete arv ESXi tuumas.<br \/>\n<b>QUED<\/b> \u2013 k\u00e4skude\/andmete arv j\u00e4rjekorras.<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 suurendamist. Mida rohkem k\u00e4sklusi j\u00e4rjekorras, seda k\u00f5rgem on QAVG ja seega KAVG.<\/p>\n<p>Disk device ekraanil saab samuti vaadata, kas VAAI (vStorage API for Array Integration) on HKA-l aktiivne. Selleks tuleb valida v\u00e4ljad A ja O. <\/p>\n<p>VAAI mehhanism v\u00f5imaldab osaliselt \u00fcle kanda t\u00f6\u00f6d h\u00fcperviisorilt otse HKA-le, n\u00e4iteks nullimist, plokkide kopeerimist v\u00f5i lukustusi.<\/p>\n<p><img decoding=\"async\" alt=\"VM-i j\u00f5udluse anal\u00fc\u00fcs VMware vSphere\u2019s. Osa 3: Salvestus\" src=\"\/wp-content\/uploads\/2019\/07\/131342d74e69af9c0898a1b350e883c8.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNagu eeltoodud pildilt n\u00e4ha, t\u00f6\u00f6tab VAAI antud HKA-l: aktiivselt kasutatakse Zero ja ATS primitiive.<\/p>\n<h3>N\u00f5uanded, kuidas optimeerida diskis\u00fcsteemi t\u00f6\u00f6d ESXi-s<\/h3>\n<p><\/p>\n<ul>\n<li>P\u00f6\u00f6rake t\u00e4helepanu ploki suurusele.<\/li>\n<li>Seadke HBA-le optimaalne j\u00e4rjekorra suurus.<\/li>\n<li>\u00c4rge unustage SIOC-i sisse l\u00fclitada andmestoorides.<\/li>\n<li>Valige PSP vastavalt salvestusseadmestiku tootja soovitustele.<\/li>\n<li>Veenduge, et VAAI t\u00f6\u00f6tab.<\/li>\n<\/ul>\n<p>\n<b class=\"spoiler_title\">Kasuartiklid teemal:<\/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 4.9.10 - aioseo.com -->\n\t<meta name=\"description\" content=\"\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\" \/>\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) 4.9.10\" \/>\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:description\" content=\"\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\" \/>\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: Salvestus | ProHoster","description":"Osa 1. Pro CPU Osa 2. Pro Memory T\u00e4nap\u00e4eval vaatame l\u00e4hemalt vSphere'i salvestuss\u00fcsteemi m\u00f5\u00f5dikuid. Salvestusprobleem on k\u00f5ige levinum p\u00f5hjus virtuaalmasinate aeglaseks t\u00f6\u00f6ks. Kui CPU ja RAM-i t\u00f5rkeotsimine l\u00f5peb h\u00fcperviisori tasemel, siis ketasprobleemide korral v\u00f5ib osutuda vajalikuks tegeleda andmesidev\u00f5rgu ja salvestusseadmestikuga. Teemat hakkan arutama","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:description":"\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","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"},"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}]}}