{"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\/sl\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","title":{"rendered":"Analiza zmienno\u015bci wydajno\u015bci VM w VMware vSphere. Cz\u0119\u015b\u0107 3: Storage","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Analiza zmienno\u015bci wydajno\u015bci VM w VMware vSphere. Cz\u0119\u015b\u0107 3: Storage\" 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\/\">Cz\u0119\u015b\u0107 1. O CPU<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/455820\/\">Cz\u0119\u015b\u0107 2. O pami\u0119ci<\/a><\/noindex><\/p>\n<p>Dzi\u015b om\u00f3wimy metryki systemu dyskowego w vSphere. Problemy ze storage'em s\u0105 najcz\u0119stsz\u0105 przyczyn\u0105 wolnej pracy wirtualnej maszyny. W przypadku CPU i RAM troubleshooting ko\u0144czy si\u0119 na poziomie hypervisora, podczas gdy w problemach z dyskiem mo\u017ce by\u0107 konieczne zbadanie sieci transmisyjnej i macierzy dyskowej.<\/p>\n<p>Temat b\u0119d\u0119 omawia\u0107 na przyk\u0142adzie dost\u0119pu blokowego do macierzy dyskowej, chocia\u017c przy dost\u0119pie plikowym wska\u017aniki s\u0105 podobne.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Nekaj teorije<\/h3>\n<p>\nKiedy m\u00f3wi si\u0119 o wydajno\u015bci systemu dyskowego wirtualnych maszyn, zazwyczaj zwraca si\u0119 uwag\u0119 na trzy ze sob\u0105 powi\u0105zane parametry:<\/p>\n<ul>\n<li>liczb\u0119 operacji wej\u015bcia\/wyj\u015bcia (Input\/Output Operations Per Second, IOPS);<\/li>\n<li>przepustowo\u015b\u0107 (Throughput);<\/li>\n<li>op\u00f3\u017anienie operacji wej\u015bcia\/wyj\u015bcia (Latency).<\/li>\n<\/ul>\n<p>\n<b>Liczba IOPS<\/b> jest zwykle wa\u017cna dla obci\u0105\u017ce\u0144 o charakterze losowym (random): dost\u0119p do blok\u00f3w na dysku rozmieszczonych w r\u00f3\u017cnych miejscach. Przyk\u0142adem takiego obci\u0105\u017cenia mog\u0105 by\u0107 bazy danych, aplikacje biznesowe (ERP, CRM) itp.<\/p>\n<p><b>Propustnost<\/b> jest wa\u017cna dla obci\u0105\u017ce\u0144 o charakterze sekwencyjnym: dost\u0119p do blok\u00f3w umieszczonych za sob\u0105. Na przyk\u0142ad takie obci\u0105\u017cenie mog\u0105 generowa\u0107 serwery plikowe (cho\u0107 nie zawsze) i systemy monitoringu wideo.<\/p>\n<p>Przepustowo\u015b\u0107 zwi\u0105zana jest z liczb\u0105 operacji wej\u015bcia\/wyj\u015bcia w nast\u0119puj\u0105cy spos\u00f3b:<\/p>\n<p><i>Throughput = IOPS * Rozmiar bloku<\/i>, gdzie Rozmiar bloku to wielko\u015b\u0107 bloku.<\/p>\n<p>Rozmiar bloku jest do\u015b\u0107 wa\u017cn\u0105 cech\u0105. Nowoczesne wersje ESXi obs\u0142uguj\u0105 bloki o rozmiarze do 32 767 KB. Je\u015bli blok jest jeszcze wi\u0119kszy, jest dzielony na mniejsze. Nie wszystkie macierze dyskowe mog\u0105 efektywnie pracowa\u0107 z tak du\u017cymi blokami, dlatego w Ustawieniach zaawansowanych ESXi istnieje parametr DiskMaxIOSize. Dzi\u0119ki niemu mo\u017cna zmniejszy\u0107 maksymalny rozmiar bloku obs\u0142ugiwanego przez hypervisora (wi\u0119cej <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1003469\">ovde<\/a><\/noindex>). Zalecam skonsultowanie si\u0119 z producentem macierzy dyskowej przed zmian\u0105 tego parametru lub przynajmniej przetestowanie zmian na stanowisku laboratoryjnym.\u00a0<\/p>\n<p>Du\u017cy rozmiar bloku mo\u017ce negatywnie wp\u0142ywa\u0107 na wydajno\u015b\u0107 macierzy dyskowej. Nawet je\u015bli liczba IOPS i throughput jest stosunkowo niewielka, przy du\u017cym rozmiarze bloku mog\u0105 wyst\u0105pi\u0107 wysokie op\u00f3\u017anienia. Dlatego zwracaj uwag\u0119 na ten parametr.<\/p>\n<p><b>Op\u00f3\u017anienie<\/b> \u2013 najzanimljivej\u0161i parametar zmogljivosti. Zamuda operacij vhod\/izhod za virtualni stroj je sestavljena iz:<\/p>\n<ul>\n<li>zamude znotraj hipervizorja (KAVG, povpre\u010dna mila sekunda\/kernel\/bralna operacija);<\/li>\n<li>zamude, ki jo povzro\u010data omre\u017eje in shrambe podatkov (DAVG, povpre\u010dna mila sekunda\/ukaz).<\/li>\n<\/ul>\n<p>\nSkupna zamuda, ki jo vidimo v gostujo\u010dem operacijskem sistemu (GAVG, povpre\u010dna mila sekunda\/gostiteljska operacija), je vsota KAVG in DAVG.<\/p>\n<p>GAVG in DAVG se merita, KAVG pa se izra\u010duna: GAVG\u2013DAVG.<\/p>\n<p><img decoding=\"async\" alt=\"Analiza zmienno\u015bci wydajno\u015bci VM w VMware vSphere. Cz\u0119\u015b\u0107 3: Storage\" 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>Source<\/i><\/a><\/noindex><\/p>\n<p>Poglejmo podrobneje o <b>KAVG<\/b>. Ob normalnem delovanju naj KAVG te\u017ei k ni\u010dli ali pa naj bo vsaj mo\u010dno ni\u017eji od DAVG. Edini znan primer, ko je KAVG pri\u010dakovano visok, je omejitev IOPS na disku VM. V tem primeru se bo KAVG pove\u010dal, ko boste posku\u0161ali prese\u010di omejitev.<\/p>\n<p>Najpomembnej\u0161a sestavina KAVG je QAVG \u2013 \u010das v vrsti za obdelavo znotraj hipervizorja. Druge komponente KAVG so zanemarljive.<\/p>\n<p>Vrsta v gonilniku diskovnega adapterja in vrste do lun je fiksne velikosti. Za okolja z visokimi obremenitvami je v\u010dasih koristno pove\u010dati to velikost. <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1267\">Tukaj<\/a><\/noindex> opisano, kako pove\u010dati vrste v gonilniku adapterja (s tem se bo pove\u010dala tudi vrsta do lun). Ta nastavitev deluje, ko z lun opravlja le ena VM, kar je redko. \u010ce je na lunu ve\u010d VM, je treba tudi pove\u010dati parameter <i>Disk.SchedNumReqOutstanding<\/i> (navodilo\u00a0 <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1268\">ovde<\/a><\/noindex>). S pove\u010danjem vrste zmanj\u0161ate QAVG in KAVG ustrezno.<\/p>\n<p>Toda, znova, najprej se seznanite z dokumentacijo dobavitelja HBA in preizkusite spremembe na laboratorijskem testnem okolju. <\/p>\n<p>Na velikost vrste do luna lahko vpliva vklop mehanizma SIOC (Storage I\/O Control). Ta zagotavlja enak dostop do luna s strani vseh stre\u017enikov v gru\u010di z dinami\u010dnim prilagajanjem vrste do luna na stre\u017enikih. To pomeni, da \u010de na katerem koli od gostiteljev deluje VM, ki zahteva nesorazmerno veliko zmogljivosti (noisy neighbor VM), SIOC zmanj\u0161a dol\u017eino vrste do luna na tem gostitelju (DQLEN). Ve\u010d o tem <noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2019\/03\/05\/dqlen-changes-what-is-going-on\/\">ovde<\/a><\/noindex>.<\/p>\n<p>S KAVG smo razjasnili, zdaj pa malo o <b>DAVG<\/b>. Tu je vse preprosto: DAVG je zamuda, ki jo povzro\u010da zunanje okolje (omre\u017eje in shrambe podatkov). V vsaki sodobni in ne tako sodobni shrambi podatkov so na voljo lastni \u0161tevec zmogljivosti. Za analizo te\u017eav z DAVG ima smisel, da jih preverite. \u010ce je vse normalno s strani ESXi in shrambe podatkov, preverite omre\u017eje.<\/p>\n<p>Da bi se izbegli problemi s performansama, odaberite pravilnu politiku izbora puta (PSP) za va\u0161 skladi\u0161ni sistem. Gotovo svi savremeni skladi\u0161ni sistemi podr\u017eavaju Round-Robin PSP (s ALUA, Asymmetric Logical Unit Access, ili bez). Ova politika omogu\u0107ava kori\u0161\u0107enje svih dostupnih puteva do skladi\u0161nog sistema. U slu\u010daju ALUA koriste se samo putevi do kontrolera koji poseduje LUN. Nisu svi skladi\u0161ni sistemi na ESXi postavljeni s podrazumevanim pravilima koja uspostavljaju Round-Robin politiku. Ako za va\u0161 skladi\u0161ni sistem nema pravila, koristite dodatak proizvo\u0111a\u010da skladi\u0161nog sistema koji \u0107e kreirati odgovaraju\u0107e pravilo na svim hostovima klastera, ili kreirajte pravilo sami. Detalji <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2053628\">ovde<\/a><\/noindex>.\u00a0<\/p>\n<p>Tako\u0111e, neki proizvo\u0111a\u010di skladi\u0161nih sistema preporu\u010duju promenu broja IOPS na putu sa standardne vrednosti 1000 na 1. U na\u0161oj praksi to je omogu\u0107ilo \"izvla\u010denje\" vi\u0161e performansi iz skladi\u0161nog sistema i zna\u010dajno skra\u0107enje vremena potrebnog za prebacivanje u slu\u010daju kvara ili a\u017euriranja kontrolera. Proverite preporuke vendor-a, i ako nema kontraindikacija, poku\u0161ajte da promenite ovaj parametar. Detalji <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2069356\">ovde<\/a><\/noindex>.<\/p>\n<h3>Osnovni brojaci performansi diskovnog podsistema virtuelne ma\u0161ine<\/h3>\n<p>\nBroja\u010di performansi diskovnog podsistema u vCenter-u su prikupljeni u sekcijama Datastore, Disk, Virtual Disk:<\/p>\n<p><img decoding=\"async\" alt=\"Analiza zmienno\u015bci wydajno\u015bci VM w VMware vSphere. Cz\u0119\u015b\u0107 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/ae852a6a128914a7aff36f461c5f0721.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n <br \/>\nV razdelku <b>Datastore<\/b> sadr\u017ee metrike o diskovnim skladi\u0161tima vSphere (datastorima), na kojima se nalaze diskovi VM-a. Ovde \u0107ete prona\u0107i standardne brojace za:<\/p>\n<ul>\n<li>IOPS (prose\u010dne operacije \u010ditanja\/pisanja po sekundi),\u00a0<\/li>\n<li>propusnost (brzina \u010ditanja\/pisanja),\u00a0<\/li>\n<li>ka\u0161njenja (\u010ditanje\/pisanje\/najve\u0107e ka\u0161njenje).<\/li>\n<\/ul>\n<p>\nIz naziva brojaca je uglavnom sve jasno. Jo\u0161 jednom \u0107u napomenuti da ovde statistika nije specifi\u010dna za odre\u0111enu VM (ili disk VM-a), ve\u0107 je ukupna za ceo datastore. Po mom mi\u0161ljenju, ovu statistiku je lak\u0161e pregledati u ESXTOP-u, barem iz razloga \u0161to je minimalni period merenja tamo 2 sekunde.<\/p>\n<p>V razdelku <b>Disk<\/b> sadr\u017ee metrike o blokovnim ure\u0111ajima koji se koriste u VM-u. Ovde su brojaci za IOPS u obliku sumacije (broj operacija ulaza\/izlaza tokom mernog perioda) i nekoliko brojaca koji se odnose na blokovski pristup (Commands aborted, Bus resets). Ove informacije, po mom mi\u0161ljenju, tako\u0111e je lak\u0161e pregledati u ESXTOP-u.<\/p>\n<p>Oddelek <b>Virtual Disk<\/b> \u2013 je najkorisnija za pronala\u017eenje problema sa performansama diskovnog sistema VM. Ovdje mo\u017eete vidjeti performanse po svakom virtuelnom disku. Ove informacije su klju\u010dne za razumevanje da li postoji problem sa odre\u0111enom virtuelnom ma\u0161inom. Pored standardnih mera unosa\/izlaza, volumena \u010ditanja\/pisanja i latencije, u ovom odeljku su prisutni korisni merni podaci koji pokazuju veli\u010dinu bloka: Veli\u010dina \u010ditanja\/pisanja zahteva.<\/p>\n<p>Na slici ispod je grafikon performansi diska VM, na kojem mo\u017eete videti broj IOPS, latenciju i veli\u010dinu bloka.\u00a0<\/p>\n<p><img decoding=\"async\" alt=\"Analiza zmienno\u015bci wydajno\u015bci VM w VMware vSphere. Cz\u0119\u015b\u0107 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/36d2a4d006d2c1bfd4d9961c745f26b6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTako\u0111e, metrike performansi se mogu pregledati za ceo datastore, ako je uklju\u010den SIOC. Ovdje su predstavljene osnovne informacije o prose\u010dnoj latenciji i IOPS-u. Podrazumevano se ove informacije mogu videti samo u realnom vremenu.<\/p>\n<p><img decoding=\"async\" alt=\"Analiza zmienno\u015bci wydajno\u015bci VM w VMware vSphere. Cz\u0119\u015b\u0107 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/7872dd131008dfdae09141553b4e42f6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>ESXTOP<\/h3>\n<p>\nU ESXTOP-u postoje vi\u0161e ekrana na kojima su prikazane informacije o diskovnom sistemu hosta u celini, kao i pojedina\u010dnim virtuelnim ma\u0161inama i njihovim diskovima.<\/p>\n<p>Po\u010dnimo od informacija o virtuelnim ma\u0161inama. Ekran \u201cDisk VM\u201d aktivira se tasterom \u201cv\u201d:<\/p>\n<p><img decoding=\"async\" alt=\"Analiza zmienno\u015bci wydajno\u015bci VM w VMware vSphere. Cz\u0119\u015b\u0107 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/793273e19fca1e4f19b96204202019fb.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>NVDISK<\/b> \u2013 to je broj diskova VM. Da biste video informacije za svaki disk, pritisnite \u201ce\u201d i unesite GID \u017eeljene virtuelne ma\u0161ine.<\/p>\n<p>Vrednosti ostalih parametara na ovom ekranu mogu se lako razumeti iz njihovih oznaka.<\/p>\n<p>Jo\u0161 jedan koristan ekran pri tra\u017eenju problema je Disk adapter. Aktivira se tasterom \u201cd\u201d (na slici ispod su izabrana polja A, B, C, D, E, G):<\/p>\n<p><img decoding=\"async\" alt=\"Analiza zmienno\u015bci wydajno\u015bci VM w VMware vSphere. Cz\u0119\u015b\u0107 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/71a7f1e3f1e40f3dbacf61385a3c07cc.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>NPTH<\/b> \u2013 broj puteva do lun-a koji su vidljivi sa ovog adaptera. Da biste dobili informacije o svakom putu na adapteru, pritisnite \u201ce\u201d i unesite naziv adaptera:<\/p>\n<p><img decoding=\"async\" alt=\"Analiza zmienno\u015bci wydajno\u015bci VM w VMware vSphere. Cz\u0119\u015b\u0107 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/12661003ce8be542ed4c5e262da77d90.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>AQLEN<\/b> \u2013 maksimalna veli\u010dina reda na adapteru.<\/p>\n<p>Na ovom ekranu su tako\u0111e prikazani merni podaci o latenciji koje sam ranije pominjao: <b>KAVG\/cmd, GAVG\/cmd, DAVG\/cmd, QAVG\/cmd<\/b>. <\/p>\n<p>Na ekranu Disk device, koji se aktivira tasterom \u201cu\u201d, prikazane su informacije o pojedina\u010dnim blok ure\u0111ajima \u2013 lun-ima (na slici ispod su izabrana polja A, B, F, G, I). Ovde mo\u017eete videti stanje reda ka lun-ima. <\/p>\n<p><img decoding=\"async\" alt=\"Analiza zmienno\u015bci wydajno\u015bci VM w VMware vSphere. Cz\u0119\u015b\u0107 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/6331ee64398fe7057c0eec015165f0a5.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>DQLEN<\/b> \u2013 veli\u010dina reda za blok ure\u0111aj.<br \/>\n<b>ACTV<\/b> \u2013 broj komandi unosa\/izlaza u ESXi jezgru.<br \/>\n<b>QUED<\/b> \u2013 broj komandi unosa\/izlaza u redu.<br \/>\n<b>%USD<\/b> \u2013 ACTV \/ DQLEN \u00d7 100%.<br \/>\n<b>LOAD<\/b> \u2013 (ACTV + QUED) \/ DQLEN.<\/p>\n<p>Ako je %USD visok, treba razmotriti mogu\u0107nost pove\u0107anja reda. \u0160to je ve\u0107i broj komandi u redu, to je ve\u0107i QAVG i, samim tim, KAVG.<\/p>\n<p>Na zaslonu diskovnega naprava lahko prav tako preverite, ali na shranjevanju deluje VAAI (vStorage API for Array Integration). Za to morate izbrati polji A in O. <\/p>\n<p>Mehanizem VAAI omogo\u010da prenos dela dela iz hipervizorja neposredno na shranjevanje, na primer, ni\u010deljenje, kopiranje blokov ali zaklepanja.<\/p>\n<p><img decoding=\"async\" alt=\"Analiza zmienno\u015bci wydajno\u015bci VM w VMware vSphere. Cz\u0119\u015b\u0107 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/131342d74e69af9c0898a1b350e883c8.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKot je razvidno iz slike zgoraj, na tem shranjevanju VAAI deluje: aktivno se uporabljajo primitivi Zero in ATS.<\/p>\n<h3>Nasveti za optimizacijo dela z diskovno podstrukturirano na ESXi<\/h3>\n<p><\/p>\n<ul>\n<li>Upo\u0161tevajte velikost bloka.<\/li>\n<li>Nastavite optimalno velikost vrste na HBA.<\/li>\n<li>Ne pozabite vklju\u010diti SIOC na podatkovnih skladi\u0161\u010dih.<\/li>\n<li>Izberite PSP v skladu s priporo\u010dili proizvajalca shranjevanja.<\/li>\n<li>Preverite, ali VAAI deluje.<\/li>\n<\/ul>\n<p>\n<b class=\"spoiler_title\">Koristni \u010dlanki na to temo:<\/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>Izvor: <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.4 - 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\/sl\/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.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"sl_SI\" \/>\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\/sl\/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\udd47Analiza zmogljivosti VM v VMware vSphere. Del 3: Shranjevanje | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/sl\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sl_SI","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\/sl\/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\/sl\/wp-json\/wp\/v2\/posts\/36486","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/comments?post=36486"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/posts\/36486\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/media\/27306"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/media?parent=36486"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/categories?post=36486"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sl\/wp-json\/wp\/v2\/tags?post=36486"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}