{"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\/hu\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","title":{"rendered":"VM teljes\u00edtm\u00e9ny\u00e9nek elemz\u00e9se VMware vSphere-ben. 3. r\u00e9sz: T\u00e1rol\u00e1s","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"VM teljes\u00edtm\u00e9ny\u00e9nek elemz\u00e9se VMware vSphere-ben. 3. r\u00e9sz: T\u00e1rol\u00e1s\" 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\/\">1. r\u00e9sz. CPU-val kapcsolatosan<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/455820\/\">2. r\u00e9sz. A Mem\u00f3ri\u00e1r\u00f3l<\/a><\/noindex><\/p>\n<p>Ma a vSphere lemezkialak\u00edt\u00e1s\u00e1nak metrik\u00e1it fogjuk megvitatni. A lemezzel kapcsolatos probl\u00e9m\u00e1k a leggyakoribb okai a virtu\u00e1lis g\u00e9p lass\u00fa m\u0171k\u00f6d\u00e9s\u00e9nek. M\u00edg CPU \u00e9s RAM eset\u00e9n a hibakeres\u00e9s a hipervizor szintj\u00e9n \u00e9r v\u00e9get, addig lemezprobl\u00e9m\u00e1k eset\u00e9n lehet, hogy a t\u00e1rol\u00f3h\u00e1l\u00f3zattal \u00e9s a t\u00e1rol\u00f3rendszerrel is foglalkozni kell.<\/p>\n<p>A t\u00e9ma elemz\u00e9se sor\u00e1n a blokk alap\u00fa hozz\u00e1f\u00e9r\u00e9st haszn\u00e1lt t\u00e1rol\u00f3rendszert fogom p\u00e9ldak\u00e9nt felhozni, b\u00e1r f\u00e1jl alap\u00fa hozz\u00e1f\u00e9r\u00e9sn\u00e9l a sz\u00e1ml\u00e1l\u00f3k k\u00f6r\u00fclbel\u00fcl ugyanezek.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Egy kis elm\u00e9let<\/h3>\n<p>\nAmikor a virtu\u00e1lis g\u00e9pek lemezmeghajt\u00f3 teljes\u00edtm\u00e9ny\u00e9r\u0151l besz\u00e9l\u00fcnk, \u00e1ltal\u00e1ban h\u00e1rom, egym\u00e1ssal \u00f6sszef\u00fcgg\u0151 param\u00e9terre h\u00edvjuk fel a figyelmet:<\/p>\n<ul>\n<li>bemeneti\/kimeneti m\u0171veletek sz\u00e1ma (Input\/Output Operations Per Second, IOPS);<\/li>\n<li>\u00e1tviteli sebess\u00e9g (Throughput);<\/li>\n<li>bemeneti\/kimeneti m\u0171veletek k\u00e9sleltet\u00e9se (Latency).<\/li>\n<\/ul>\n<p>\n<b>Az IOPS sz\u00e1ma<\/b> \u00e1ltal\u00e1ban fontos a v\u00e9letlenszer\u0171 jelleg\u0171 terhel\u00e9sek sz\u00e1m\u00e1ra: hozz\u00e1f\u00e9r\u00e9s a lemez k\u00fcl\u00f6nb\u00f6z\u0151 helyein l\u00e9v\u0151 blokkokhoz. Ilyen terhel\u00e9st p\u00e9ld\u00e1ul az adatb\u00e1zisok, \u00fczleti alkalmaz\u00e1sok (ERP, CRM) gener\u00e1lhatnak.<\/p>\n<p><b>S\u00e1vsz\u00e9less\u00e9g<\/b> fontos a sorozatos jelleg\u0171 terhel\u00e9sekhez: hozz\u00e1f\u00e9r\u00e9s a blokkokhoz, amelyek egym\u00e1s ut\u00e1n helyezkednek el. P\u00e9ld\u00e1ul ilyen terhel\u00e9st gener\u00e1lhatnak a f\u00e1jl kiszolg\u00e1l\u00f3k (de nem mindig) \u00e9s a vide\u00f3megfigyel\u0151 rendszerek.<\/p>\n<p>Az \u00e1tvitel sebess\u00e9ge az I\/O m\u0171veletek sz\u00e1m\u00e1val a k\u00f6vetkez\u0151k\u00e9ppen van \u00f6sszef\u00fcgg\u00e9sben:<\/p>\n<p><i>Throughput = IOPS * Blokkm\u00e9ret<\/i>, ahol a Blokkm\u00e9ret a blokk m\u00e9rete.<\/p>\n<p>A blokk m\u00e9rete meglehet\u0151sen fontos jellemz\u0151. A modern ESXi verzi\u00f3k ak\u00e1r 32 767 KB m\u00e9ret\u0171 blokkot is \u00e1tengednek. Ha a blokk m\u00e9g enn\u00e9l is nagyobb, akkor t\u00f6bb r\u00e9szre oszt\u00f3dik. Nem minden t\u00e1rol\u00f3rendszer tud hat\u00e9konyan m\u0171k\u00f6dni ilyen nagy blokkokkal, ez\u00e9rt az ESXi Advanced Settings men\u00fcj\u00e9ben megtal\u00e1lhat\u00f3 a DiskMaxIOSize param\u00e9ter. Ezzel a param\u00e9terrel cs\u00f6kkenthet\u0151 a hipervizor \u00e1ltal \u00e1tengedett blokk maxim\u00e1lis m\u00e9rete (tov\u00e1bbi r\u00e9szletek <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1003469\">itt<\/a><\/noindex>). Miel\u0151tt ezt a param\u00e9tert m\u00f3dos\u00edtan\u00e1, javaslom, hogy konzult\u00e1ljon a t\u00e1rol\u00f3rendszer gy\u00e1rt\u00f3j\u00e1val, vagy legal\u00e1bb tesztelje a m\u00f3dos\u00edt\u00e1sokat egy laborat\u00f3riumi k\u00f6rnyezetben.\u00a0<\/p>\n<p>A nagy blokk m\u00e9ret kedvez\u0151tlen hat\u00e1ssal lehet a t\u00e1rol\u00f3rendszer teljes\u00edtm\u00e9ny\u00e9re. M\u00e9g akkor is, ha az IOPS \u00e9s az \u00e1tvitel viszonylag alacsony, nagy blokk m\u00e9ret eset\u00e9n magas k\u00e9sleltet\u00e9s figyelhet\u0151 meg. Ez\u00e9rt figyeljen erre a param\u00e9terre.<\/p>\n<p><b>K\u00e9sleltet\u00e9s<\/b> \u2013 a teljes\u00edtm\u00e9ny leg\u00e9rdekesebb param\u00e9tere. A virtu\u00e1lis g\u00e9p bemeneti\/kimeneti m\u0171veleteinek k\u00e9sleltet\u00e9se a k\u00f6vetkez\u0151kb\u0151l \u00e1ll:<\/p>\n<ul>\n<li>a hypervisoron bel\u00fcli k\u00e9sleked\u00e9sek (KAVG, \u00c1tlagos Kernel MilliSec\/Read);<\/li>\n<li>a bet\u00e1pl\u00e1lt adat\u00e1tviteli h\u00e1l\u00f3zat \u00e9s a t\u00e1rol\u00f3rendszer \u00e1ltal okozott k\u00e9sleked\u00e9sek (DAVG, \u00c1tlagos Driver MilliSec\/Command).<\/li>\n<\/ul>\n<p>\nA vend\u00e9g oper\u00e1ci\u00f3s rendszerben l\u00e1that\u00f3 \u00e1ltal\u00e1nos k\u00e9sleked\u00e9s (GAVG, \u00c1tlagos Vend\u00e9g MilliSec\/Command) a KAVG \u00e9s DAVG \u00f6sszege.<\/p>\n<p>A GAVG \u00e9s DAVG m\u00e9rhet\u0151k, m\u00edg a KAVG kisz\u00e1m\u00edtand\u00f3: GAVG\u2013DAVG.<\/p>\n<p><img decoding=\"async\" alt=\"VM teljes\u00edtm\u00e9ny\u00e9nek elemz\u00e9se VMware vSphere-ben. 3. r\u00e9sz: T\u00e1rol\u00e1s\" 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>Forr\u00e1s<\/i><\/a><\/noindex><\/p>\n<p>R\u00e9szletesebben foglalkozzunk a <b>KAVG<\/b>. Norm\u00e1l m\u0171k\u00f6d\u00e9s eset\u00e9n a KAVG-nak a null\u00e1hoz kell k\u00f6zelesnie, vagy legal\u00e1bbis jelent\u0151sen kisebbnek kell lennie, mint a DAVG. Az egyetlen eset, amikor KAVG v\u00e1rhat\u00f3an magas, az a VM lemez\u00e9n l\u00e9v\u0151 IOPS korl\u00e1toz\u00e1s. Ekkor a korl\u00e1t t\u00fall\u00e9p\u00e9s\u00e9n\u00e9l a KAVG n\u0151ni fog.<\/p>\n<p>A KAVG legjelent\u0151sebb \u00f6sszetev\u0151je a QAVG - az el\u0151feldolgoz\u00e1sra v\u00e1rakoz\u00e1si id\u0151 a hypervisoron bel\u00fcl. A KAVG t\u00f6bbi \u00f6sszetev\u0151je elhanyagolhat\u00f3.<\/p>\n<p>A lemezes adapter meghajt\u00f3ban \u00e9s az lunokhoz val\u00f3 v\u00e1r\u00f3list\u00e1k fix m\u00e9ret\u0171ek. Nagy terhel\u00e9s\u0171 k\u00f6rnyezetekben \u00e9rdemes lehet megn\u00f6velni ezt a m\u00e9retet. <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1267\">Itt<\/a><\/noindex> le\u00edrja, hogyan lehet n\u00f6velni a v\u00e1r\u00f3list\u00e1kat az adapter meghajt\u00f3ban (ezzel egy\u00fctt a lunokra val\u00f3 v\u00e1r\u00f3list\u00e1t is). Ez a be\u00e1ll\u00edt\u00e1s m\u0171k\u00f6dik, amikor a lunon csak egy VM van, ami ritka eset. Ha a lunon t\u00f6bb VM m\u0171k\u00f6dik, akkor azt is meg kell n\u00f6velni, <i>Disk.SchedNumReqOutstanding<\/i> (utas\u00edt\u00e1s\u00a0 <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1268\">itt<\/a><\/noindex>). A v\u00e1r\u00f3lista megn\u00f6vel\u00e9s\u00e9vel cs\u00f6kkenti a QAVG-t \u00e9s a KAVG-t is.<\/p>\n<p>De el\u0151sz\u00f6r is n\u00e9zze meg a gy\u00e1rt\u00f3 HBA dokument\u00e1ci\u00f3j\u00e1t, \u00e9s tesztelje a v\u00e1ltoztat\u00e1sokat egy laborat\u00f3riumi k\u00f6rnyezetben. <\/p>\n<p>A lunhoz val\u00f3 v\u00e1r\u00f3lista m\u00e9ret\u00e9t befoly\u00e1solhatja az SIOC (Storage I\/O Control) mechanizmus aktiv\u00e1l\u00e1sa. Ez biztos\u00edtja a lunhoz val\u00f3 egyenletes hozz\u00e1f\u00e9r\u00e9st a klaszter \u00f6sszes szervere sz\u00e1m\u00e1ra az\u00e1ltal, hogy dinamikusan megv\u00e1ltoztatja a lunhoz val\u00f3 v\u00e1r\u00f3list\u00e1t a szervereken. Teh\u00e1t ha az egyik gazdag\u00e9pen m\u0171k\u00f6dik egy VM, amely ar\u00e1nytalanul sok teljes\u00edtm\u00e9nyt ig\u00e9nyel (noisy neighbor VM), a SIOC cs\u00f6kkenti a lunra vonatkoz\u00f3 v\u00e1r\u00f3lista hossz\u00e1t az adott gazdag\u00e9pen (DQLEN). B\u0151vebben <noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2019\/03\/05\/dqlen-changes-what-is-going-on\/\">itt<\/a><\/noindex>.<\/p>\n<p>A KAVG-n\u00e1l v\u00e9gz\u00fcnk, most pedig egy kicsit a <b>DAVG<\/b>. Itt minden egyszer\u0171: a DAVG az a k\u00e9sleked\u00e9s, amelyet a k\u00fcls\u0151 k\u00f6rnyezet (adat\u00e1tviteli h\u00e1l\u00f3zat \u00e9s a t\u00e1rol\u00f3rendszer) okoz. Minden modern \u00e9s kev\u00e9sb\u00e9 modern t\u00e1rol\u00f3rendszer rendelkezik saj\u00e1t teljes\u00edtm\u00e9nym\u00e9r\u0151ivel. A DAVG probl\u00e9m\u00e1k elemz\u00e9sekor \u00e9rdemes ezeket figyelni. Ha az ESXi \u00e9s a t\u00e1rol\u00f3rendszer oldal\u00e1r\u00f3l minden rendben van, ellen\u0151rizze az adat\u00e1tviteli h\u00e1l\u00f3zatot.<\/p>\n<p>A teljes\u00edtm\u00e9nnyel kapcsolatos probl\u00e9m\u00e1k elker\u00fcl\u00e9se \u00e9rdek\u00e9ben v\u00e1lassza ki a megfelel\u0151 Path Selection Policy (PSP) be\u00e1ll\u00edt\u00e1st a t\u00e1rol\u00f3rendszer\u00e9hez. A szinte minden modern t\u00e1rol\u00f3rendszer t\u00e1mogatja a Round-Robin PSP-t (ALUA, Asymmetric Logical Unit Access, haszn\u00e1lat\u00e1val vagy an\u00e9lk\u00fcl). Ez a politika lehet\u0151v\u00e9 teszi, hogy az \u00f6sszes el\u00e9rhet\u0151 \u00fatvonalat haszn\u00e1lja a t\u00e1rol\u00f3rendszerhez. ALUA eset\u00e9n csak azok az \u00fatvonalak haszn\u00e1lhat\u00f3k, amelyek a lun-t kezel\u0151 vez\u00e9rl\u0151h\u00f6z vezetnek. Nem minden t\u00e1rol\u00f3rendszerhez vannak alap\u00e9rtelmezett szab\u00e1lyok az ESXi-n, amelyek a Round-Robin politik\u00e1t \u00e1ll\u00edtj\u00e1k be. Ha az \u00d6n t\u00e1rol\u00f3rendszer\u00e9hez nincs ilyen szab\u00e1ly, haszn\u00e1ljon a t\u00e1rol\u00f3rendszer gy\u00e1rt\u00f3j\u00e1t\u00f3l sz\u00e1rmaz\u00f3 plugint, amely l\u00e9trehozza a megfelel\u0151 szab\u00e1lyt az \u00f6sszes cluster gazdag\u00e9p\u00e9n, vagy hozza l\u00e9tre saj\u00e1t maga a szab\u00e1lyt. R\u00e9szletek <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2053628\">itt<\/a><\/noindex>.\u00a0<\/p>\n<p>A t\u00e1rol\u00f3rendszerek egyes gy\u00e1rt\u00f3i azt is javasolj\u00e1k, hogy a IOPS sz\u00e1m\u00e1t \u00e1ll\u00edtsa \u00e1t az alap\u00e9rtelmezett 1000-r\u0151l 1-re. Gyakorlatunkban ez lehet\u0151v\u00e9 tette, hogy \u201et\u00f6bbet hozzunk ki\u201d a t\u00e1rol\u00f3rendszerb\u0151l \u00e9s jelent\u0151sen cs\u00f6kkents\u00fck a failover-hez sz\u00fcks\u00e9ges id\u0151t, ha a vez\u00e9rl\u0151k meghib\u00e1sodnak vagy friss\u00edt\u00e9sre ker\u00fclnek. Ellen\u0151rizze a gy\u00e1rt\u00f3 aj\u00e1nl\u00e1sait, \u00e9s ha nincs ellenjavallat, pr\u00f3b\u00e1lja meg m\u00f3dos\u00edtani ezt a param\u00e9tert. R\u00e9szletek <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2069356\">itt<\/a><\/noindex>.<\/p>\n<h3>A virtu\u00e1lis g\u00e9p t\u00e1rol\u00f3rendszer\u00e9nek teljes\u00edtm\u00e9nym\u00e9r\u0151i<\/h3>\n<p>\nA vCenter-ben gy\u0171jt\u00f6tt t\u00e1rol\u00f3rendszer teljes\u00edtm\u00e9nym\u00e9r\u0151i a Datastore, Disk, Virtual Disk szakaszokban tal\u00e1lhat\u00f3k:<\/p>\n<p><img decoding=\"async\" alt=\"VM teljes\u00edtm\u00e9ny\u00e9nek elemz\u00e9se VMware vSphere-ben. 3. r\u00e9sz: T\u00e1rol\u00e1s\" src=\"\/wp-content\/uploads\/2019\/07\/ae852a6a128914a7aff36f461c5f0721.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n <br \/>\nA r\u00e9szben <b>Datastore<\/b> itt tal\u00e1lhat\u00f3k a vSphere t\u00e1rol\u00f3 (datastore) statisztik\u00e1i, ahol a virtu\u00e1lis g\u00e9pek diszkjei tal\u00e1lhat\u00f3k. Itt megtal\u00e1lja a k\u00f6vetkez\u0151 standard teljes\u00edtm\u00e9nym\u00e9r\u0151ket:<\/p>\n<ul>\n<li>IOPS (\u00e1tlagos olvas\u00e1si \/ \u00edr\u00e1si k\u00e9r\u00e9sek m\u00e1sodpercenk\u00e9nt),\u00a0<\/li>\n<li>\u00e1tereszt\u0151 k\u00e9pess\u00e9g (olvas\u00e1si \/ \u00edr\u00e1si sebess\u00e9g),\u00a0<\/li>\n<li>k\u00e9sleltet\u00e9s (olvas\u00e1si \/ \u00edr\u00e1si \/ legmagasabb k\u00e9sleltet\u00e9s).<\/li>\n<\/ul>\n<p>\nA m\u00e9r\u0151k nev\u00e9b\u0151l mindent meg\u00e9rthet\u00fcnk. Ism\u00e9t hangs\u00falyozom, hogy itt a statisztika nem egy adott virtu\u00e1lis g\u00e9pre (vagy virtu\u00e1lis g\u00e9p lemez\u00e9re) vonatkozik, hanem az eg\u00e9sz datastore-ra. V\u00e9lem\u00e9nyem szerint a statisztik\u00e1t k\u00e9nyelmesebb az ESXTOP-ban n\u00e9zni, legal\u00e1bbis abb\u00f3l a szempontb\u00f3l, hogy a legkisebb m\u00e9r\u00e9si id\u0151tartam ott 2 m\u00e1sodperc.<\/p>\n<p>A r\u00e9szben <b>Lemez<\/b> itt tal\u00e1lhat\u00f3k a blokkeszk\u00f6z\u00f6kre vonatkoz\u00f3 statisztik\u00e1k, amelyek a virtu\u00e1lis g\u00e9pek \u00e1ltal haszn\u00e1lt. Itt van IOPS t\u00edpus\u00fa summation (a m\u00e9r\u00e9si id\u0151szak alatt v\u00e9grehajtott bemeneti\/kimeneti m\u0171veletek sz\u00e1ma) \u00e9s sz\u00e1mos blokk-hozz\u00e1f\u00e9r\u00e9shez kapcsol\u00f3d\u00f3 m\u00e9r\u0151 (Commands aborted, Bus resets). V\u00e9lem\u00e9nyem szerint ezt az inform\u00e1ci\u00f3t szint\u00e9n k\u00e9nyelmesebb az ESXTOP-ban megtekinteni.<\/p>\n<p>R\u00e9sz <b>Virtual Disk<\/b> \u2013 a leghasznosabb az adatb\u00e1zis teljes\u00edtm\u00e9nyprobl\u00e9m\u00e1inak keres\u00e9se szempontj\u00e1b\u00f3l a VM. Itt megtekinthetj\u00fck a teljes\u00edtm\u00e9nyt minden virtu\u00e1lis lemezen. Ez az inform\u00e1ci\u00f3 sz\u00fcks\u00e9ges ahhoz, hogy meg\u00e9rts\u00fck, van-e probl\u00e9ma egy adott virtu\u00e1lis g\u00e9pn\u00e9l. A standard bels\u0151\/k\u00fcls\u0151 m\u0171veletek sz\u00e1ml\u00e1l\u00f3i, a beolvasott\/\u00edrt terjedelem \u00e9s k\u00e9sleltet\u00e9sek mellett ebben a r\u00e9szben hasznos sz\u00e1ml\u00e1l\u00f3k tal\u00e1lhat\u00f3k, amelyek a blokk m\u00e9ret\u00e9t mutatj\u00e1k: Read\/Write request size.<\/p>\n<p>Az al\u00e1bbi k\u00e9pen l\u00e1that\u00f3 a VM lemez teljes\u00edtm\u00e9nygrafikonja, amelyen l\u00e1thatjuk az IOPS sz\u00e1m\u00e1t, k\u00e9sleltet\u00e9seket \u00e9s a blokk m\u00e9ret\u00e9t.\u00a0<\/p>\n<p><img decoding=\"async\" alt=\"VM teljes\u00edtm\u00e9ny\u00e9nek elemz\u00e9se VMware vSphere-ben. 3. r\u00e9sz: T\u00e1rol\u00e1s\" src=\"\/wp-content\/uploads\/2019\/07\/36d2a4d006d2c1bfd4d9961c745f26b6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nA teljes\u00edtm\u00e9nymutat\u00f3k a teljes t\u00e1rol\u00f3n is megtekinthet\u0151k, ha az SIOC be van kapcsolva. Itt tal\u00e1lhat\u00f3 az \u00e1tlagos Latency \u00e9s IOPS alapinform\u00e1ci\u00f3i. Alap\u00e9rtelmez\u00e9s szerint ezt csak val\u00f3s id\u0151ben lehet megtekinteni.<\/p>\n<p><img decoding=\"async\" alt=\"VM teljes\u00edtm\u00e9ny\u00e9nek elemz\u00e9se VMware vSphere-ben. 3. r\u00e9sz: T\u00e1rol\u00e1s\" src=\"\/wp-content\/uploads\/2019\/07\/7872dd131008dfdae09141553b4e42f6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>ESXTOP<\/h3>\n<p>\nAz ESXTOP-nak t\u00f6bb k\u00e9perny\u0151je van, amelyen a gazda diszk alrendszer\u00e9re vonatkoz\u00f3 inform\u00e1ci\u00f3k, k\u00fcl\u00f6nb\u00f6z\u0151 virtu\u00e1lis g\u00e9pek \u00e9s azok lemezei tal\u00e1lhat\u00f3k.<\/p>\n<p>Kezdj\u00fck a virtu\u00e1lis g\u00e9pek inform\u00e1ci\u00f3ival. A \"Disk VM\" k\u00e9perny\u0151 az \"v\" billenty\u0171 megnyom\u00e1s\u00e1val h\u00edvhat\u00f3 el\u0151:<\/p>\n<p><img decoding=\"async\" alt=\"VM teljes\u00edtm\u00e9ny\u00e9nek elemz\u00e9se VMware vSphere-ben. 3. r\u00e9sz: T\u00e1rol\u00e1s\" src=\"\/wp-content\/uploads\/2019\/07\/793273e19fca1e4f19b96204202019fb.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>NVDISK<\/b> \u2013 a VM-ek lemezeinek sz\u00e1ma. A r\u00e9szletes inform\u00e1ci\u00f3k megtekint\u00e9s\u00e9hez a k\u00f6vetkez\u0151 lemezre kattintva nyomja meg az \"e\" billenty\u0171t \u00e9s \u00edrja be a k\u00edv\u00e1nt VM GID-j\u00e9t.<\/p>\n<p>A t\u00f6bbi param\u00e9ter \u00e9rt\u00e9ke ezen a k\u00e9perny\u0151n a nev\u00fckb\u0151l vil\u00e1gosan \u00e9rthet\u0151.<\/p>\n<p>Egy m\u00e1sik hasznos k\u00e9perny\u0151 a probl\u00e9m\u00e1k keres\u00e9s\u00e9hez \u2013 Disk adapter. Az \"d\" billenty\u0171 megnyom\u00e1s\u00e1val h\u00edvhat\u00f3 el\u0151 (az al\u00e1bbi k\u00e9pen az A, B, C, D, E, G mez\u0151k vannak kiv\u00e1lasztva):<\/p>\n<p><img decoding=\"async\" alt=\"VM teljes\u00edtm\u00e9ny\u00e9nek elemz\u00e9se VMware vSphere-ben. 3. r\u00e9sz: T\u00e1rol\u00e1s\" src=\"\/wp-content\/uploads\/2019\/07\/71a7f1e3f1e40f3dbacf61385a3c07cc.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>NPTH<\/b> \u2013 az adott adapterr\u0151l l\u00e1that\u00f3 utak sz\u00e1ma a lunokhoz. Az adapteren lev\u0151 minden \u00fat inform\u00e1ci\u00f3j\u00e1nak megtekint\u00e9s\u00e9hez nyomja meg az \"e\" billenty\u0171t \u00e9s \u00edrja be az adapter nev\u00e9t:<\/p>\n<p><img decoding=\"async\" alt=\"VM teljes\u00edtm\u00e9ny\u00e9nek elemz\u00e9se VMware vSphere-ben. 3. r\u00e9sz: T\u00e1rol\u00e1s\" src=\"\/wp-content\/uploads\/2019\/07\/12661003ce8be542ed4c5e262da77d90.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>AQLEN<\/b> \u2013 az adapter maxim\u00e1lis sorozatm\u00e9rete.<\/p>\n<p>Ezen a k\u00e9perny\u0151n a m\u00e1r eml\u00edtett k\u00e9sleltet\u00e9seket mutat\u00f3 sz\u00e1ml\u00e1l\u00f3k is l\u00e1that\u00f3k: <b>KAVG\/cmd, GAVG\/cmd, DAVG\/cmd, QAVG\/cmd<\/b>. <\/p>\n<p>A Disk device k\u00e9perny\u0151n, amely az \"u\" billenty\u0171 megnyom\u00e1s\u00e1val h\u00edvhat\u00f3 el\u0151, az egyes blokkeszk\u00f6z\u00f6kr\u0151l \u2013 lunokr\u00f3l (az al\u00e1bbi k\u00e9pen az A, B, F, G, I mez\u0151k vannak kiv\u00e1lasztva) tal\u00e1lhat\u00f3 inform\u00e1ci\u00f3. Itt l\u00e1that\u00f3 a lunokhoz tartoz\u00f3 sor \u00e1llapota. <\/p>\n<p><img decoding=\"async\" alt=\"VM teljes\u00edtm\u00e9ny\u00e9nek elemz\u00e9se VMware vSphere-ben. 3. r\u00e9sz: T\u00e1rol\u00e1s\" src=\"\/wp-content\/uploads\/2019\/07\/6331ee64398fe7057c0eec015165f0a5.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>DQLEN<\/b> \u2013 a blokkeszk\u00f6z sorsz\u00e1ma.<br \/>\n<b>ACTV<\/b> \u2013 a be\u00e9p\u00edtett ESXi kernelben lev\u0151 bels\u0151\/k\u00fcls\u0151 m\u0171veletek sz\u00e1ma.<br \/>\n<b>QUED<\/b> \u2013 a sorban lev\u0151 bels\u0151\/k\u00fcls\u0151 m\u0171veletek sz\u00e1ma.<br \/>\n<b>%USD<\/b> \u2013 ACTV \/ DQLEN \u00d7 100%.<br \/>\n<b>LOAD<\/b> \u2013 (ACTV + QUED) \/ DQLEN.<\/p>\n<p>Ha a %USD magas, \u00e9rdemes megfontolni a sorozat n\u00f6vel\u00e9s\u00e9t. Min\u00e9l t\u00f6bb m\u0171velet van a sorban, ann\u00e1l magasabb a QAVG \u00e9s ennek megfelel\u0151en a KAVG.<\/p>\n<p>A Disk device k\u00e9perny\u0151n megn\u00e9zheti, hogy a t\u00e1rol\u00f3rendszeren m\u0171k\u00f6dik-e a VAAI (vStorage API for Array Integration). Ehhez ki kell v\u00e1lasztania az A \u00e9s O mez\u0151ket. <\/p>\n<p>A VAAI mechanizmusa lehet\u0151v\u00e9 teszi, hogy a hypervisor munk\u00e1j\u00e1nak egy r\u00e9sz\u00e9t k\u00f6zvetlen\u00fcl a t\u00e1rol\u00f3rendszerre helyezz\u00fck, p\u00e9ld\u00e1ul a null\u00e1z\u00e1st, blokkok m\u00e1sol\u00e1s\u00e1t vagy blokkol\u00e1st.<\/p>\n<p><img decoding=\"async\" alt=\"VM teljes\u00edtm\u00e9ny\u00e9nek elemz\u00e9se VMware vSphere-ben. 3. r\u00e9sz: T\u00e1rol\u00e1s\" src=\"\/wp-content\/uploads\/2019\/07\/131342d74e69af9c0898a1b350e883c8.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nAhogy a fenti k\u00e9pen l\u00e1that\u00f3, ezen a t\u00e1rol\u00f3rendszeren m\u0171k\u00f6dik a VAAI: akt\u00edvan haszn\u00e1lj\u00e1k a Zero \u00e9s az ATS primit\u00edveket.<\/p>\n<h3>Tippek a lemezrendszer optimaliz\u00e1l\u00e1s\u00e1hoz az ESXi-n<\/h3>\n<p><\/p>\n<ul>\n<li>Figyeljen a blokk m\u00e9ret\u00e9re.<\/li>\n<li>\u00c1ll\u00edtsa be az optim\u00e1lis sorozatm\u00e9retet az HBA-n.<\/li>\n<li>Ne felejtse el enged\u00e9lyezni a SIOC-ot a datastore-okn\u00e1l.<\/li>\n<li>V\u00e1lassza ki a PSP-t a t\u00e1rol\u00f3rendszer gy\u00e1rt\u00f3j\u00e1nak aj\u00e1nl\u00e1sa alapj\u00e1n.<\/li>\n<li>Gy\u0151z\u0151dj\u00f6n meg r\u00f3la, hogy a VAAI m\u0171k\u00f6dik.<\/li>\n<\/ul>\n<p>\n<b class=\"spoiler_title\">Hasznos cikkek a t\u00e9m\u00e1ban:<\/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>Forr\u00e1s: <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\/hu\/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=\"hu_HU\" \/>\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\/hu\/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 teljes\u00edtm\u00e9ny\u00e9nek elemz\u00e9se a VMware vSphere-en. 3. r\u00e9sz: T\u00e1rol\u00e1s | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"hu_HU","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\/hu\/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\/hu\/wp-json\/wp\/v2\/posts\/36486","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/comments?post=36486"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/posts\/36486\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/media\/27306"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/media?parent=36486"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/categories?post=36486"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/tags?post=36486"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}