{"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\/ro\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","title":{"rendered":"Analiza performan\u021bei VM \u00een VMware vSphere. Partea 3: Stocare","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Analiza performan\u021bei VM \u00een VMware vSphere. Partea 3: Stocare\" 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\/\">Partea 1. Despre CPU<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/455820\/\">Partea 2. Despre Memorie<\/a><\/noindex><\/p>\n<p>Ast\u0103zi vom analiza metricile subsistemului de stocare \u00een vSphere. Problema cu stocarea este cea mai frecvent\u0103 cauz\u0103 a func\u021bion\u0103rii lente a ma\u0219inii virtuale. Dac\u0103 \u00een cazul CPU \u0219i RAM, depanarea se finalizeaz\u0103 la nivelul hypervisorului, \u00een cazul problemelor cu discul, este posibil s\u0103 fie nevoie s\u0103 analiz\u0103m re\u021beaua de transfer de date \u0219i sistemul de stocare conectat.<\/p>\n<p>Tematica va fi discutat\u0103 pe baza accesului bloc la sistemul de stocare conectat, de\u0219i \u00een cazul accesului pe fi\u0219iere, contoarele sunt aproximativ acelea\u0219i.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Pu\u021bin\u0103 teorie<\/h3>\n<p>\nAtunci c\u00e2nd se vorbe\u0219te despre performan\u021ba subsistemului de stocare al ma\u0219inilor virtuale, de obicei se acord\u0103 aten\u021bie la trei parametri interconecta\u021bi:<\/p>\n<ul>\n<li>num\u0103rul de opera\u021biuni de intrare\/ie\u0219ire (Input\/Output Operations Per Second, IOPS);<\/li>\n<li>l\u0103\u021bimea de band\u0103 (Throughput);<\/li>\n<li>\u00eent\u00e2rzierea opera\u021biunilor de intrare\/ie\u0219ire (Latency).<\/li>\n<\/ul>\n<p>\n<b>Num\u0103rul de IOPS<\/b> este de obicei important pentru sarcini de caracter aleatoriu (random): accesul la blocuri pe disc, aflate \u00een locuri diferite. Un exemplu de astfel de sarcin\u0103 ar putea fi bazele de date, aplica\u021biile de afaceri (ERP, CRM) etc.<\/p>\n<p><b>L\u0103\u021bimea de band\u0103<\/b> este important\u0103 pentru sarcini de caracter secven\u021bial: accesul la blocuri, aflate unele dup\u0103 altele. De exemplu, o astfel de sarcin\u0103 ar putea fi generat\u0103 de servere de fi\u0219iere (dar nu \u00eentotdeauna) \u0219i sistemele de supraveghere video.<\/p>\n<p>L\u0103\u021bimea de band\u0103 este legat\u0103 de num\u0103rul de opera\u021biuni de intrare\/ie\u0219ire \u00een felul urm\u0103tor:<\/p>\n<p><i>Throughput = IOPS * Dimensiunea blocului<\/i>, unde Dimensiunea blocului este dimensiunea blocului.<\/p>\n<p>Dimensiunea blocului este o caracteristic\u0103 destul de important\u0103. Versiunile moderne de ESXi permit blocuri de dimensiuni de p\u00e2n\u0103 la 32.767 KB. Dac\u0103 blocul este \u0219i mai mare, acesta este \u00eemp\u0103r\u021bit \u00een mai multe. Nu toate sistemele de stocare conectate pot func\u021biona eficient cu astfel de blocuri mari, de aceea \u00een Set\u0103rile Avansate ale ESXi exist\u0103 un parametru DiskMaxIOSize. Acesta poate reduce dimensiunea maxim\u0103 a blocului permis de hypervisor (mai multe detalii <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1003469\">aici<\/a><\/noindex>). Recomand s\u0103 consulta\u021bi produc\u0103torul sistemului de stocare conectat \u00eenainte de a modifica acest parametru sau, m\u0103car, s\u0103 testa\u021bi modific\u0103rile pe un stand de laborator.\u00a0<\/p>\n<p>O dimensiune mare a blocului poate afecta negativ performan\u021ba sistemului de stocare conectat. Chiar \u0219i \u00een cazul \u00een care num\u0103rul de IOPS \u0219i throughput este relativ mic, la o dimensiune mare a blocului pot ap\u0103rea \u00eent\u00e2rzieri ridicate. A\u0219adar, acorda\u021bi aten\u021bie acestui parametru.<\/p>\n<p><b>\u00cent\u00e2rzierea<\/b> este cel mai interesant parametru de performan\u021b\u0103. \u00cent\u00e2rzierea opera\u021biunilor de intrare\/ie\u0219ire pentru o ma\u0219in\u0103 virtual\u0103 este compus\u0103 din:<\/p>\n<ul>\n<li>\u00eent\u00e2rzierile din interiorul hipervizorului (KAVG, Milisecunde medii ale kernelului \/ Citire);<\/li>\n<li>\u00eent\u00e2rzierile cauzate de re\u021beaua de transfer de date \u0219i de sistemul de stocare (DAVG, Milisecunde medii ale driverului \/ Comand\u0103).<\/li>\n<\/ul>\n<p>\n\u00cent\u00e2rziera total\u0103, care este vizibil\u0103 \u00een sistemul de operare guest (GAVG, Milisecunde medii ale guest-ului \/ Comand\u0103), este suma KAVG \u0219i DAVG.<\/p>\n<p>GAVG \u0219i DAVG sunt m\u0103surate, iar KAVG este calculat: GAVG\u2013DAVG.<\/p>\n<p><img decoding=\"async\" alt=\"Analiza performan\u021bei VM \u00een VMware vSphere. Partea 3: Stocare\" 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>Sursa<\/i><\/a><\/noindex><\/p>\n<p>S\u0103 ne oprim pu\u021bin asupra <b>KAVG<\/b>. \u00cen mod normal, KAVG ar trebui s\u0103 tind\u0103 spre zero sau, cel pu\u021bin, s\u0103 fie semnificativ mai mic dec\u00e2t DAVG. Singurul caz cunoscut mie c\u00e2nd KAVG este a\u0219teptat a fi ridicat este restric\u021bia de IOPS pe discurile VM-ului. \u00cen acest caz, atunci c\u00e2nd se \u00eencearc\u0103 dep\u0103\u0219irea limitei, KAVG va cre\u0219te.<\/p>\n<p>Cea mai semnificativ\u0103 component\u0103 a KAVG este QAVG \u2013 timpul de a\u0219teptare pentru procesare \u00een interiorul hipervizorului. Celelalte componente ale KAVG sunt neglijabile.<\/p>\n<p>Coada din driverul adaptorului de disc \u0219i cozi c\u0103tre lun\u0103 au o dimensiune fix\u0103. Pentru medii cu sarcini mari, aceast\u0103 dimensiune poate fi util s\u0103 fie m\u0103rit\u0103. <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1267\">Aici<\/a><\/noindex> Este descris cum s\u0103 creasc\u0103 cozile \u00een driverul adaptorului (\u00eempreun\u0103 cu cre\u0219terea cozii c\u0103tre lun\u0103). Aceast\u0103 setare func\u021bioneaz\u0103 atunci c\u00e2nd o singur\u0103 VM lucreaz\u0103 cu lun\u0103, ceea ce este rar. Dac\u0103 la lun\u0103 sunt mai multe VM-uri, trebuie s\u0103 cre\u0219te\u021bi \u0219i parametrul <i>Disk.SchedNumReqOutstanding<\/i> (instruc\u021biune\u00a0 <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1268\">aici<\/a><\/noindex>). M\u0103rind coada, reduce\u021bi QAVG \u0219i KAVG \u00een mod corespunz\u0103tor.<\/p>\n<p>Dar, din nou, mai \u00eent\u00e2i consultati documenta\u021bia de la furnizorul HBA \u0219i testa\u021bi modific\u0103rile pe un mediu de laborator. <\/p>\n<p>Dimensiunea coada c\u0103tre lun\u0103 poate fi influen\u021bat\u0103 de activarea mecanismului SIOC (Controlul I\/O de Stocare). Acesta asigur\u0103 un acces uniform la lun\u0103 din partea tuturor serverelor din cluster prin modificarea dinamic\u0103 a cozii c\u0103tre lun\u0103 pe servere. Cu alte cuvinte, dac\u0103 pe vreunul din gazde func\u021bioneaz\u0103 o VM care necesit\u0103 o putere dispropor\u021bionat\u0103 de procesare (VM zgomotoas\u0103), SIOC reduce lungimea cozii c\u0103tre lun\u0103 pe acea gazd\u0103 (DQLEN). Mai multe detalii <noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2019\/03\/05\/dqlen-changes-what-is-going-on\/\">aici<\/a><\/noindex>.<\/p>\n<p>Cu KAVG am \u00een\u021beles, acum pu\u021bin despre <b>DAVG<\/b>. Aici totul este simplu: DAVG este \u00eent\u00e2rziera impus\u0103 de mediu (re\u021beaua de transfer de date \u0219i sistemul de stocare). \u00cen orice sistem de stocare modern \u0219i nu foarte modern exist\u0103 propriile contoare de performan\u021b\u0103. Pentru analiza problemelor cu DAVG, are sens s\u0103 v\u0103 uita\u021bi la ele. Dac\u0103 din perspectiva ESXi \u0219i a sistemului de stocare totul este \u00een regul\u0103, verifica\u021bi re\u021beaua de transfer de date.<\/p>\n<p>Pentru a evita problemele de performan\u021b\u0103, alege\u021bi politica corect\u0103 de selec\u021bie a c\u0103ilor (PSP) pentru stocarea dvs. Acest lucru este sus\u021binut de aproape toate stoc\u0103rile moderne, care accept\u0103 PSP Round-Robin (cu ALUA, Acces Logic Asimetric la Unitate, sau f\u0103r\u0103). Aceast\u0103 politic\u0103 permite utilizarea tuturor c\u0103ilor disponibile c\u0103tre stocare. \u00cen cazul ALUA, se utilizeaz\u0103 doar c\u0103ile c\u0103tre controlerul care de\u021bine LUN-ul. Nu toate stoc\u0103rile de pe ESXi au reguli implicite care stabilesc politica Round-Robin. Dac\u0103 nu exist\u0103 reguli pentru stocarea dvs., utiliza\u021bi pluginul de la furnizorul stoc\u0103rii care va crea regula corespunz\u0103toare pe toate gazdele clusterei sau crea\u021bi regula singuri. Detalii <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2053628\">aici<\/a><\/noindex>.\u00a0<\/p>\n<p>De asemenea, o parte dintre furnizorii de stocare recomand\u0103 schimbarea num\u0103rului de IOPS pe cale din valoarea standard de 1000 la 1. \u00cen practicile noastre, aceasta a permis \u201emaximizarea\u201d performan\u021bei stoc\u0103rii \u0219i a redus semnificativ timpul necesar pentru failover \u00een cazul unei defec\u021biuni sau actualiz\u0103ri a controlerelor. Consulta\u021bi recomand\u0103rile furnizorului \u0219i, dac\u0103 nu sunt contraindica\u021bii, \u00eencerca\u021bi s\u0103 modifica\u021bi acest parametru. Detalii <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2069356\">aici<\/a><\/noindex>.<\/p>\n<h3>Principalele contorii de performan\u021b\u0103 a subsistemului de stocare al ma\u0219inii virtuale<\/h3>\n<p>\nContorii de performan\u021b\u0103 a subsistemului de stocare \u00een vCenter sunt grupa\u021bi \u00een sec\u021biunile Datastore, Disk, Virtual Disk:<\/p>\n<p><img decoding=\"async\" alt=\"Analiza performan\u021bei VM \u00een VMware vSphere. Partea 3: Stocare\" src=\"\/wp-content\/uploads\/2019\/07\/ae852a6a128914a7aff36f461c5f0721.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n <br \/>\n\u00cen sec\u021biune <b>Datastore<\/b> se g\u0103sesc metrici pentru stoc\u0103rile de discuri vSphere (datastoruri), pe care se afl\u0103 discurile VM. Aici ve\u021bi g\u0103si contoare standard pentru:<\/p>\n<ul>\n<li>IOPS (Cereri de citire\/scriere medii pe secund\u0103),\u00a0<\/li>\n<li>l\u0103\u021bimea de band\u0103 (Rata de citire\/scriere),\u00a0<\/li>\n<li>\u00eent\u00e2rzieri (\u00cent\u00e2rzieri de citire\/scriere\/cea mai mare \u00eent\u00e2rzire).<\/li>\n<\/ul>\n<p>\nDin denumirile contorilor, practic totul este clar. Voi sublinia din nou c\u0103 aici statistica nu este pentru o anumit\u0103 VM (sau disc VM), ci una general\u0103 pentru \u00eentregul datastore. Din punctul meu de vedere, aceast\u0103 statistic\u0103 este mai convenabil de vizualizat \u00een ESXTOP, mai ales av\u00e2nd \u00een vedere c\u0103 perioada minim\u0103 de m\u0103surare este de 2 secunde.<\/p>\n<p>\u00cen sec\u021biune <b>Discul<\/b> se g\u0103sesc metrici pentru unit\u0103\u021bile bloc care sunt utilizate de VM. Aici exist\u0103 contoare de tip IOPS summation (num\u0103rul de opera\u021bii de intrare\/ie\u0219ire pe perioada de m\u0103surare) \u0219i c\u00e2teva contoare legate de accesul bloc (Comenzi anulate, Reset\u0103ri de magistral\u0103). Aceast\u0103 informa\u021bie, din punctul meu de vedere, este de asemenea mai convenabil de vizualizat \u00een ESXTOP.<\/p>\n<p>Sec\u021biunea <b>Discul Virtual<\/b> \u2013 cel mai util \u00een ceea ce prive\u0219te identificarea problemelor de performan\u021b\u0103 ale subsistemului de stocare al VM-ului. Aici pute\u021bi vizualiza performan\u021ba fiec\u0103rui disc virtual. Aceast\u0103 informa\u021bie este esen\u021bial\u0103 pentru a \u00een\u021belege dac\u0103 exist\u0103 o problem\u0103 la o anumit\u0103 ma\u0219in\u0103 virtual\u0103. Pe l\u00e2ng\u0103 contorizatorii standard pentru num\u0103rul de opera\u021biuni de citire\/scriere, volumul de date citite\/scrise \u0219i \u00eent\u00e2rzierile, \u00een aceast\u0103 sec\u021biune exist\u0103 contorizatori utili care arat\u0103 dimensiunea blocului: dimensiunea cererilor de citire\/scriere.<\/p>\n<p>\u00cen imaginea de mai jos se afl\u0103 graficul de performan\u021b\u0103 al discului VM, unde pute\u021bi observa num\u0103rul de IOPS, \u00eent\u00e2rzierile \u0219i dimensiunea blocului.\u00a0<\/p>\n<p><img decoding=\"async\" alt=\"Analiza performan\u021bei VM \u00een VMware vSphere. Partea 3: Stocare\" src=\"\/wp-content\/uploads\/2019\/07\/36d2a4d006d2c1bfd4d9961c745f26b6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDe asemenea, metrica de performan\u021b\u0103 poate fi vizualizat\u0103 pe \u00eentregul datastor, dac\u0103 SIOC este activat. Aici sunt prezentate informa\u021bii de baz\u0103 despre Latency medie \u0219i IOPS. \u00cen mod implicit, aceste informa\u021bii pot fi vizualizate doar \u00een timp real.<\/p>\n<p><img decoding=\"async\" alt=\"Analiza performan\u021bei VM \u00een VMware vSphere. Partea 3: Stocare\" src=\"\/wp-content\/uploads\/2019\/07\/7872dd131008dfdae09141553b4e42f6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>ESXTOP<\/h3>\n<p>\n\u00cen ESXTOP exist\u0103 mai multe ecrane care ofer\u0103 informa\u021bii despre subsistemul de stocare al gazdei \u00een ansamblu, pentru ma\u0219ini virtuale specifice \u0219i discurile acestora.<\/p>\n<p>S\u0103 \u00eencepem cu informa\u021biile despre ma\u0219inile virtuale. Ecranul \"Disk VM\" se deschide cu tasta \"v\":<\/p>\n<p><img decoding=\"async\" alt=\"Analiza performan\u021bei VM \u00een VMware vSphere. Partea 3: Stocare\" src=\"\/wp-content\/uploads\/2019\/07\/793273e19fca1e4f19b96204202019fb.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>NVDISK<\/b> \u2013 aceasta este num\u0103rul de discuri ale VM-ului. Pentru a vizualiza informa\u021bii despre fiecare disc, ap\u0103sa\u021bi \"e\" \u0219i introduce\u021bi GID-ul VM-ului de interes.<\/p>\n<p>Valoarea celorlalte parametrii pe acest ecran poate fi \u00een\u021beleas\u0103 din denumirile lor.<\/p>\n<p>Un alt ecran util \u00een caz de c\u0103utare a problemelor \u2013 Disk adapter. Se deschide cu tasta \"d\" (\u00een imaginea de mai jos sunt selectate c\u00e2mpurile A, B, C, D, E, G):<\/p>\n<p><img decoding=\"async\" alt=\"Analiza performan\u021bei VM \u00een VMware vSphere. Partea 3: Stocare\" src=\"\/wp-content\/uploads\/2019\/07\/71a7f1e3f1e40f3dbacf61385a3c07cc.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>NPTH<\/b> \u2013 num\u0103rul de c\u0103i c\u0103tre LUN-uri care sunt vizibile din acest adaptor. Pentru a ob\u021bine informa\u021bii despre fiecare cale de pe adaptor, ap\u0103sa\u021bi \"e\" \u0219i introduce\u021bi denumirea adaptorului:<\/p>\n<p><img decoding=\"async\" alt=\"Analiza performan\u021bei VM \u00een VMware vSphere. Partea 3: Stocare\" src=\"\/wp-content\/uploads\/2019\/07\/12661003ce8be542ed4c5e262da77d90.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>AQLEN<\/b> \u2013 dimensiunea maxim\u0103 a cozii pe adaptor.<\/p>\n<p>De asemenea, pe acest ecran sunt prezenta\u021bi contorizatori pentru \u00eent\u00e2rzierile despre care am vorbit mai sus: <b>KAVG\/cmd, GAVG\/cmd, DAVG\/cmd, QAVG\/cmd<\/b>. <\/p>\n<p>Pe ecranul Disk device, care se deschide cu tasta \"u\", sunt prezentate informa\u021bii despre dispozitivele de blocare individuale \u2013 LUN-uri (\u00een imaginea de mai jos sunt selectate c\u00e2mpurile A, B, F, G, I). Aici pute\u021bi vedea starea cozii c\u0103tre LUN-uri. <\/p>\n<p><img decoding=\"async\" alt=\"Analiza performan\u021bei VM \u00een VMware vSphere. Partea 3: Stocare\" src=\"\/wp-content\/uploads\/2019\/07\/6331ee64398fe7057c0eec015165f0a5.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>DQLEN<\/b> \u2013 dimensiunea cozii pentru dispozitivul de bloc.<br \/>\n<b>ACTV<\/b> \u2013 num\u0103rul de comenzi de citire\/scriere \u00een nucleul ESXi.<br \/>\n<b>QUED<\/b> \u2013 num\u0103rul de comenzi de citire\/scriere \u00een coad\u0103.<br \/>\n<b>%USD<\/b> \u2013 ACTV \/ DQLEN \u00d7 100%.<br \/>\n<b>LOAD<\/b> \u2013 (ACTV + QUED) \/ DQLEN.<\/p>\n<p>Dac\u0103 %USD este ridicat, ar trebui s\u0103 lua\u021bi \u00een considerare posibilitatea de a cre\u0219te coada. Cu c\u00e2t mai multe comenzi sunt \u00een coad\u0103, cu at\u00e2t QAVG este mai mare \u0219i, prin urmare, KAVG.<\/p>\n<p>De asemenea, pe ecranul Dispozitiv de disk se poate observa dac\u0103 VAAI (vStorage API pentru Integrarea Array-ului) func\u021bioneaz\u0103 pe S\u00ceD. Pentru aceasta, trebuie s\u0103 selecta\u021bi c\u00e2mpurile A \u0219i O. <\/p>\n<p>Mecanismul VAAI permite mutarea unei p\u0103r\u021bi din lucru din hypervizor direct pe S\u00ceD, de exemplu, anularea, copierea blocurilor sau bloc\u0103rile.<\/p>\n<p><img decoding=\"async\" alt=\"Analiza performan\u021bei VM \u00een VMware vSphere. Partea 3: Stocare\" src=\"\/wp-content\/uploads\/2019\/07\/131342d74e69af9c0898a1b350e883c8.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDup\u0103 cum se vede \u00een imaginea de mai sus, pe acest S\u00ceD VAAI func\u021bioneaz\u0103: se utilizeaz\u0103 activ primitivele Zero \u0219i ATS.<\/p>\n<h3>Sfaturi pentru optimizarea lucrului cu subsystemul de disc pe ESXi<\/h3>\n<p><\/p>\n<ul>\n<li>Acorda\u021bi aten\u021bie dimensiunii blocului.<\/li>\n<li>Stabili\u021bi dimensiunea optim\u0103 a cozii pe HBA.<\/li>\n<li>Nu uita\u021bi s\u0103 activa\u021bi SIOC pe datastoruri.<\/li>\n<li>Alege\u021bi PSP conform recomand\u0103rilor produc\u0103torului S\u00ceD.<\/li>\n<li>Asigura\u021bi-v\u0103 c\u0103 VAAI func\u021bioneaz\u0103.<\/li>\n<\/ul>\n<p>\n<b class=\"spoiler_title\">Articole utile pe aceast\u0103 tem\u0103:<\/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>Sursa: <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\/ro\/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=\"ro_RO\" \/>\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\/ro\/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 performan\u021bei VM \u00een VMware vSphere. Partea 3: Storage | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\/ro\/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\/ro\/wp-json\/wp\/v2\/posts\/36486","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=36486"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/36486\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/27306"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=36486"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=36486"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=36486"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}