{"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 procesorit<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/455820\/\">Pjesa 2. Rreth Memories<\/a><\/noindex><\/p>\n<p>Sot do t\u00eb shqyrtojm\u00eb metrikat e sistemit t\u00eb ruajtjes n\u00eb vSphere. Problemi me ruajtjen \u00ebsht\u00eb arsyeja m\u00eb e zakonshme e ngadal\u00ebsimit t\u00eb funksionimit t\u00eb makin\u00ebs virtuale. Kur p\u00ebr CPU dhe RAM problemi zgjidhet n\u00eb nivelin e hipervizorit, n\u00eb rastet e problemeve me disqet, mund t\u00eb jet\u00eb e nevojshme t\u00eb merremi me rrjetin e transferimit t\u00eb t\u00eb dh\u00ebnave dhe sistemin e ruajtjes.<\/p>\n<p>Tem\u00ebn do ta shqyrtoj me shembuj t\u00eb qasjes bllok n\u00eb sistemin e ruajtjes, megjithat\u00eb, me qasje skedar\u00ebsh, treguesit jan\u00eb af\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 t\u00eb ruajtjes s\u00eb makinave virtuale, zakonisht i kushtohet v\u00ebmendje tre parametrave t\u00eb lidhur me nj\u00ebri-tjetrin:<\/p>\n<ul>\n<li>numri i operacioneve t\u00eb hyrje\/dalje (Input\/Output Operations Per Second, IOPS);<\/li>\n<li>kapaciteti (Throughput);<\/li>\n<li>vonesa e operacioneve t\u00eb hyrje\/dalje (Latency).<\/li>\n<\/ul>\n<p>\n<b>Numri i IOPS<\/b> zakonisht \u00ebsht\u00eb i r\u00ebnd\u00ebsish\u00ebm p\u00ebr ngarkesat e natyr\u00ebs s\u00eb rast\u00ebsishme (random): qasja n\u00eb blloqet e diskut t\u00eb vendosura 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<\/b> \u00ebsht\u00eb e r\u00ebnd\u00ebsishme p\u00ebr ngarkesat e natyr\u00ebs s\u00eb rregullt: qasja n\u00eb blloqet, t\u00eb vendosura nj\u00ebri pas tjetrit. P\u00ebr shembull, nj\u00eb ngarkes\u00eb e till\u00eb mund t\u00eb gjenerohet nga server\u00ebt e skedar\u00ebve (por jo gjithmon\u00eb) dhe sistemet e mbik\u00ebqyrjes video.<\/p>\n<p>Kapaciteti \u00ebsht\u00eb i lidhur me numrin e operacioneve t\u00eb hyrje\/dalje n\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb:<\/p>\n<p><i>Throughput = IOPS * Sasia e bllokut<\/i>, ku Sasia e bllokut \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 kalojn\u00eb blloqe me madh\u00ebsi deri n\u00eb 32,767 KB. N\u00ebse blloku \u00ebsht\u00eb edhe m\u00eb i madh, ai ndahet n\u00eb disa. Jo t\u00eb gjitha sistemet e ruajtjes mund t\u00eb funksionojn\u00eb efikasht me blloqe kaq t\u00eb m\u00ebdha, prandaj n\u00eb Cil\u00ebsimet e Avancuara t\u00eb ESXi ka nj\u00eb paramet\u00ebr DiskMaxIOSize. Me ndihm\u00ebn e tij, mund t\u00eb zvog\u00ebloni madh\u00ebsin\u00eb maksimale t\u00eb bllokut q\u00eb kalon hipervizori (m\u00eb shum\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1003469\">k\u00ebtu<\/a><\/noindex>). Rekomandoj q\u00eb para ndryshimit t\u00eb k\u00ebtij parametri t\u00eb konsultoheni me prodhuesin e sistemit t\u00eb ruajtjes ose s\u00eb paku t\u00eb testoni ndryshimet n\u00eb nj\u00eb ambient laboratorik.\u00a0<\/p>\n<p>Madh\u00ebsia e madhe e bllokut mund t\u00eb ndikoj\u00eb negatively n\u00eb performanc\u00ebn e sistemit t\u00eb ruajtjes. Edhe n\u00ebse numri i IOPS dhe throughput \u00ebsht\u00eb relativisht i vog\u00ebl, me madh\u00ebsi t\u00eb madhe blloku mund t\u00eb shfaqen vonesa t\u00eb larta. Prandaj, kushtojini v\u00ebmendje k\u00ebtij parametri.<\/p>\n<p><b>Latenca<\/b> \u2013 parametri m\u00eb interesant i performanc\u00ebs. Vonesa e operacioneve t\u00eb hyrje\/dalje p\u00ebr makin\u00ebn virtuale p\u00ebrb\u00ebhet nga:<\/p>\n<ul>\n<li>vonesa brenda hipervizorit (KAVG, Average Kernel MilliSec\/Read);<\/li>\n<li>mungesa q\u00eb ofrojn\u00eb rrjetin e transmetimit t\u00eb t\u00eb dh\u00ebnave dhe S\u00c7D (DAVG, Milisekonda e Mesme e Drejtuesit \/ Komand\u00ebs).<\/li>\n<\/ul>\n<p>\nMungesa totale, e cila \u00ebsht\u00eb e dukshme n\u00eb OS-n\u00eb mysafire (GAVG, Milisekonda e Mesme e Mysafirit \/ Komand\u00ebs), \u00ebsht\u00eb shuma e KAVG dhe DAVG.<\/p>\n<p>GAVG dhe DAVG maten, nd\u00ebrsa 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 n\u00eb <b>KAVG<\/b>. N\u00eb nj\u00eb funksionim normal, KAVG duhet t\u00eb tendoset drejt zeros ose, t\u00eb pakt\u00ebn, t\u00eb jet\u00eb shum\u00eb m\u00eb e vog\u00ebl se DAVG. Rasti i vet\u00ebm q\u00eb njoh ku KAVG pritet t\u00eb jet\u00eb i lart\u00eb \u00ebsht\u00eb kufizimi IOPS n\u00eb disqin e VM. N\u00eb k\u00ebt\u00eb rast, kur p\u00ebrpiqeni t\u00eb kaloni limitin, KAVG do t\u00eb rritet.<\/p>\n<p>Pjesa m\u00eb e r\u00ebnd\u00ebsishme e KAVG \u00ebsht\u00eb QAVG - koha n\u00eb radh\u00eb p\u00ebr p\u00ebrpunim brenda hipervizorit. Pjes\u00ebt e tjera t\u00eb KAVG jan\u00eb t\u00eb pap\u00ebrfillshme.<\/p>\n<p>Radh\u00ebt n\u00eb drejtuesin e adaptorit t\u00eb diskut dhe radh\u00ebt ndaj lunave kan\u00eb nj\u00eb madh\u00ebsi fikse. P\u00ebr mjediset me ngarkes\u00eb t\u00eb lart\u00eb, \u00ebsht\u00eb e dobishme ta rrisni k\u00ebt\u00eb 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 rrisni radh\u00ebt n\u00eb drejtuesin e adaptorit (nj\u00ebkoh\u00ebsisht do t\u00eb rritet radh\u00ebt ndaj lunave). Ky rregullim funksionon kur n\u00eb lun punon vet\u00ebm nj\u00eb VM, e cila ndodh rrall\u00eb. N\u00ebse n\u00eb lun jan\u00eb disa VM, \u00ebsht\u00eb e nevojshme gjithashtu t\u00eb rrisni parametrin <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, ju zvog\u00ebloni QAVG dhe KAVG p\u00ebrkat\u00ebsisht.<\/p>\n<p>Por, s\u00ebrish, fillimisht shikoni dokumentacionin nga furnizuesi HBA dhe testoni ndryshimet n\u00eb nj\u00eb laborator. <\/p>\n<p>Madh\u00ebsia e radh\u00ebs ndaj lun\u00ebs mund t\u00eb ndikoj\u00eb nga aktivizimi i mekanizmit SIOC (Kontrolli i I\/O S\u00eb Ruajtjes). Ai siguron akses t\u00eb barabart\u00eb n\u00eb lun nga t\u00eb gjitha server\u00ebt e grupit duke ndryshuar dinamikisht radh\u00ebn ndaj lun\u00ebs n\u00eb serverat. Kjo do t\u00eb thot\u00eb q\u00eb, n\u00ebse n\u00eb ndonj\u00eb nga host\u00ebt punon nj\u00eb VM q\u00eb k\u00ebrkon nj\u00eb performanc\u00eb t\u00eb proporcioni t\u00eb lart\u00eb (noisy neighbor VM), SIOC zvog\u00eblon gjat\u00ebsin\u00eb e radh\u00ebs ndaj lun\u00ebs n\u00eb k\u00ebt\u00eb host (DQLEN). M\u00eb shum\u00eb informacion <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>Me KAVG e diskutua, tani pak mbi <b>DAVG<\/b>. K\u00ebtu \u00ebsht\u00eb e thjesht\u00eb: DAVG \u00ebsht\u00eb vonesa e sjell\u00eb nga ambienti i jasht\u00ebm (rrjeti i transmetimit t\u00eb t\u00eb dh\u00ebnave dhe S\u00c7D). N\u00eb \u00e7do S\u00c7D moderne dhe jo shum\u00eb, ka numra t\u00eb performanc\u00ebs. P\u00ebr t\u00eb analizuar problemet me DAVG, ka kuptim t\u00eb shikoni ata. N\u00ebse nga ana e ESXi dhe S\u00c7D gjith\u00e7ka \u00ebsht\u00eb mir\u00eb, kontrolloni rrjetin e transmetimit 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\u00ebs (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, Asimetri\u00e7ka Qasje n\u00eb Nj\u00ebsit\u00eb Logjike, ose pa t\u00eb). Kjo politik\u00eb lejon p\u00ebrdorimin e t\u00eb gjitha rrug\u00ebve t\u00eb disponueshme p\u00ebr sistemin e ruajtjes. N\u00eb rastin e ALUA p\u00ebrdoren vet\u00ebm rrug\u00ebt deri te kontrolluesi q\u00eb zot\u00ebron LUN-in. Nuk jan\u00eb t\u00eb gjitha sistemet e ruajtjes n\u00eb ESXi q\u00eb kan\u00eb rregulla t\u00eb parazgjedhura, t\u00eb cilat vendosin politik\u00ebn Round-Robin. N\u00ebse p\u00ebr sistemin tuaj t\u00eb ruajtjes nuk ka rregulla, p\u00ebrdorni nj\u00eb plugin nga prodhuesi i sistemit, i cili do t\u00eb krijoj\u00eb rregullin p\u00ebrkat\u00ebs n\u00eb t\u00eb gjitha hostet e klasterit, ose krijoni rregullin vet\u00eb. Detaje <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2053628\">k\u00ebtu<\/a><\/noindex>.\u00a0<\/p>\n<p>Po ashtu disa prodhues t\u00eb sistemit 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 ka lejuar \"t\u00eb nxjerrim\" m\u00eb shum\u00eb performanc\u00eb nga sistemi i ruajtjes dhe t\u00eb reduktojm\u00eb ndjesh\u00ebm koh\u00ebn e nevojshme p\u00ebr failover n\u00eb rast d\u00ebshtimi apo p\u00ebrdit\u00ebsimi t\u00eb kontrolluesve. Rishikoni rekomandimet e ofruesit, dhe n\u00ebse nuk ka kund\u00ebrshtime, provoni t\u00eb ndryshoni k\u00ebt\u00eb paramet\u00ebr. Detaje <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2069356\">k\u00ebtu<\/a><\/noindex>.<\/p>\n<h3>Matrica kryesore t\u00eb performanc\u00ebs s\u00eb n\u00ebnsystemit disk t\u00eb makin\u00ebs virtuale<\/h3>\n<p>\nMatrica e performanc\u00ebs s\u00eb n\u00ebnsystemit disk n\u00eb vCenter jan\u00eb mbledhur n\u00eb seksionet Datastore, Disk, Disku Virtual:<\/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> ndodhen metrikat p\u00ebr ruajtjet disk vSphere (datastoret), n\u00eb t\u00eb cilat ndodhen disqet e VM. K\u00ebtu do t\u00eb gjeni matjet standarde p\u00ebr:<\/p>\n<ul>\n<li>IOPS (K\u00ebrkesat mesatare t\u00eb leximit\/shkrimit p\u00ebr sekond\u00eb),\u00a0<\/li>\n<li>kapacitetin (Shpejt\u00ebsia e Leximit\/Shkrimit),\u00a0<\/li>\n<li>vonesat (Vonesa e Leximit\/Shkrimit\/Vonesa m\u00eb e lart\u00eb).<\/li>\n<\/ul>\n<p>\nNga emrat e matjeve n\u00eb t\u00eb v\u00ebrtet\u00eb \u00ebsht\u00eb gjith\u00e7ka e kuptueshme. P\u00ebrs\u00ebris se k\u00ebtu statistika nuk \u00ebsht\u00eb p\u00ebr nj\u00eb VM (apo disk t\u00eb VM) t\u00eb ve\u00e7ant\u00eb, por e p\u00ebrgjithshme p\u00ebr t\u00eb gjith\u00eb datastorin. N\u00eb mendimin tim, \u00ebsht\u00eb m\u00eb e leht\u00eb t\u00eb shikohet kjo statistik\u00eb n\u00eb ESXTOP, t\u00eb pakt\u00ebn duke pasur parasysh q\u00eb periudha minimale e matjes atje \u00ebsht\u00eb 2 sekonda.<\/p>\n<p>N\u00eb seksionin <b>Disk<\/b> ndodhen metrikat p\u00ebr pajisjet bllokuese, t\u00eb cilat p\u00ebrdoren nga VM. K\u00ebtu ka matje p\u00ebr IOPS t\u00eb tipit summation (numri i operacioneve t\u00eb hyrjes\/daljes n\u00eb periudh\u00ebn e matjes) dhe disa matje t\u00eb tjera t\u00eb lidhura me qasjen bllokuese (Komandat e nd\u00ebrprera, Rivendosjet e autobus\u00ebve). N\u00eb mendimin tim, \u00ebsht\u00eb gjithashtu m\u00eb e leht\u00eb t\u00eb shikohet kjo informacion n\u00eb ESXTOP.<\/p>\n<p>Seksioni <b>Disku Virtual<\/b> \u2013 \u00ebsht\u00eb m\u00eb i dobish\u00ebm p\u00ebr gjetjen e problemeve me performanc\u00ebn e n\u00ebnshkall\u00ebs diskore t\u00eb VM. K\u00ebtu mund t\u00eb shihni performanc\u00ebn e \u00e7do disku virtual. Kjo \u00ebsht\u00eb informacioni q\u00eb nevojitet p\u00ebr t\u00eb kuptuar n\u00ebse ka nj\u00eb problem me nj\u00eb makin\u00eb virtuale t\u00eb ve\u00e7ant\u00eb. P\u00ebrve\u00e7 hesapimeve standarde t\u00eb numrit t\u00eb operacioneve t\u00eb hyrjes\/daljes, volumit t\u00eb leximit\/shkrimit dhe vonesave, n\u00eb k\u00ebt\u00eb seksion ka parameter 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 figur\u00ebn m\u00eb posht\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 \/>\nPo ashtu, metrikat e performanc\u00ebs mund t\u00eb shihen p\u00ebr t\u00ebr\u00eb datastorin, n\u00ebse SIOC \u00ebsht\u00eb i aktivizuar. K\u00ebtu \u00ebsht\u00eb paraqitur informacion i baz\u00ebs n\u00eb lidhje me Latency t\u00eb mesme dhe IOPS. Sipas parazgjedhjes, 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 \u00ebsht\u00eb paraqitur informacioni mbi n\u00ebnshkall\u00ebn diskore 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 mbi 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> \u2013 \u00ebsht\u00eb numri i disk\u00ebve t\u00eb VM. P\u00ebr t\u00eb shikuar informacionin p\u00ebr \u00e7do disk, shtypni \"e\" dhe 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 p\u00ebr gjetjen e problemeve \u00ebsht\u00eb Disk adapter. Aktivizohet me \u00e7el\u00ebsin \"d\" (n\u00eb figur\u00ebn 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> \u2013 numri i rrug\u00ebve n\u00eb lunat, t\u00eb cilat jan\u00eb t\u00eb dukshme nga ky adaptues. P\u00ebr t\u00eb marr\u00eb informacionin p\u00ebr \u00e7do 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> \u2013 madh\u00ebsia maksimale e radh\u00ebs n\u00eb adaptues.<\/p>\n<p>Po ashtu, n\u00eb k\u00ebt\u00eb ekran jan\u00eb paraqitur hesapet e vonesave, p\u00ebr t\u00eb cilat kam folur m\u00eb sip\u00ebr: <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 mbi pajisjet e ve\u00e7anta bllokuese \u2013 lunat (n\u00eb figur\u00ebn m\u00eb posht\u00eb jan\u00eb zgjedhur fushat A, B, F, G, I). K\u00ebtu mund t\u00eb shihni gjendjen e radh\u00ebs p\u00ebr lunat. <\/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> \u2013 madh\u00ebsia e radh\u00ebs p\u00ebr pajisjen e bllokut.<br \/>\n<b>ACTV<\/b> \u2013 numri i komandave t\u00eb hyrjes\/daljes n\u00eb b\u00ebrtham\u00ebn ESXi.<br \/>\n<b>QUED<\/b> \u2013 numri i komandave t\u00eb hyrjes\/daljes n\u00eb radh\u00eb.<br \/>\n<b>%USD<\/b> \u2013 ACTV \/ DQLEN \u00d7 100%.<br \/>\n<b>LOAD<\/b> \u2013 (ACTV + QUED) \/ DQLEN.<\/p>\n<p>N\u00ebse %USD \u00ebsht\u00eb i lart\u00eb, \u00ebsht\u00eb e arsyeshme t\u00eb shqyrtohet rritja e radh\u00ebs. Sa m\u00eb shum\u00eb komanda t\u00eb jen\u00eb n\u00eb radh\u00eb, aq m\u00eb i lart\u00eb \u00ebsht\u00eb QAVG dhe, p\u00ebr rrjedhoj\u00eb, KAVG.<\/p>\n<p>N\u00eb ekranin Disk device mund t\u00eb kontrolloni n\u00ebse VAAI (vStorage API for Array Integration) funksionon n\u00eb SHK. P\u00ebr k\u00ebt\u00eb, duhet t\u00eb zgjidhni fushat A dhe O. <\/p>\n<p>Mekanizmi VAAI lejon q\u00eb t\u00eb transferohet nj\u00eb pjes\u00eb e pun\u00ebs nga hipervizori direkt n\u00eb SHK, p\u00ebr shembull, zerozimi, kopjimi i blloqeve ose bllokimi.<\/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 e m\u00ebsip\u00ebrm, n\u00eb k\u00ebt\u00eb SHK VAAI funksionon: p\u00ebrdoren aktivisht primitiv\u00ebt Zero dhe ATS.<\/p>\n<h3>K\u00ebshilla p\u00ebr optimizimin e pun\u00ebs me n\u00ebn sistemin e disks 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 datastoret.<\/li>\n<li>Zgjidhni PSP n\u00eb p\u00ebrputhje me rekomandimet e prodhuesit t\u00eb SHK.<\/li>\n<li>Sigurohuni q\u00eb VAAI t\u00eb funksionoj\u00eb.<\/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.2 - 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\/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.2\" \/>\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: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":"","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: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}]}}