{"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\/hr\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","title":{"rendered":"Analiza performansi VM-a u VMware vSphere. Dio 3: Storage","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Analiza performansi VM-a u VMware vSphere. Dio 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\/\">Dio 1. O CPU-u<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/455820\/\">Dio 2. O Memoriji<\/a><\/noindex><\/p>\n<p>Danas \u0107emo razmotriti metrike diskovnog sustava u vSphere-u. Problemi sa pohranom su naj\u010de\u0161\u0107i uzrok sporog rada virtualne ma\u0161ine. Dok se u slu\u010dajevima s CPU-om i RAM-om rje\u0161avanje problema zavr\u0161ava na razini hipervizora, kod problema s diskom, mo\u017eda \u0107e biti potrebno istra\u017eiti mre\u017eu prijenosa podataka i SAN.<\/p>\n<p>Tema \u0107e biti razmatrana na primjeru blokovskog pristupa SAN-u, iako su brojila otprilike ista i kod datote\u010dnog pristupa.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Malo teorije<\/h3>\n<p>\nKada se govori o performansama diskovnog sustava virtualnih ma\u0161ina, obi\u010dno se obra\u0107a pa\u017enja na tri me\u0111usobno povezana parametra:<\/p>\n<ul>\n<li>broj operacija ulaza\/izlaza (Input\/Output Operations Per Second, IOPS);<\/li>\n<li>propusnost (Throughput);<\/li>\n<li>ka\u0161njenje operacija ulaza\/izlaza (Latency).<\/li>\n<\/ul>\n<p>\n<b>Broj IOPS-a<\/b> obi\u010dno je va\u017ean za naslove proizvoljnog karaktera (random): pristup blokovima na disku koji su smje\u0161teni na razli\u010ditim mjestima. Primjer takvog optere\u0107enja mogu biti baze podataka, poslovne aplikacije (ERP, CRM) itd.<\/p>\n<p><b>Propusnost<\/b> va\u017ean je za naslove sekvencijalnog karaktera: pristup blokovima koji su smje\u0161teni jedan iza drugog. Na primjer, takvo optere\u0107enje mogu generirati datote\u010dni poslu\u017eitelji (ali ne uvijek) i sustavi videonadzora.<\/p>\n<p>Propusnost je povezana s brojem operacija ulaza\/izlaza na sljede\u0107i na\u010din:<\/p>\n<p><i>Throughput = IOPS * Veli\u010dina bloka<\/i>, gdje je Veli\u010dina bloka zapravo veli\u010dina bloka.<\/p>\n<p>Veli\u010dina bloka je prili\u010dno va\u017ena karakteristika. Moderne verzije ESXi-a propu\u0161taju blokove veli\u010dine do 32 767 KB. Ako je blok jo\u0161 ve\u0107i, dijeli se na vi\u0161e. Ne svi SAN-ovi mogu u\u010dinkovito raditi s tako velikim blokovima, pa u Advanced Settings ESXi postoji parametar DiskMaxIOSize. Uz njegovu pomo\u0107 mo\u017eete smanjiti maksimalnu veli\u010dinu bloka koja se propu\u0161ta kroz hipervizor (vi\u0161e o tome <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1003469\">ovdje<\/a><\/noindex>). Preporu\u010dujem da se prije promjene ovog parametra konzultirate s proizvo\u0111a\u010dem SAN-a ili barem testirate promjene na laboratorijskom postavu.\u00a0<\/p>\n<p>Velika veli\u010dina bloka mo\u017ee nepovoljno utjecati na performanse SAN-a. \u010cak i ako je broj IOPS-a i throughput relativno mali, pri velikoj veli\u010dini bloka mogu se primijetiti visoka ka\u0161njenja. Zato obratite pa\u017enju na ovaj parametar.<\/p>\n<p><b>Ka\u0161njenje<\/b> \u2013 najzanimljiviji parametar performansi. Ka\u0161njenje operacija ulaza\/izlaza za virtualnu ma\u0161inu sastoji se od:<\/p>\n<ul>\n<li>ka\u0161njenja unutar hipervizora (KAVG, Prosje\u010dno vrijeme izvr\u0161avanja jezgre - Milisekunde\/\u010citanje);<\/li>\n<li>ka\u0161njenja koja uzrokuju mre\u017ea za prijenos podataka i SAN (DAVG, Prosje\u010dno vrijeme voza\u010da - Milisekunde\/Komanda).<\/li>\n<\/ul>\n<p>\nUkupno ka\u0161njenje koje se vidi u gostuju\u0107em OS-u (GAVG, Prosje\u010dno gostuju\u0107e vrijeme - Milisekunde\/Komanda) je zbroj KAVG i DAVG.<\/p>\n<p>GAVG i DAVG se mjere, a KAVG se izra\u010dunava: GAVG\u2013DAVG.<\/p>\n<p><img decoding=\"async\" alt=\"Analiza performansi VM-a u VMware vSphere. Dio 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>Izvor<\/i><\/a><\/noindex><\/p>\n<p>Detaljnije o <b>KAVG<\/b>. U normalnim uvjetima KAVG bi trebao biti blizu nule ili, barem, znatno manji od DAVG. Jedini poznati slu\u010daj kada je KAVG o\u010dekivano visok je ograni\u010denje IOPS na disku VM-a. U tom slu\u010daju, kada se poku\u0161a prema\u0161iti limit, KAVG \u0107e rasti.<\/p>\n<p>Najzna\u010dajnija komponenta KAVG-a je QAVG \u2013 vrijeme provedeno u redu za obradu unutar hipervizora. Ostale komponente KAVG-a su zanemarive.<\/p>\n<p>Red u upravlja\u010dkom voza\u010du diska i redovi prema lunama imaju fiksnu veli\u010dinu. Za visoko optere\u0107ena okru\u017eenja, korisno je pove\u0107ati ovu veli\u010dinu. <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1267\">Ovdje<\/a><\/noindex> opisano je kako pove\u0107ati redove u voza\u010du adaptera (istovremeno \u0107e se pove\u0107ati i red prema lunama). Ova postavka radi kada jedna VM radi s lunama, \u0161to je rijetko. Ako na luni radi vi\u0161e VM-ova, potrebno je tako\u0111er pove\u0107ati parametar <i>Disk.SchedNumReqOutstanding<\/i> (uputstvo\u00a0 <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1268\">ovdje<\/a><\/noindex>). Pove\u0107anjem reda smanjujete QAVG i KAVG prema tome.<\/p>\n<p>No, opet, prvo se upoznajte s dokumentacijom dobavlja\u010da HBA i testirajte promjene na laboratorijskoj postavci. <\/p>\n<p>Na veli\u010dinu reda prema luni mo\u017ee utjecati uklju\u010divanje mehanizma SIOC (Storage I\/O Control). On osigurava ravnomjeran pristup lunama sa strane svih servera u klasteru dinami\u010dkim promjenama reda prema lunama na serverima. Drugim rije\u010dima, ako na nekom od hostova radi VM koja zahtijeva nesrazmjerno mnogo performansi (noisy neighbor VM), SIOC smanjuje duljinu reda prema lunama na tom hostu (DQLEN). Vi\u0161e informacija <noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2019\/03\/05\/dqlen-changes-what-is-going-on\/\">ovdje<\/a><\/noindex>.<\/p>\n<p>O KAVG-u smo razjasnili, sada malo o <b>DAVG<\/b>. Ovdje je sve jednostavno: DAVG je ka\u0161njenje koje unosi vanjsko okru\u017eenje (mre\u017ea za prijenos podataka i SAN). U bilo kojoj suvremenoj i nezamjenjivoj SAN-u postoje vlastiti pokazatelji performansi. Za analizu problema s DAVG-om ima smisla pogledati ih. Ako je s ESXi i SAN-om sve u redu, provjerite mre\u017eu za prijenos podataka.<\/p>\n<p>Kako biste izbjegli probleme s performansama, odaberite pravu Politiku odabira puta (PSP) za va\u0161 SAN. Gotovo svi moderni SAN-ovi podr\u017eavaju PSP Round-Robin (s ALUA, Asimetri\u010dni pristup logi\u010dkim jedinicama, ili bez). Ova politika omogu\u0107ava kori\u0161tenje svih dostupnih puteva do SAN-a. U slu\u010daju ALUA koriste se samo putevi do kontrolera koji posjeduje LUN. Nisu svi SAN-ovi na ESXi-u unaprijed definirani s pravilima koja postavljaju politiku Round-Robin. Ako za va\u0161 SAN nema pravila, koristite dodatak od proizvo\u0111a\u010da SAN-a, koji \u0107e stvoriti odgovaraju\u0107e pravilo na svim hostovima klastera, ili izradite pravilo sami. Detalji <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2053628\">ovdje<\/a><\/noindex>.\u00a0<\/p>\n<p>Tako\u0111er, neki proizvo\u0111a\u010di SAN-a preporu\u010duju da se broj IOPS-a na putu promijeni s standardne vrijednosti 1000 na 1. U na\u0161oj praksi to je omogu\u0107avalo 'izvla\u010denje' ve\u0107e performanse iz SAN-a i znatno smanjenje vremena potrebnog za prebacivanje u slu\u010daju kvara ili nadogradnje kontrolera. Provjerite preporuke dobavlja\u010da, i ako nema kontraindikacija, poku\u0161ajte promijeniti ovu postavku. Detalji <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2069356\">ovdje<\/a><\/noindex>.<\/p>\n<h3>Glavni pokazatelji performansi diskovnog podsustava virtualne ma\u0161ine<\/h3>\n<p>\nPokazatelji performansi diskovnog podsustava u vCenteru prikupljeni su u odjeljcima Datastore, Disk, Virtual Disk:<\/p>\n<p><img decoding=\"async\" alt=\"Analiza performansi VM-a u VMware vSphere. Dio 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/ae852a6a128914a7aff36f461c5f0721.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n <br \/>\nU odjeljku <b>Datastore<\/b> nalaze se metrike za diskovne pohrane vSphere (datastore) na kojima su pohranjeni diskovi VM-a. Ovdje \u0107ete prona\u0107i standardne pokazatelje za:<\/p>\n<ul>\n<li>IOPS (prosje\u010dni zahtjevi za \u010ditanjem\/pisanjem po sekundi),\u00a0<\/li>\n<li>propusnost (stopa \u010ditanja\/pisanja),\u00a0<\/li>\n<li>ka\u0161njenja (najve\u0107e ka\u0161njenje \u010ditanja\/pisanja).<\/li>\n<\/ul>\n<p>\nIz naziva pokazatelja sve je prili\u010dno jasno. Ponovno nagla\u0161avam da ovdje statistika nije specifi\u010dna za odre\u0111enu VM (ili disk VM-a), ve\u0107 je op\u0107a prema cijelom datastoreu. Po mom mi\u0161ljenju, ovu statistiku je lak\u0161e pregledati u ESXTOP-u, barem izvode\u0107i iz toga da je minimalni period mjerenja tamo 2 sekunde.<\/p>\n<p>U odjeljku <b>Disk<\/b> nalaze se metrike za blok ure\u0111aje koji se koriste u VM-ima. Tu su pokazatelji za IOPS tipa summation (broj ulazno\/izlaznih operacija tijekom mjernog razdoblja) i nekoliko pokazatelja koji se odnose na blokovni pristup (Commands aborted, Bus resets). Ove informacije, po mom mi\u0161ljenju, tako\u0111er je lak\u0161e pregledati u ESXTOP-u.<\/p>\n<p>Odjeljak <b>Virtual Disk<\/b> \u2013 najkorisnija informacija za prepoznavanje problema s performansama diskovnog sustava VM-a. Ovdje se mo\u017ee vidjeti performanse svakog virtuelnog diska. Ove informacije su potrebne za razumijevanje postoji li problem na odre\u0111enoj virtuelnoj ma\u0161ini. Osim standardnih mjera broja operacija ulaza\/izlaza, obima \u010ditanja\/pisanja i latencije, u ovom odjeljku su prisutni korisni mjerni podaci koji pokazuju veli\u010dinu bloka: Veli\u010dina Read\/Write zahtjeva.<\/p>\n<p>Na slici ispod je prikaz performansi diska VM-a, gdje se mo\u017ee vidjeti broj IOPS, latencija i veli\u010dina bloka.\u00a0<\/p>\n<p><img decoding=\"async\" alt=\"Analiza performansi VM-a u VMware vSphere. Dio 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/36d2a4d006d2c1bfd4d9961c745f26b6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTako\u0111er, metrike performansi mogu se pogledati za cijeli datastore ako je SIOC uklju\u010den. Ovdje su predstavljene osnovne informacije o prosje\u010dnoj latenciji i IOPS-ima. Ove informacije su dostupne samo u stvarnom vremenu prema zadanim postavkama.<\/p>\n<p><img decoding=\"async\" alt=\"Analiza performansi VM-a u VMware vSphere. Dio 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 postoji nekoliko ekrana na kojima su predstavljene informacije o diskovnom sustavu doma\u0107ina, odre\u0111enim virtuelnim ma\u0161inama i njihovim diskovima.<\/p>\n<p>Zapo\u010det \u0107emo s informacijama o virtuelnim ma\u0161inama. Ekran 'Disk VM' poziva se tipkom 'v':<\/p>\n<p><img decoding=\"async\" alt=\"Analiza performansi VM-a u VMware vSphere. Dio 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-a. Da biste vidjeli informacije o svakom disku, pritisnite 'e' i unesite GID interesantne VM.<\/p>\n<p>Vrijednost ostalih parametara na ovom ekranu jasna je iz njihovih naziva.<\/p>\n<p>Jo\u0161 jedan koristan ekran za pronala\u017eenje problema je Disk adapter. Poziva se tipkom 'd' (na slici ispod su odabrana polja A, B, C, D, E, G):<\/p>\n<p><img decoding=\"async\" alt=\"Analiza performansi VM-a u VMware vSphere. Dio 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 putanja do lun-a koji su vidljivi s ovog adaptera. Da biste dobili informacije o svakoj putanji na adapteru, pritisnite 'e' i unesite naziv adaptera:<\/p>\n<p><img decoding=\"async\" alt=\"Analiza performansi VM-a u VMware vSphere. Dio 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>Tako\u0111er, na ovom ekranu su prikazani mjerni podaci o latenciji o kojima sam govorio ranije: <b>KAVG\/cmd, GAVG\/cmd, DAVG\/cmd, QAVG\/cmd<\/b>. <\/p>\n<p>Na ekranu Disk device, koji se poziva tipkom 'u', predstavljene su informacije o pojedina\u010dnim blokovnim ure\u0111ajima \u2013 lun-ovima (na slici ispod su odabrana polja A, B, F, G, I). Ovdje mo\u017eete vidjeti stanje reda za lun-ove. <\/p>\n<p><img decoding=\"async\" alt=\"Analiza performansi VM-a u VMware vSphere. Dio 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 ulazno\/izlaznih komandi u jezgru ESXi.<br \/>\n<b>QUED<\/b> \u2013 broj ulazno\/izlaznih komandi 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 pove\u0107anje reda. \u0160to vi\u0161e komandi u redu, ve\u0107i je QAVG i, shodno tome, KAVG.<\/p>\n<p>Na ekranu Disk device tako\u0111er mo\u017eete provjeriti radi li VAAI (vStorage API for Array Integration) na SAN-u. Da biste to u\u010dinili, odaberite polja A i O. <\/p>\n<p>Mehanizam VAAI omogu\u0107uje premje\u0161tanje dijela posla iz hipervizora izravno na SAN, na primjer, nulte blokove, kopiranje blokova ili zaklju\u010davanje.<\/p>\n<p><img decoding=\"async\" alt=\"Analiza performansi VM-a u VMware vSphere. Dio 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/131342d74e69af9c0898a1b350e883c8.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKao \u0161to je prikazano na slici iznad, VAAI radi na ovom SAN-u: aktivno se koriste primitivni Zero i ATS.<\/p>\n<h3>Savjeti za optimizaciju rada s diskovnim podsustavom na ESXi.<\/h3>\n<p><\/p>\n<ul>\n<li>Obratite pozornost na veli\u010dinu bloka.<\/li>\n<li>Postavite optimalnu veli\u010dinu reda na HBA.<\/li>\n<li>Ne zaboravite uklju\u010diti SIOC na datastore-ima.<\/li>\n<li>Odaberite PSP u skladu s preporukama proizvo\u0111a\u010da SAN-a.<\/li>\n<li>Provjerite radi li VAAI.<\/li>\n<\/ul>\n<p>\n<b class=\"spoiler_title\">Korisni \u010dlanci o temi:<\/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\/hr\/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=\"hr_HR\" \/>\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\/hr\/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 performansi VM u VMware vSphere. Dio 3: Storage | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"hr_HR","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\/hr\/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\/hr\/wp-json\/wp\/v2\/posts\/36486","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/comments?post=36486"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/36486\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media\/27306"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media?parent=36486"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/categories?post=36486"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/tags?post=36486"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}