{"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\/sq\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","title":{"rendered":"Analiza e performanc\u00ebs s\u00eb VM n\u00eb VMware vSphere. Pjesa 3: Storage","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb VM n\u00eb VMware vSphere. Pjesa 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\/\">Pjesa 1. Rreth CPU-s\u00eb<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/455820\/\">Pjesa 2. Rreth Memory<\/a><\/noindex><\/p>\n<p>Sot do t\u00eb shqyrtojm\u00eb metrikat e sistemit disk n\u00eb vSphere. Problemet me ruajtjen jan\u00eb arsyeja m\u00eb e zakonshme p\u00ebr ngadal\u00ebsin\u00eb e makin\u00ebs virtuale. Ndryshe nga CPU dhe RAM, ku diagnostikimi ndalon n\u00eb nivelin e hipervizorit, kur ka probleme me diskun, ndoshta do t\u00eb duhet t\u00eb shqyrtojm\u00eb rrjetin e transferimit t\u00eb t\u00eb dh\u00ebnave dhe ruajt\u00ebsin e lidhur.<\/p>\n<p>Tema do t\u00eb shqyrtohet n\u00eb shembullin e qasjes bllok, megjithat\u00eb, n\u00eb qasjen me skedar\u00eb, numrat jan\u00eb p\u00ebraf\u00ebrsisht t\u00eb nj\u00ebjt\u00eb.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Pak teori<\/h3>\n<p>\nKur flitet p\u00ebr performanc\u00ebn e sistemit disk t\u00eb makinave virtuale, zakonisht kushtohet v\u00ebmendje tre parametrave t\u00eb lidhur ngusht\u00eb:<\/p>\n<ul>\n<li>numri i operacioneve t\u00eb hyrjes\/daljeve (Input\/Output Operations Per Second, IOPS);<\/li>\n<li>kapaciteti (Throughput);<\/li>\n<li>vonesa e operacioneve t\u00eb hyrjes\/daljeve (Latency).<\/li>\n<\/ul>\n<p>\n<b>Numri i IOPS<\/b> zakaton \u00ebsht\u00eb i r\u00ebnd\u00ebsish\u00ebm p\u00ebr ngarkesa me karakter t\u00eb rast\u00ebsish\u00ebm (random): qasja n\u00eb blloqet e diskut t\u00eb shp\u00ebrndara n\u00eb vende t\u00eb ndryshme. Nj\u00eb shembull i till\u00eb ngarkese mund t\u00eb jen\u00eb bazat e t\u00eb dh\u00ebnave, aplikacionet e biznesit (ERP, CRM) etj.<\/p>\n<p><b>Kapaciteti i Kalimit<\/b> \u00ebsht\u00eb e r\u00ebnd\u00ebsishme p\u00ebr ngarkesa me karakter disaher\u00eb: qasja n\u00eb blloqet q\u00eb jan\u00eb ngjitur nj\u00ebri pas tjetrit. P\u00ebr shembull, ngarkesa e till\u00eb mund t\u00eb gjenerohet nga server\u00ebt e skedar\u00ebve (por jo gjithmon\u00eb) dhe sistemet e videov\u00ebzhgimit.<\/p>\n<p>Kapaciteti lidhet me numrin e operacioneve t\u00eb hyrjes\/daljeve n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb:<\/p>\n<p><i>Throughput = IOPS * Block size<\/i>, ku Block size \u00ebsht\u00eb madh\u00ebsia e bllokut.<\/p>\n<p>Madh\u00ebsia e bllokut \u00ebsht\u00eb nj\u00eb karakteristik\u00eb mjaft e r\u00ebnd\u00ebsishme. Versionet moderne t\u00eb ESXi lejojn\u00eb blloqe me madh\u00ebsi deri n\u00eb 32 767 KB. N\u00ebse blloku \u00ebsht\u00eb akoma m\u00eb i madh, ai ndahet n\u00eb disa blloqe. Jo t\u00eb gjith\u00eb ruajt\u00ebsit jan\u00eb n\u00eb gjendje t\u00eb punojn\u00eb efektivisht me blloqe t\u00eb tilla t\u00eb m\u00ebdha, prandaj n\u00eb Cil\u00ebsimet e Avancuara t\u00eb ESXi ekziston parametri DiskMaxIOSize. Me t\u00eb, mund t\u00eb zvog\u00ebloni madh\u00ebsin\u00eb maksimale t\u00eb bllokut q\u00eb lejohet nga hipervizori (Lexoni m\u00eb shum\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1003469\">k\u00ebtu<\/a><\/noindex>). Rekomandoj q\u00eb para se t\u00eb ndryshoni k\u00ebt\u00eb paramet\u00ebr t\u00eb konsultoheni me prodhuesin e ruajt\u00ebsit ose t\u00eb pakt\u00ebn t\u00eb testoni ndryshimet n\u00eb nj\u00eb mjedis laboratorik.\u00a0<\/p>\n<p>Madh\u00ebsia e madhe e bllokut mund t\u00eb ndihmoj\u00eb n\u00eb performanc\u00ebn e dob\u00ebt t\u00eb ruajt\u00ebsit. Edhe n\u00ebse numri i IOPS dhe kapaciteti jan\u00eb relativisht t\u00eb ul\u00ebt, mund t\u00eb ket\u00eb vonesa t\u00eb larta n\u00ebse madh\u00ebsia e bllokut \u00ebsht\u00eb e madhe. Prandaj, tregoni v\u00ebmendje ndaj k\u00ebtij parametri.<\/p>\n<p><b>Gabimi<\/b> \u2013 \u00ebsht\u00eb parametri m\u00eb interesant i performanc\u00ebs. Vonesa e operacioneve t\u00eb hyrjes\/daljeve p\u00ebr nj\u00eb makin\u00eb virtuale p\u00ebrb\u00ebhet nga:<\/p>\n<ul>\n<li>vonesa brenda hipervizorit (KAVG, Average Kernel MilliSec\/Read);<\/li>\n<li>vonesa q\u00eb jep rrjeti i transferimit t\u00eb t\u00eb dh\u00ebnave dhe ruajt\u00ebsi (DAVG, Average Driver MilliSec\/Command).<\/li>\n<\/ul>\n<p>\nVonesa totale, e cila shikohet n\u00eb sistemin e operimit t\u00eb mysafirit (GAVG, Average Guest MilliSec\/Command), \u00ebsht\u00eb shuma e KAVG dhe DAVG.<\/p>\n<p>GAVG dhe DAVG matet, kurse KAVG llogaritet: GAVG\u2013DAVG.<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb VM n\u00eb VMware vSphere. Pjesa 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>Burimi<\/i><\/a><\/noindex><\/p>\n<p>Le t\u00eb ndalemi pak m\u00eb shum\u00eb te <b>KAVG<\/b>. N\u00eb pun\u00ebn normale KAVG duhet t\u00eb p\u00ebrpiqet t\u00eb arrij\u00eb zero ose, t\u00eb pakt\u00ebn, t\u00eb jet\u00eb shum\u00eb m\u00eb e vog\u00ebl se DAVG. Nj\u00eb rast i vet\u00ebm i njohur p\u00ebr mua kur KAVG \u00ebsht\u00eb pritur t\u00eb jet\u00eb i lart\u00eb \u00ebsht\u00eb kufizimi i IOPS n\u00eb diskun e VM. N\u00eb k\u00ebt\u00eb rast, p\u00ebrpjekja p\u00ebr t\u00eb tejkaluar limitin do t\u00eb rris\u00eb KAVG.<\/p>\n<p>Pjesa m\u00eb e r\u00ebnd\u00ebsishme e KAVG \u00ebsht\u00eb QAVG \u2013 koha n\u00eb radh\u00eb p\u00ebr p\u00ebrpunim brenda hipervizorit. Pjes\u00ebt e tjera t\u00eb KAVG jan\u00eb shum\u00eb t\u00eb vogla p\u00ebr t'u konsideruar.<\/p>\n<p>Radh\u00ebt n\u00eb driver-in e adaptores s\u00eb diskut dhe radh\u00ebt p\u00ebr lun\u00ebt kan\u00eb nj\u00eb madh\u00ebsi fikse. P\u00ebr mjediset me ngarkes\u00eb t\u00eb lart\u00eb, ndonj\u00ebher\u00eb \u00ebsht\u00eb e dobishme t\u00eb rritet kjo madh\u00ebsi. <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1267\">K\u00ebtu<\/a><\/noindex> \u00ebsht\u00eb p\u00ebrshkruar si t\u00eb rriten radh\u00ebt n\u00eb driver-in e adaptores (nj\u00ebkoh\u00ebsisht do t\u00eb rritet edhe radh\u00ebt p\u00ebr lun\u00ebt). Ky paramet\u00ebr funksionon kur me lunin punon vet\u00ebm nj\u00eb VM, gj\u00eb q\u00eb ndodh rrall\u00eb. N\u00ebse me lunin punojn\u00eb disa VM, gjithashtu duhet t\u00eb rritet parametri <i>Disk.SchedNumReqOutstanding<\/i> (udh\u00ebzimi\u00a0 <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1268\">k\u00ebtu<\/a><\/noindex>). Duke rritur radh\u00ebn, ulni QAVG dhe KAVG p\u00ebrkat\u00ebsisht.<\/p>\n<p>Por, p\u00ebrs\u00ebri, fillimisht duhet t\u00eb njiheni me dokumentacionin e prodhuesit HBA dhe t\u00eb testoni ndryshimet n\u00eb nj\u00eb mjedis laboratorik. <\/p>\n<p>Madh\u00ebsia e radh\u00ebs p\u00ebr lun mund t\u00eb ndikohet nga aktivizimi i mekanizmit SIOC (Storage I\/O Control). Ai siguron nj\u00eb qasje t\u00eb barabart\u00eb n\u00eb lun nga t\u00eb gjith\u00eb serverat e klasterit duke ndryshuar dinamik radh\u00ebn p\u00ebr lun n\u00eb serverat. Pra, n\u00ebse n\u00eb ndonj\u00eb nga hostet punon nj\u00eb VM, e cila k\u00ebrkon nj\u00eb performanc\u00eb t\u00eb proporcioni shum\u00eb t\u00eb lart\u00eb (VM fqinj i zhurmsh\u00ebm), SIOC zvog\u00eblon gjat\u00ebsi radh\u00ebs p\u00ebr lun n\u00eb k\u00ebt\u00eb host (DQLEN). Lexoni m\u00eb shum\u00eb <noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2019\/03\/05\/dqlen-changes-what-is-going-on\/\">k\u00ebtu<\/a><\/noindex>.<\/p>\n<p>Tani q\u00eb e kuptuam KAVG, le t\u00eb flasim pak p\u00ebr <b>DAVG<\/b>. K\u00ebtu gjith\u00e7ka \u00ebsht\u00eb e thjesht\u00eb: DAVG \u00ebsht\u00eb vonesa q\u00eb sjell ambienti jasht\u00eb (rrjeti i transferimeve dhe ruajt\u00ebsi). N\u00eb \u00e7do ruajt\u00ebs modern, ka numra t\u00eb vet t\u00eb performanc\u00ebs. P\u00ebr analiz\u00ebn e problemeve me DAVG ka kuptim t\u00eb shikoni n\u00eb to. N\u00ebse nga ana e ESXi dhe ruajt\u00ebsit \u00ebsht\u00eb gjith\u00e7ka n\u00eb rregull, kontrolloni rrjetin e transferimit t\u00eb t\u00eb dh\u00ebnave.<\/p>\n<p>P\u00ebr t\u00eb shmangur problemet me performanc\u00ebn, zgjidhni Politiken e Zgjedhjes s\u00eb Rrug\u00ebve (PSP) t\u00eb duhur p\u00ebr sistemin tuaj t\u00eb ruajtjes. Praktikisht t\u00eb gjitha sistemet moderne t\u00eb ruajtjes mb\u00ebshtesin PSP Round-Robin (me ALUA, Asymmetric Logical Unit Access, ose pa t\u00eb). Kjo politik\u00eb lejon p\u00ebrdorimin e t\u00eb gjitha rrug\u00ebve t\u00eb disponueshme drejt sistemit t\u00eb ruajtjes. N\u00eb rastin e ALUA-s, p\u00ebrdoren vet\u00ebm rrug\u00ebt drejt kontrolluesit q\u00eb zot\u00ebron LUN-in. Jo t\u00eb gjitha sistemet e ruajtjes n\u00eb ESXi kan\u00eb rregulla t\u00eb paracaktuara q\u00eb vendosin politik\u00ebn Round-Robin. N\u00ebse p\u00ebr sistemin tuaj t\u00eb ruajtjes nuk ka rregulla, p\u00ebrdorni plugin-in e prodhuesit q\u00eb do t\u00eb krijoj\u00eb nj\u00eb rregull p\u00ebrkat\u00ebs n\u00eb t\u00eb gjitha hostet e klasterit, ose krijoni nj\u00eb rregull vet\u00eb. Detajet <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2053628\">k\u00ebtu<\/a><\/noindex>.\u00a0<\/p>\n<p>Gjithashtu, disa prodhues t\u00eb sistemeve t\u00eb ruajtjes rekomandojn\u00eb t\u00eb ndryshoni numrin e IOPS nga vlera standarde 1000 n\u00eb 1. N\u00eb praktik\u00ebn ton\u00eb, kjo na ka lejuar t\u00eb \"nxjerrim\" m\u00eb shum\u00eb performanc\u00eb nga sistemi i ruajtjes dhe t\u00eb reduktojm\u00eb ndjesh\u00ebm koh\u00ebn q\u00eb nevojitet p\u00ebr failover n\u00eb rast se ndodh ndonj\u00eb d\u00ebshtim ose p\u00ebrdit\u00ebsim t\u00eb kontrolluesve. Konsultohuni me rekomandimet e prodhuesit dhe n\u00ebse nuk ka kund\u00ebrshtime, provoni t\u00eb ndryshoni k\u00ebt\u00eb paramet\u00ebr. Detajet <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2069356\">k\u00ebtu<\/a><\/noindex>.<\/p>\n<h3>Numrat kryesor\u00eb t\u00eb performanc\u00ebs s\u00eb n\u00ebn-sistem\u00ebve t\u00eb disk\u00ebve t\u00eb makin\u00ebs virtuale<\/h3>\n<p>\nNumrat e performanc\u00ebs s\u00eb n\u00ebn-sistem\u00ebve t\u00eb disk\u00ebve n\u00eb vCenter jan\u00eb t\u00eb mbledhur n\u00eb seksionet Datastore, Disk, Virtual Disk:<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb VM n\u00eb VMware vSphere. Pjesa 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/ae852a6a128914a7aff36f461c5f0721.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n <br \/>\nN\u00eb seksionin <b>Datastore<\/b> jan\u00eb metrikat p\u00ebr objektet e ruajtjes vSphere (datastoret) ku ndodhen disk\u00ebt e VM. K\u00ebtu do t\u00eb gjeni numra standard p\u00ebr:<\/p>\n<ul>\n<li>IOPS (K\u00ebrkesat mesatare p\u00ebr lexim\/shkrim n\u00eb sekond\u00eb),\u00a0<\/li>\n<li>kapacitetin (Shkalla e Leximit\/Shkruarjes),\u00a0<\/li>\n<li>von\u00ebset (Lexim\/Shkrim\/Von\u00ebsimi m\u00eb i lart\u00eb).<\/li>\n<\/ul>\n<p>\nNga emrat e numrave, n\u00eb p\u00ebrgjith\u00ebsi \u00ebsht\u00eb e qart\u00eb. S\u00ebrish do t\u00eb theksoj se k\u00ebtu statistikat nuk jan\u00eb p\u00ebr nj\u00eb VM specifike (ose p\u00ebr diskun e VM-s\u00eb), por jan\u00eb t\u00eb p\u00ebrgjithshme p\u00ebr t\u00eb gjith\u00eb datastorin. N\u00eb mendimin tim, kjo statistik\u00eb \u00ebsht\u00eb m\u00eb e leht\u00eb p\u00ebr t'u par\u00eb n\u00eb ESXTOP, duke marr\u00eb parasysh se periudha minimale e matjes aty \u00ebsht\u00eb 2 sekonda.<\/p>\n<p>N\u00eb seksionin <b>Disk<\/b> jan\u00eb metrikat p\u00ebr pajisjet bllokuese q\u00eb p\u00ebrdoren nga VM. K\u00ebtu ka numra p\u00ebr IOPS t\u00eb tipit summation (numri i operacioneve t\u00eb hyrjes\/daljes gjat\u00eb periudh\u00ebs s\u00eb matjes) dhe disa numra q\u00eb i p\u00ebrkasin qasjes bllokuese (Commands aborted, Bus resets). K\u00ebt\u00eb informacion, n\u00eb mendimin tim, \u00ebsht\u00eb gjithashtu m\u00eb e leht\u00eb ta shihni n\u00eb ESXTOP.<\/p>\n<p>Pjesa <b>Virtual Disk<\/b> \u00ebsht\u00eb m\u00eb i dobish\u00ebm p\u00ebr t\u00eb gjetur problemet e performanc\u00ebs s\u00eb n\u00ebn-sistemit t\u00eb disk\u00ebve t\u00eb VM. K\u00ebtu mund t\u00eb shihni performanc\u00ebn p\u00ebr secil\u00ebn disk virtual. Kjo informacion \u00ebsht\u00eb e nevojshme p\u00ebr t\u00eb kuptuar n\u00ebse ka ndonj\u00eb problem te nj\u00eb makin\u00eb virtuale specifike. P\u00ebrve\u00e7 numrave standard t\u00eb operacioneve t\u00eb hyrjes\/daljes, volumit t\u00eb leximit\/shkrimit dhe von\u00ebsave, n\u00eb k\u00ebt\u00eb seksion ka numra t\u00eb dobish\u00ebm q\u00eb tregojn\u00eb madh\u00ebsin\u00eb e bllokut: Madh\u00ebsia e k\u00ebrkes\u00ebs p\u00ebr Lexim\/Shkrim.<\/p>\n<p>N\u00eb imazhin m\u00eb posht\u00eb \u00ebsht\u00eb grafiku i performanc\u00ebs s\u00eb diskut t\u00eb VM, ku mund t\u00eb shihni numrin e IOPS, vonesat dhe madh\u00ebsin\u00eb e bllokut.\u00a0<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb VM n\u00eb VMware vSphere. Pjesa 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/36d2a4d006d2c1bfd4d9961c745f26b6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nGjithashtu, metrikat e performanc\u00ebs mund t\u00eb shihen p\u00ebr t\u00ebr\u00eb datastorin, n\u00ebse \u00ebsht\u00eb aktivizuar SIOC. K\u00ebtu paraqitet informacioni baz\u00eb p\u00ebr vones\u00ebn mesatare dhe IOPS. Nga default, ky informacion mund t\u00eb shikohet vet\u00ebm n\u00eb koh\u00eb reale.<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb VM n\u00eb VMware vSphere. Pjesa 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>\nN\u00eb ESXTOP ka disa ekrane, ku prezantohet informacioni p\u00ebr n\u00ebn-sistemin e disk\u00ebve t\u00eb hostit n\u00eb t\u00ebr\u00ebsi, makinat virtuale t\u00eb ve\u00e7anta dhe disk\u00ebt e tyre.<\/p>\n<p>Le t\u00eb fillojm\u00eb me informacionin p\u00ebr makinat virtuale. Ekrani \"Disk VM\" aktivizohet me \u00e7el\u00ebsin \"v\":<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb VM n\u00eb VMware vSphere. Pjesa 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/793273e19fca1e4f19b96204202019fb.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>NVDISK<\/b> - \u00ebsht\u00eb numri i disk\u00ebve t\u00eb VM. P\u00ebr t\u00eb par\u00eb informacionin p\u00ebr secilin disk, shtypni \"e\" dhe, n\u00ebse \u00ebsht\u00eb e nevojshme, shkruani GID e VM-s\u00eb q\u00eb ju intereson.<\/p>\n<p>Vlera e parametrave t\u00eb tjer\u00eb n\u00eb k\u00ebt\u00eb ekran \u00ebsht\u00eb e qart\u00eb nga emrat e tyre.<\/p>\n<p>Nj\u00eb ekran tjet\u00ebr i dobish\u00ebm n\u00eb gjetjen e problemeve \u00ebsht\u00eb \u2013 Disk adapter. Aktivizohet me \u00e7el\u00ebsin \"d\" (n\u00eb imazhin m\u00eb posht\u00eb jan\u00eb zgjedhur fushat A,B,C,D,E,G):<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb VM n\u00eb VMware vSphere. Pjesa 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/71a7f1e3f1e40f3dbacf61385a3c07cc.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>NPTH<\/b> - numri i rrug\u00ebve drejt LUN-ave q\u00eb jan\u00eb t\u00eb dukshme nga ky adaptues. P\u00ebr t\u00eb marr\u00eb informacion p\u00ebr secil\u00ebn rrug\u00eb n\u00eb adaptues, shtypni \"e\" dhe shkruani emrin e adaptuesit:<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb VM n\u00eb VMware vSphere. Pjesa 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/12661003ce8be542ed4c5e262da77d90.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>AQLEN<\/b> - madh\u00ebsia maksimale e radh\u00ebs n\u00eb adaptues.<\/p>\n<p>Gjithashtu n\u00eb k\u00ebt\u00eb ekran jan\u00eb paraqitur numrat e vonesave p\u00ebr t\u00eb cilat kam folur m\u00eb lart: <b>KAVG\/cmd, GAVG\/cmd, DAVG\/cmd, QAVG\/cmd<\/b>. <\/p>\n<p>N\u00eb ekranin Disk device, i cili aktivizohet me \u00e7el\u00ebsin \"u\", paraqitet informacioni p\u00ebr pajisjet e ve\u00e7anta bllokuese \u2013 LUN-ave (n\u00eb imazhin m\u00eb posht\u00eb jan\u00eb zgjedhur fushat A, B, F, G, I). K\u00ebtu mund t\u00eb shihni gjendjen e radh\u00ebs ndaj LUN-ave. <\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb VM n\u00eb VMware vSphere. Pjesa 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/6331ee64398fe7057c0eec015165f0a5.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>DQLEN<\/b> - madh\u00ebsia e radh\u00ebs p\u00ebr pajisjen bllokuese.<br \/>\n<b>ACTV<\/b> - numri i komandave t\u00eb hyrjes\/daljes n\u00eb b\u00ebrtham\u00ebn ESXi.<br \/>\n<b>QUED<\/b> - numri i komandave t\u00eb hyrjes\/daljes n\u00eb radh\u00eb.<br \/>\n<b>%USD<\/b> - ACTV \/ DQLEN \u00d7 100%.<br \/>\n<b>LOAD<\/b> - (ACTV + QUED) \/ DQLEN.<\/p>\n<p>N\u00ebse %USD \u00ebsht\u00eb i lart\u00eb, \u00ebsht\u00eb e arsyeshme t\u00eb shqyrtohet mund\u00ebsia e rritjes s\u00eb radh\u00ebs. Sa m\u00eb shum\u00eb komanda t\u00eb jen\u00eb n\u00eb radh\u00eb, aq m\u00eb e lart\u00eb \u00ebsht\u00eb QAVG dhe, p\u00ebr rrjedhoj\u00eb, KAVG.<\/p>\n<p>Gjithashtu, n\u00eb ekranin Disk device mund t\u00eb shihni n\u00ebse \u00ebsht\u00eb aktiv VAAI (vStorage API p\u00ebr Integrimin e Array). P\u00ebr k\u00ebt\u00eb, duhet t\u00eb zgjidhni fushat A dhe O. <\/p>\n<p>Mekanizmi VAAI lejon transferimin e nj\u00eb pjes\u00eb t\u00eb pun\u00ebs nga hipervizori direkt n\u00eb sistemin e ruajtjes, p\u00ebr shembull, zerimin, kopjimin e blloqeve ose bllokimin.<\/p>\n<p><img decoding=\"async\" alt=\"Analiza e performanc\u00ebs s\u00eb VM n\u00eb VMware vSphere. Pjesa 3: Storage\" src=\"\/wp-content\/uploads\/2019\/07\/131342d74e69af9c0898a1b350e883c8.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nSi\u00e7 shihet n\u00eb imazhin m\u00eb sip\u00ebr, VAAI funksionon n\u00eb k\u00ebt\u00eb sistem ruajtjeje: p\u00ebrdoren aktivisht primitiv\u00ebt Zero dhe ATS.<\/p>\n<h3>K\u00ebshilla p\u00ebr optimizimin e pun\u00ebs me sistemin e disk\u00ebve n\u00eb ESXi<\/h3>\n<p><\/p>\n<ul>\n<li>Kujdesuni p\u00ebr madh\u00ebsin\u00eb e bllokut.<\/li>\n<li>Vendosni madh\u00ebsin\u00eb optimale t\u00eb radh\u00ebs n\u00eb HBA.<\/li>\n<li>Mos harroni t\u00eb aktivizoni SIOC n\u00eb datastores.<\/li>\n<li>Zgjidhni PSP n\u00eb p\u00ebrputhje me rekomandimet e prodhuesit t\u00eb sistemit t\u00eb ruajtjes.<\/li>\n<li>Sigurohuni q\u00eb VAAI funksionon.<\/li>\n<\/ul>\n<p>\n<b class=\"spoiler_title\">Artikuj t\u00eb dobish\u00ebm mbi tem\u00ebn:<\/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>Burimi: <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.0.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0427\u0430\u0441\u0442\u044c 1. \u041f\u0440\u043e CPU \u0427\u0430\u0441\u0442\u044c 2. \u041f\u0440\u043e Memory \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u0440\u0430\u0437\u0431\u0435\u0440\u0435\u043c \u043c\u0435\u0442\u0440\u0438\u043a\u0438 \u0434\u0438\u0441\u043a\u043e\u0432\u043e\u0439 \u043f\u043e\u0434\u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0432 vSphere. \u041f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0441\u043e \u0441\u0442\u043e\u0440\u0430\u0434\u0436\u0435\u043c \u2013 \u0441\u0430\u043c\u0430\u044f \u0447\u0430\u0441\u0442\u0430\u044f \u043f\u0440\u0438\u0447\u0438\u043d\u0430 \u043c\u0435\u0434\u043b\u0435\u043d\u043d\u043e\u0439 \u0440\u0430\u0431\u043e\u0442\u044b \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0439 \u043c\u0430\u0448\u0438\u043d\u044b. \u0415\u0441\u043b\u0438 \u0432 \u0441\u043b\u0443\u0447\u0430\u044f\u0445 \u0441 CPU \u0438 RAM \u0442\u0440\u0430\u0431\u043b\u0448\u0443\u0442\u0438\u043d\u0433 \u0437\u0430\u043a\u0430\u043d\u0447\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 \u0433\u0438\u043f\u0435\u0440\u0432\u0438\u0437\u043e\u0440\u0430, \u0442\u043e \u043f\u0440\u0438 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430\u0445 \u0441 \u0434\u0438\u0441\u043a\u043e\u043c, \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e, \u043f\u0440\u0438\u0434\u0435\u0442\u0441\u044f \u0440\u0430\u0437\u0431\u0438\u0440\u0430\u0442\u044c\u0441\u044f \u0441 \u0441\u0435\u0442\u044c\u044e \u043f\u0435\u0440\u0435\u0434\u0430\u0447\u0438 \u0434\u0430\u043d\u043d\u044b\u0445 \u0438 \u0421\u0425\u0414. \u0422\u0435\u043c\u0443 \u0431\u0443\u0434\u0443 \u0440\u0430\u0437\u0431\u0438\u0440\u0430\u0442\u044c\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.0.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0410\u043d\u0430\u043b\u0438\u0437 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0412\u041c \u0432 VMware vSphere. \u0427\u0430\u0441\u0442\u044c 3: Storage | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0427\u0430\u0441\u0442\u044c 1. \u041f\u0440\u043e CPU \u0427\u0430\u0441\u0442\u044c 2. \u041f\u0440\u043e Memory \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u0440\u0430\u0437\u0431\u0435\u0440\u0435\u043c \u043c\u0435\u0442\u0440\u0438\u043a\u0438 \u0434\u0438\u0441\u043a\u043e\u0432\u043e\u0439 \u043f\u043e\u0434\u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0432 vSphere. \u041f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0441\u043e \u0441\u0442\u043e\u0440\u0430\u0434\u0436\u0435\u043c \u2013 \u0441\u0430\u043c\u0430\u044f \u0447\u0430\u0441\u0442\u0430\u044f \u043f\u0440\u0438\u0447\u0438\u043d\u0430 \u043c\u0435\u0434\u043b\u0435\u043d\u043d\u043e\u0439 \u0440\u0430\u0431\u043e\u0442\u044b \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0439 \u043c\u0430\u0448\u0438\u043d\u044b. \u0415\u0441\u043b\u0438 \u0432 \u0441\u043b\u0443\u0447\u0430\u044f\u0445 \u0441 CPU \u0438 RAM \u0442\u0440\u0430\u0431\u043b\u0448\u0443\u0442\u0438\u043d\u0433 \u0437\u0430\u043a\u0430\u043d\u0447\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 \u0433\u0438\u043f\u0435\u0440\u0432\u0438\u0437\u043e\u0440\u0430, \u0442\u043e \u043f\u0440\u0438 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430\u0445 \u0441 \u0434\u0438\u0441\u043a\u043e\u043c, \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e, \u043f\u0440\u0438\u0434\u0435\u0442\u0441\u044f \u0440\u0430\u0437\u0431\u0438\u0440\u0430\u0442\u044c\u0441\u044f \u0441 \u0441\u0435\u0442\u044c\u044e \u043f\u0435\u0440\u0435\u0434\u0430\u0447\u0438 \u0434\u0430\u043d\u043d\u044b\u0445 \u0438 \u0421\u0425\u0414. \u0422\u0435\u043c\u0443 \u0431\u0443\u0434\u0443 \u0440\u0430\u0437\u0431\u0438\u0440\u0430\u0442\u044c\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/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 e performanc\u00ebs s\u00eb VM n\u00eb VMware vSphere. Pjesa 3: Storage | ProHoster","description":"Pjesa 1. P\u00ebr CPU Pjesa 2. P\u00ebr Memory Sot do t\u00eb shqyrtojm\u00eb metrikat e sistemit t\u00eb disk\u00ebve n\u00eb vSphere. Problemi me ruajtjen \u00ebsht\u00eb arsyeja m\u00eb e zakonshme e ngadal\u00ebsimit t\u00eb pun\u00ebs s\u00eb makin\u00ebs virtuale. N\u00eb rastet me CPU dhe RAM, problemet p\u00ebrfundojn\u00eb n\u00eb nivelin e hipervizorit, nd\u00ebrsa p\u00ebr problemet me diskun, ndoshta do t\u00eb duhet t\u00eb merremi me rrjetin e transmetimit t\u00eb t\u00eb dh\u00ebnave dhe sistemin e ruajtjes. Tem\u00ebn do ta diskutoj","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0410\u043d\u0430\u043b\u0438\u0437 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0412\u041c \u0432 VMware vSphere. \u0427\u0430\u0441\u0442\u044c 3: Storage | ProHoster","og:description":"\u0427\u0430\u0441\u0442\u044c 1. \u041f\u0440\u043e CPU \u0427\u0430\u0441\u0442\u044c 2. \u041f\u0440\u043e Memory \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u0440\u0430\u0437\u0431\u0435\u0440\u0435\u043c \u043c\u0435\u0442\u0440\u0438\u043a\u0438 \u0434\u0438\u0441\u043a\u043e\u0432\u043e\u0439 \u043f\u043e\u0434\u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0432 vSphere. \u041f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0441\u043e \u0441\u0442\u043e\u0440\u0430\u0434\u0436\u0435\u043c \u2013 \u0441\u0430\u043c\u0430\u044f \u0447\u0430\u0441\u0442\u0430\u044f \u043f\u0440\u0438\u0447\u0438\u043d\u0430 \u043c\u0435\u0434\u043b\u0435\u043d\u043d\u043e\u0439 \u0440\u0430\u0431\u043e\u0442\u044b \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0439 \u043c\u0430\u0448\u0438\u043d\u044b. \u0415\u0441\u043b\u0438 \u0432 \u0441\u043b\u0443\u0447\u0430\u044f\u0445 \u0441 CPU \u0438 RAM \u0442\u0440\u0430\u0431\u043b\u0448\u0443\u0442\u0438\u043d\u0433 \u0437\u0430\u043a\u0430\u043d\u0447\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u043d\u0430 \u0443\u0440\u043e\u0432\u043d\u0435 \u0433\u0438\u043f\u0435\u0440\u0432\u0438\u0437\u043e\u0440\u0430, \u0442\u043e \u043f\u0440\u0438 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430\u0445 \u0441 \u0434\u0438\u0441\u043a\u043e\u043c, \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e, \u043f\u0440\u0438\u0434\u0435\u0442\u0441\u044f \u0440\u0430\u0437\u0431\u0438\u0440\u0430\u0442\u044c\u0441\u044f \u0441 \u0441\u0435\u0442\u044c\u044e \u043f\u0435\u0440\u0435\u0434\u0430\u0447\u0438 \u0434\u0430\u043d\u043d\u044b\u0445 \u0438 \u0421\u0425\u0414. \u0422\u0435\u043c\u0443 \u0431\u0443\u0434\u0443 \u0440\u0430\u0437\u0431\u0438\u0440\u0430\u0442\u044c","og:url":"https:\/\/prohoster.info\/sq\/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\/sq\/wp-json\/wp\/v2\/posts\/36486","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=36486"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/36486\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/27306"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=36486"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=36486"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=36486"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}