{"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\/sk\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","title":{"rendered":"Anal\u00fdza v\u00fdkonnosti VM v VMware vSphere. \u010cas\u0165 3: Ukladanie d\u00e1t","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonnosti VM v VMware vSphere. \u010cas\u0165 3: Ukladanie d\u00e1t\" 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\/\">\u010cas\u0165 1. O CPU<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/455820\/\">\u010cas\u0165 2. O pam\u00e4ti<\/a><\/noindex><\/p>\n<p>Dnes sa zameriame na metriky diskov\u00e9ho subsyst\u00e9mu vo vSphere. Probl\u00e9my so skladovan\u00edm s\u00fa naj\u010dastej\u0161ou pr\u00ed\u010dinou pomal\u00e9ho fungovania virtu\u00e1lnych strojov. K\u00fdm v pr\u00edpadoch s CPU a RAM sa rie\u0161enie probl\u00e9mov kon\u010d\u00ed na \u00farovni hyperv\u00edzora, pri probl\u00e9moch s diskom m\u00f4\u017ee by\u0165 potrebn\u00e9 pos\u00fadi\u0165 aj sie\u0165 pren\u00e1\u0161ania d\u00e1t a \u00falo\u017en\u00e9 syst\u00e9my.<\/p>\n<p>T\u00e9mu budem rozobera\u0165 na pr\u00edklade blokov\u00e9ho pr\u00edstupu k \u00falo\u017en\u00fdm syst\u00e9mom, aj ke\u010f pri s\u00faborovom pr\u00edstupe s\u00fa po\u010d\u00edta\u010de pribli\u017ene tie ist\u00e9.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Trochu te\u00f3rie<\/h3>\n<p>\nKe\u010f sa hovor\u00ed o v\u00fdkonnosti diskov\u00e9ho subsyst\u00e9mu virtu\u00e1lnych strojov, zvy\u010dajne sa pozornos\u0165 venuje trom vz\u00e1jomne prepojen\u00fdm parametrom:<\/p>\n<ul>\n<li>po\u010det oper\u00e1ci\u00ed vstupu\/v\u00fdstupu (Input\/Output Operations Per Second, IOPS);<\/li>\n<li>priepustnosti (Throughput);<\/li>\n<li>zdr\u017eaniu oper\u00e1ci\u00ed vstupu\/v\u00fdstupu (Latency).<\/li>\n<\/ul>\n<p>\n<b>Po\u010det IOPS<\/b> je zvy\u010dajne d\u00f4le\u017eit\u00fd pre n\u00e1klady n\u00e1hodn\u00e9ho charakteru (random): pr\u00edstup k blokom na disku, ktor\u00e9 s\u00fa umiestnen\u00e9 na r\u00f4znych miestach. Pr\u00edkladom takejto z\u00e1\u0165a\u017ee m\u00f4\u017eu by\u0165 datab\u00e1zy, obchodn\u00e9 aplik\u00e1cie (ERP, CRM) a podobne.<\/p>\n<p><b>Priemern\u00e1 priepustnos\u0165<\/b> je d\u00f4le\u017eit\u00e1 pre n\u00e1klady sekven\u010dn\u00e9ho charakteru: pr\u00edstup k blokom umiestnen\u00fdm za sebou. Napr\u00edklad tak\u00fato z\u00e1\u0165a\u017e m\u00f4\u017eu generova\u0165 s\u00faborov\u00e9 servery (nie v\u017edy) a syst\u00e9my na sledovanie videa.<\/p>\n<p>Priepustnos\u0165 s\u00favis\u00ed s po\u010dtom oper\u00e1ci\u00ed vstupu\/v\u00fdstupu nasledovne:<\/p>\n<p><i>Throughput = IOPS * Ve\u013ekos\u0165 bloku<\/i>, kde Ve\u013ekos\u0165 bloku je ve\u013ekos\u0165 bloku.<\/p>\n<p>Ve\u013ekos\u0165 bloku je pomerne d\u00f4le\u017eit\u00e1 charakteristika. Modern\u00e9 verzie ESXi podporuj\u00fa bloky s ve\u013ekos\u0165ou a\u017e 32 767 KB. Ak je blok e\u0161te v\u00e4\u010d\u0161\u00ed, del\u00ed sa na nieko\u013eko. Nie v\u0161etky \u00falo\u017en\u00e9 syst\u00e9my m\u00f4\u017eu efekt\u00edvne pracova\u0165 s tak\u00fdmi ve\u013ek\u00fdmi blokmi, a preto v pokro\u010dil\u00fdch nastaveniach ESXi existuje parameter DiskMaxIOSize. Pomocou neho je mo\u017en\u00e9 zn\u00ed\u017ei\u0165 maxim\u00e1lnu ve\u013ekos\u0165 bloku, ktor\u00fd hyperv\u00edzor prech\u00e1dza (podrobnej\u0161ie <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1003469\">tu<\/a><\/noindex>). Odpor\u00fa\u010dam pred zmenou tohto parametra konzultova\u0165 s v\u00fdrobcom \u00falo\u017en\u00e9ho syst\u00e9mu alebo aspo\u0148 otestova\u0165 zmeny na laborat\u00f3rnom st\u00e1nku.\u00a0<\/p>\n<p>Ve\u013ek\u00e1 ve\u013ekos\u0165 bloku m\u00f4\u017ee ma\u0165 negat\u00edvny vplyv na v\u00fdkonnos\u0165 \u00falo\u017en\u00e9ho syst\u00e9mu. Aj ke\u010f je po\u010det IOPS a throughput relat\u00edvne mal\u00fd, pri ve\u013ekej ve\u013ekosti bloku m\u00f4\u017eu nast\u00e1va\u0165 vysok\u00e9 zdr\u017eania. Preto venujte pozornos\u0165 tomuto parametru.<\/p>\n<p><b>Latency<\/b> \u2013 najzauj\u00edmavej\u0161\u00ed parameter v\u00fdkonnosti. Zdr\u017eanie oper\u00e1ci\u00ed vstupu\/v\u00fdstupu pre virtu\u00e1lny po\u010d\u00edta\u010d sa sklad\u00e1 z:<\/p>\n<ul>\n<li>zdr\u017eania v r\u00e1mci hyperv\u00edzora (KAVG, Priemern\u00fd \u010das v milisekund\u00e1ch z jadra pri \u010d\u00edtan\u00ed);<\/li>\n<li>zdr\u017eania, ktor\u00e9 sp\u00f4sobuje sie\u0165 na prenos d\u00e1t a \u00falo\u017en\u00fd syst\u00e9m (DAVG, Priemern\u00fd \u010das v milisekund\u00e1ch z ovl\u00e1da\u010da na pr\u00edkaz).<\/li>\n<\/ul>\n<p>\nCelkov\u00e9 zdr\u017eanie, ktor\u00e9 je vidite\u013en\u00e9 v hos\u0165ovskom OS (GAVG, Priemern\u00fd \u010das v milisekund\u00e1ch z hostite\u013ea na pr\u00edkaz), je s\u00fa\u010det KAVG a DAVG.<\/p>\n<p>GAVG a DAVG sa meraj\u00fa, zatia\u013e \u010do KAVG sa vypo\u010d\u00edtava: GAVG\u2013DAVG.<\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonnosti VM v VMware vSphere. \u010cas\u0165 3: Ukladanie d\u00e1t\" 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>Zdroj<\/i><\/a><\/noindex><\/p>\n<p>Zastavme sa podrobnej\u0161ie pri <b>KAVG<\/b>. Pri norm\u00e1lnom fungovan\u00ed by mal KAVG smerova\u0165 k nule alebo, aspo\u0148, by\u0165 v\u00fdznamne men\u0161\u00ed ne\u017e DAVG. Jedin\u00fd zn\u00e1my pr\u00edpad, ke\u010f je KAVG o\u010dak\u00e1vane vysok\u00fd, je obmedzenie IOPS na disku VM. V takom pr\u00edpade, pri pokuse o prekro\u010denie limitu, bude KAVG narasta\u0165.<\/p>\n<p>Najv\u00fdznamnej\u0161ou s\u00fa\u010das\u0165ou KAVG je QAVG \u2013 \u010das v rade na spracovanie v r\u00e1mci hyperv\u00edzora. Ostatn\u00e9 zlo\u017eky KAVG s\u00fa zanedbate\u013ene mal\u00e9.<\/p>\n<p>Rada v ovl\u00e1da\u010di diskov\u00e9ho adapt\u00e9ra a rada k lun\u00e1m m\u00e1 pevne stanoven\u00fa ve\u013ekos\u0165. Pre vysoko za\u0165a\u017een\u00e9 prostredia b\u00fdva prospe\u0161n\u00e9 t\u00fato ve\u013ekos\u0165 zv\u00fd\u0161i\u0165. <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1267\">Tu<\/a><\/noindex> opisuje, ako zv\u00fd\u0161i\u0165 rady v ovl\u00e1da\u010di adapt\u00e9ra (s\u00fa\u010dasne sa zv\u00fd\u0161i rada k lun\u00e1m). Toto nastavenie funguje, ke\u010f s lunou pracuje iba jeden VM, \u010do sa st\u00e1va zriedka. Ak na lune pracuje viac VM, je potrebn\u00e9 tie\u017e zv\u00fd\u0161i\u0165 parameter <i>Disk.SchedNumReqOutstanding<\/i> (in\u0161trukcia\u00a0 <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1268\">tu<\/a><\/noindex>). Zv\u00fd\u0161en\u00edm radu zni\u017eujete QAVG a KAVG pr\u00edslu\u0161ne.<\/p>\n<p>Ale op\u00e4\u0165, najprv sa obozn\u00e1mte s dokument\u00e1ciou od dod\u00e1vate\u013ea HBA a otestujte zmeny na laborat\u00f3rnom stande. <\/p>\n<p>Na ve\u013ekos\u0165 radu k lune m\u00f4\u017ee ma\u0165 vplyv aktiv\u00e1cia mechanizmu SIOC (Storage I\/O Control). Tento mechanizmus zais\u0165uje rovnak\u00fd pr\u00edstup k lune zo strany v\u0161etk\u00fdch serverov klastru prostredn\u00edctvom dynamickej \u00fapravy radu k lune na serveroch. To znamen\u00e1, \u017ee ak na niektorom z hostite\u013eov be\u017e\u00ed VM, ktor\u00e1 potrebuje neprimerane ve\u013ea v\u00fdkonu (noisy neighbor VM), SIOC zni\u017euje d\u013a\u017eku radu k lune na tomto hostite\u013eovi (DQLEN). Podrobnej\u0161ie <noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2019\/03\/05\/dqlen-changes-what-is-going-on\/\">tu<\/a><\/noindex>.<\/p>\n<p>S KAVG sme skon\u010dili, teraz trochu o <b>DAVG<\/b>. Tu je to jednoduch\u00e9: DAVG \u2013 to je zdr\u017eanie, ktor\u00e9 sp\u00f4sobuje vonkaj\u0161ie prostredie (sie\u0165 na prenos d\u00e1t a \u00falo\u017en\u00fd syst\u00e9m). V ka\u017edom modernom a nie ve\u013emi modernom \u00falo\u017enom syst\u00e9me s\u00fa vlastn\u00e9 po\u010d\u00edtadl\u00e1 v\u00fdkonu. Pre anal\u00fdzu probl\u00e9mov s DAVG m\u00e1 zmysel sa na ne pozera\u0165. Ak je v\u0161ak zo strany ESXi a \u00falo\u017en\u00e9ho syst\u00e9mu v\u0161etko v poriadku, kontrolujte sie\u0165 na prenos d\u00e1t.<\/p>\n<p>Aby ste sa vyhli probl\u00e9mom s v\u00fdkonom, vyberte spr\u00e1vnu politiku v\u00fdberu ciest (PSP) pre va\u0161e \u00falo\u017eisko. Takmer v\u0161etky modern\u00e9 \u00falo\u017eisk\u00e1 podporuj\u00fa PSP Round-Robin (s ALUA, Asymetrick\u00fd pr\u00edstup k logickej jednotke, alebo bez). T\u00e1to politika umo\u017e\u0148uje vyu\u017e\u00edva\u0165 v\u0161etky dostupn\u00e9 cesty k \u00falo\u017eisku. V pr\u00edpade ALUA sa pou\u017e\u00edvaj\u00fa len cesty k ovl\u00e1da\u010du, ktor\u00fd vlastn\u00ed LUN. Nie v\u0161etky \u00falo\u017eisk\u00e1 na ESXi maj\u00fa predvolen\u00e9 pravidl\u00e1, ktor\u00e9 nastavuj\u00fa politiku Round-Robin. Ak pre va\u0161e \u00falo\u017eisko pravidlo neexistuje, pou\u017eite plugin od v\u00fdrobcu \u00falo\u017eiska, ktor\u00fd vytvor\u00ed zodpovedaj\u00face pravidlo na v\u0161etk\u00fdch hostite\u013eoch klastru, alebo vytvorte pravidlo sami. Podrobnosti <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2053628\">tu<\/a><\/noindex>.\u00a0<\/p>\n<p>Niektor\u00ed v\u00fdrobcovia \u00falo\u017e\u00edsk tie\u017e odpor\u00fa\u010daj\u00fa zmeni\u0165 po\u010det IOPS na ceste zo \u0161tandardnej hodnoty 1000 na 1. V na\u0161ej praxi to umo\u017enilo \u201evytiahnu\u0165\u201c z \u00falo\u017eiska viac v\u00fdkonu a v\u00fdrazne skr\u00e1ti\u0165 \u010das potrebn\u00fd na failover v pr\u00edpade zlyhania alebo aktualiz\u00e1cie ovl\u00e1da\u010dov. Porovnajte sa s odpor\u00fa\u010daniami dod\u00e1vate\u013ea a ak nie s\u00fa \u017eiadne kontraindik\u00e1cie, sk\u00faste zmeni\u0165 tento parameter. Podrobnosti <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2069356\">tu<\/a><\/noindex>.<\/p>\n<h3>Hlavn\u00e9 ukazovatele v\u00fdkonu diskov\u00e9ho subsyst\u00e9mu virtu\u00e1lneho stroja<\/h3>\n<p>\nUkazovatele v\u00fdkonu diskov\u00e9ho subsyst\u00e9mu vo vCenter s\u00fa zhroma\u017eden\u00e9 v sekci\u00e1ch Datastore, Disk, Virtual Disk:<\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonnosti VM v VMware vSphere. \u010cas\u0165 3: Ukladanie d\u00e1t\" src=\"\/wp-content\/uploads\/2019\/07\/ae852a6a128914a7aff36f461c5f0721.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n <br \/>\nV sekcii <b>Datastore<\/b> s\u00fa metriky diskov\u00fdch \u00falo\u017e\u00edsk vSphere (datastore), na ktor\u00fdch s\u00fa umiestnen\u00e9 disky VM. Tu n\u00e1jdete \u0161tandardn\u00e9 ukazovatele pre:<\/p>\n<ul>\n<li>IOPS (Priemern\u00e9 \u010d\u00edtacie\/zapisovacie po\u017eiadavky za sekundu),\u00a0<\/li>\n<li>priepustnos\u0165 (R\u00fdchlos\u0165 \u010d\u00edtania\/z\u00e1pisu),\u00a0<\/li>\n<li>oneskorenie (\u010c\u00edtacie\/Zapisovacie\/NaHighest oneskorenie).<\/li>\n<\/ul>\n<p>\nZ n\u00e1zvov ukazovate\u013eov je v podstate v\u0161etko jasn\u00e9. E\u0161te raz zd\u00f4razn\u00edm, \u017ee tu \u0161tatistika nie je pre konkr\u00e9tny VM (alebo disk VM), ale celkov\u00e1 pre cel\u00e9 datastore. Pod\u013ea m\u00f4jho n\u00e1zoru je t\u00fato \u0161tatistiku pohodlnej\u0161ie sledova\u0165 v ESXTOP, aspo\u0148 kv\u00f4li tomu, \u017ee minim\u00e1lny interval merania tam je 2 sekundy.<\/p>\n<p>V sekcii <b>Disk<\/b> s\u00fa metriky pre blokov\u00e9 zariadenia, ktor\u00e9 sa pou\u017e\u00edvaj\u00fa VM. Tu s\u00fa ukazovatele pre IOPS typu summation (po\u010det oper\u00e1ci\u00ed vstupu\/v\u00fdstupu za merac\u00ed interval) a nieko\u013eko ukazovate\u013eov, ktor\u00e9 sa t\u00fdkaj\u00fa blokov\u00e9ho pr\u00edstupu (Commands aborted, Bus resets). T\u00fato inform\u00e1ciu, pod\u013ea m\u00f4jho n\u00e1zoru, je taktie\u017e pohodlnej\u0161ie sledova\u0165 v ESXTOP.<\/p>\n<p>Sekcia <b>Virtual Disk<\/b> \u2013 je najviac u\u017eito\u010dn\u00fd z h\u013eadiska vyh\u013ead\u00e1vania probl\u00e9mov s v\u00fdkonom diskov\u00e9ho subsyst\u00e9mu VM. Tu si m\u00f4\u017eete pozrie\u0165 v\u00fdkon ka\u017ed\u00e9ho virtu\u00e1lneho disku. Pr\u00e1ve tieto inform\u00e1cie s\u00fa potrebn\u00e9 na zistenie, \u010di m\u00e1 konkr\u00e9tna virtu\u00e1lna ma\u0161ina probl\u00e9my. Okrem \u0161tandardn\u00fdch \u010d\u00edta\u010dov po\u010dtu oper\u00e1ci\u00ed vstupu\/v\u00fdstupu, objemu \u010d\u00edtania\/p\u00edsania a latenci\u00ed s\u00fa v tejto sekcii pr\u00edtomn\u00e9 u\u017eito\u010dn\u00e9 \u010d\u00edta\u010de, ktor\u00e9 ukazuj\u00fa ve\u013ekos\u0165 bloku: Ve\u013ekos\u0165 po\u017eiadavky na \u010d\u00edtanie\/p\u00edsanie.<\/p>\n<p>Na obr\u00e1zku ni\u017e\u0161ie je graf v\u00fdkonu disku VM, na ktorom m\u00f4\u017eete vidie\u0165 mno\u017estvo IOPS, latencie a ve\u013ekos\u0165 bloku.\u00a0<\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonnosti VM v VMware vSphere. \u010cas\u0165 3: Ukladanie d\u00e1t\" src=\"\/wp-content\/uploads\/2019\/07\/36d2a4d006d2c1bfd4d9961c745f26b6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTakisto m\u00f4\u017eete zobrazi\u0165 metriky v\u00fdkonu pre cel\u00fd d\u00e1tov\u00fd sklad, ak je povolen\u00e9 SIOC. Tu s\u00fa z\u00e1kladn\u00e9 inform\u00e1cie o priemernej latencii a IOPS. Predvolene je mo\u017en\u00e9 tieto inform\u00e1cie zobrazi\u0165 iba v re\u00e1lnom \u010dase.<\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonnosti VM v VMware vSphere. \u010cas\u0165 3: Ukladanie d\u00e1t\" src=\"\/wp-content\/uploads\/2019\/07\/7872dd131008dfdae09141553b4e42f6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>ESXTOP<\/h3>\n<p>\nV ESXTOP je nieko\u013eko obrazoviek, na ktor\u00fdch s\u00fa zobrazen\u00e9 inform\u00e1cie o diskovom subsyst\u00e9me hostite\u013ea ako celku, jednotliv\u00fdch virtu\u00e1lnych strojoch a ich diskoch.<\/p>\n<p>Za\u010dneme s inform\u00e1ciami o virtu\u00e1lnych strojoch. Obrazovka \u201eDisk VM\u201c je vyvolan\u00e1 kl\u00e1vesou \u201ev\u201c:<\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonnosti VM v VMware vSphere. \u010cas\u0165 3: Ukladanie d\u00e1t\" src=\"\/wp-content\/uploads\/2019\/07\/793273e19fca1e4f19b96204202019fb.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>NVDISK<\/b> \u2013 to je po\u010det diskov VM. Ak chcete zobrazi\u0165 inform\u00e1cie o ka\u017edom disku, stla\u010dte \u201ee\u201c a zadajte GID zauj\u00edmav\u00e9ho VM.<\/p>\n<p>Hodnoty ostatn\u00fdch parametrov na tejto obrazovke s\u00fa jasn\u00e9 zo svojich n\u00e1zvov.<\/p>\n<p>\u010eal\u0161ia u\u017eito\u010dn\u00e1 obrazovka pri h\u013eadan\u00ed probl\u00e9mov je \u2013 Disk adapter. Vyvol\u00e1va sa kl\u00e1vesou \u201ed\u201c (na obr\u00e1zku ni\u017e\u0161ie s\u00fa vybran\u00e9 polia A,B,C,D,E,G):<\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonnosti VM v VMware vSphere. \u010cas\u0165 3: Ukladanie d\u00e1t\" src=\"\/wp-content\/uploads\/2019\/07\/71a7f1e3f1e40f3dbacf61385a3c07cc.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>NPTH<\/b> \u2013 po\u010det ciest k lun\u00e1m, ktor\u00e9 s\u00fa vidite\u013en\u00e9 z tohto adapt\u00e9ra. Ak chcete z\u00edska\u0165 inform\u00e1cie o ka\u017edej ceste na adapt\u00e9ri, stla\u010dte \u201ee\u201c a zadajte n\u00e1zov adapt\u00e9ra:<\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonnosti VM v VMware vSphere. \u010cas\u0165 3: Ukladanie d\u00e1t\" src=\"\/wp-content\/uploads\/2019\/07\/12661003ce8be542ed4c5e262da77d90.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>AQLEN<\/b> \u2013 maxim\u00e1lna ve\u013ekos\u0165 fronty na adapt\u00e9ri.<\/p>\n<p>Na tejto obrazovke s\u00fa taktie\u017e zobrazen\u00e9 \u010d\u00edta\u010de latenci\u00ed, o ktor\u00fdch som hovoril vy\u0161\u0161ie: <b>KAVG\/cmd, GAVG\/cmd, DAVG\/cmd, QAVG\/cmd<\/b>. <\/p>\n<p>Na obrazovke Disk device, ktor\u00e1 sa vyvol\u00e1 kl\u00e1vesou \u201eu\u201c, s\u00fa zobrazen\u00e9 inform\u00e1cie o jednotliv\u00fdch blokov\u00fdch zariadeniach \u2013 lun\u00e1ch (na obr\u00e1zku ni\u017e\u0161ie s\u00fa vybran\u00e9 polia A, B, F, G, I). Tu m\u00f4\u017eete vidie\u0165 stav fronty k lun\u00e1m. <\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonnosti VM v VMware vSphere. \u010cas\u0165 3: Ukladanie d\u00e1t\" src=\"\/wp-content\/uploads\/2019\/07\/6331ee64398fe7057c0eec015165f0a5.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>DQLEN<\/b> \u2013 ve\u013ekos\u0165 fronty pre blokov\u00e9 zariadenie.<br \/>\n<b>ACTV<\/b> \u2013 po\u010det pr\u00edkazov vstupu\/v\u00fdstupu v jadre ESXi.<br \/>\n<b>QUED<\/b> \u2013 po\u010det pr\u00edkazov vstupu\/v\u00fdstupu vo fronte.<br \/>\n<b>%USD<\/b> \u2013 ACTV \/ DQLEN \u00d7 100%.<br \/>\n<b>LOAD<\/b> \u2013 (ACTV + QUED) \/ DQLEN.<\/p>\n<p>Ak je %USD vysok\u00e9, stoj\u00ed za zv\u00e1\u017eenie mo\u017enos\u0165 zv\u00fd\u0161enia fronty. \u010c\u00edm viac pr\u00edkazov je vo fronte, t\u00fdm vy\u0161\u0161ie QAVG a, samozrejme, KAVG.<\/p>\n<p>Na obrazovke Disk device si m\u00f4\u017eete pozrie\u0165, \u010di na S\u010cD funguje VAAI (vStorage API for Array Integration). Na to je potrebn\u00e9 zvoli\u0165 polia A a O. <\/p>\n<p>Mechanizmus VAAI umo\u017e\u0148uje presun\u00fa\u0165 \u010das\u0165 pr\u00e1ce z hyperv\u00edzora priamo na S\u010cD, napr\u00edklad nulovanie, kop\u00edrovanie blokov alebo blokovanie.<\/p>\n<p><img decoding=\"async\" alt=\"Anal\u00fdza v\u00fdkonnosti VM v VMware vSphere. \u010cas\u0165 3: Ukladanie d\u00e1t\" src=\"\/wp-content\/uploads\/2019\/07\/131342d74e69af9c0898a1b350e883c8.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nAko je vidie\u0165 na obr\u00e1zku vy\u0161\u0161ie, na tejto S\u010cD VAAI funguje: akt\u00edvne sa vyu\u017e\u00edvaj\u00fa primit\u00edvy Zero a ATS.<\/p>\n<h3>Tipy na optimaliz\u00e1ciu pr\u00e1ce s diskov\u00fdm subsyst\u00e9mom na ESXi<\/h3>\n<p><\/p>\n<ul>\n<li>Venova\u0165 pozornos\u0165 ve\u013ekosti bloku.<\/li>\n<li>Nastavi\u0165 optim\u00e1lnu ve\u013ekos\u0165 frontu na HBA.<\/li>\n<li>Nezabudnite zapn\u00fa\u0165 SIOC na datastoroch.<\/li>\n<li>Vyberte PSP v s\u00falade s odpor\u00fa\u010daniami v\u00fdrobcu S\u010cD.<\/li>\n<li>Uistite sa, \u017ee VAAI funguje.<\/li>\n<\/ul>\n<p>\n<b class=\"spoiler_title\">U\u017eito\u010dn\u00e9 \u010dl\u00e1nky na t\u00e9mu:<\/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>Zdroj: <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.3 - 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\/sk\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\n\t\t<meta property=\"og:locale\" content=\"sk_SK\" \/>\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\/sk\/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\udd47Anal\u00fdza v\u00fdkonu VM vo VMware vSphere. \u010cas\u0165 3: Storage | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","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\/sk\/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\/sk\/wp-json\/wp\/v2\/posts\/36486","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=36486"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/36486\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/27306"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=36486"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=36486"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=36486"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}