{"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\/da\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","title":{"rendered":"Analyse af VM-ydeevne i VMware vSphere. Del 3: Lagring","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Analyse af VM-ydeevne i VMware vSphere. Del 3: Lagring\" 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\/\">Del 1. Om CPU<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/455820\/\">Del 2. Om Hukommelse<\/a><\/noindex><\/p>\n<p>I dag vil vi se n\u00e6rmere p\u00e5 metrics for disksystemet i vSphere. Problemer med lagring er den mest almindelige \u00e5rsag til en langsom virtuel maskine. Hvis vi i tilf\u00e6lde af CPU og RAM slutter fejlfindingen p\u00e5 hypervisorens niveau, s\u00e5 skal vi ved problemer med disken m\u00e5ske ogs\u00e5 se p\u00e5 netv\u00e6rket for datatransmission og lagringssystemet.<\/p>\n<p>Jeg vil tage emnet op ved at give et eksempel p\u00e5 blokadgang til lagringssystemet, selvom t\u00e6llerne er cirka de samme ved filadgang.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Lidt teori<\/h3>\n<p>\nN\u00e5r man taler om ydeevnen af disksystemet til virtuelle maskiner, fokuserer man typisk p\u00e5 tre relaterede parametre:<\/p>\n<ul>\n<li>antal input\/output operationer pr. sekund (Input\/Output Operations Per Second, IOPS);<\/li>\n<li>b\u00e5ndbredde (Throughput);<\/li>\n<li>forsinkelse af input\/output operationer (Latency).<\/li>\n<\/ul>\n<p>\n<b>Antallet af IOPS<\/b> er s\u00e6rligt vigtigt for belastninger af tilf\u00e6ldig karakter (random): adgang til blokke p\u00e5 disken, der er placeret forskellige steder. Eksempler p\u00e5 s\u00e5dan belastning kan v\u00e6re databaser, forretningsapplikationer (ERP, CRM) osv.<\/p>\n<p><b>B\u00e5ndbredde<\/b> er vigtig for belastninger af sekventiel karakter: adgang til blokke, der er placeret efter hinanden. For eksempel kan s\u00e5dan belastning genereres af filservere (men ikke altid) og overv\u00e5gningssystemer.<\/p>\n<p>B\u00e5ndbredden er relateret til antallet af input\/output operationer som f\u00f8lger:<\/p>\n<p><i>Throughput = IOPS * Blokst\u00f8rrelse<\/i>, hvor Blokst\u00f8rrelse er st\u00f8rrelsen p\u00e5 blokken.<\/p>\n<p>Blokst\u00f8rrelsen er en ret vigtig egenskab. Moderne versioner af ESXi tillader blokke op til 32.767 KB. Hvis blokken er endnu st\u00f8rre, deles den op i flere. Ikke alle lagringssystemer kan effektivt h\u00e5ndtere s\u00e5 store blokke, s\u00e5 i Advanced Settings i ESXi findes parameteren DiskMaxIOSize. Denne kan bruges til at reducere den maksimale blokst\u00f8rrelse, som hypervisoren tillader (l\u00e6s mere <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1003469\">her<\/a><\/noindex>). Jeg anbefaler at konsultere producenten af lagringssystemet, f\u00f8r dette parameter \u00e6ndres, eller i det mindste at teste \u00e6ndringerne p\u00e5 et laboratorium.\u00a0<\/p>\n<p>En stor blokst\u00f8rrelse kan have en negativ indvirkning p\u00e5 ydeevnen af lagringssystemet. Selv hvis antallet af IOPS og throughput er relativt lavt, kan der ved store blokke observeres h\u00f8je forsinkelser. S\u00e5 v\u00e6r opm\u00e6rksom p\u00e5 denne parameter.<\/p>\n<p><b>Forsinkelse<\/b> er den mest interessante parameter for ydeevnen. Forsinkelsen af input\/output operationer for den virtuelle maskine best\u00e5r af:<\/p>\n<ul>\n<li>forsinkelsen inden i hypervisoren (KAVG, Average Kernel MilliSec\/Read);<\/li>\n<li>forsinkelse, som dataoverf\u00f8rselsnetv\u00e6rket og storage systemet giver (DAVG, Gennemsnitlig Driver MilliSec\/Command).<\/li>\n<\/ul>\n<p>\nDen samlede forsinkelse, der vises i g\u00e6ste-OS'et (GAVG, Gennemsnitlig G\u00e6st MilliSec\/Command), er summen af KAVG og DAVG.<\/p>\n<p>GAVG og DAVG m\u00e5les, mens KAVG beregnes: GAVG\u2013DAVG.<\/p>\n<p><img decoding=\"async\" alt=\"Analyse af VM-ydeevne i VMware vSphere. Del 3: Lagring\" 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>Kilde<\/i><\/a><\/noindex><\/p>\n<p>Lad os se n\u00e6rmere p\u00e5 <b>KAVG<\/b>. Under normale forhold b\u00f8r KAVG tendere mod nul eller i det mindste v\u00e6re meget lavere end DAVG. Den eneste kendte situation, hvor KAVG forventes at v\u00e6re h\u00f8j, er begr\u00e6nsningen p\u00e5 IOPS p\u00e5 VM-diskene. I s\u00e5 fald vil KAVG stige, hvis der fors\u00f8ges at overskride gr\u00e6nsen.<\/p>\n<p>Den mest betydningsfulde komponent af KAVG er QAVG \u2013 ventetid for behandling inden for hypervisoren. De andre komponenter af KAVG er ubetydelige.<\/p>\n<p>K\u00f8en i diskadapterdriveren og k\u00f8en til lunene har en fast st\u00f8rrelse. For meget belastede milj\u00f8er kan det v\u00e6re nyttigt at \u00f8ge denne st\u00f8rrelse. <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1267\">Her<\/a><\/noindex> beskriver, hvordan man \u00f8ger k\u00f8erne i adapterdriveren (k\u00f8en til lunene vil ogs\u00e5 blive \u00f8get). Denne indstilling fungerer, n\u00e5r der kun er \u00e9n VM, der arbejder med en lun, hvilket sj\u00e6ldent er tilf\u00e6ldet. Hvis der er flere VMer p\u00e5 lunen, skal parameteren <i>Disk.SchedNumReqOutstanding<\/i> (instruktionen\u00a0 <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/1268\">her<\/a><\/noindex>). Ved at \u00f8ge k\u00f8en reducerer du QAVG og KAVG tilsvarende.<\/p>\n<p>Men igen, s\u00f8rg for f\u00f8rst at l\u00e6se dokumentationen fra HBA-udbyderen og teste \u00e6ndringerne p\u00e5 et laboratoriemilj\u00f8. <\/p>\n<p>K\u00f8ens st\u00f8rrelse til lunen kan p\u00e5virkes af aktiveringen af SIOC-mekanismen (Storage I\/O Control). Den sikrer j\u00e6vn adgang til lunen fra alle servere i klyngen ved dynamisk at \u00e6ndre k\u00f8en til lunen p\u00e5 serverne. Det vil sige, hvis en VM p\u00e5 en af v\u00e6rterne kr\u00e6ver uforholdsm\u00e6ssigt meget ydeevne (noisy neighbor VM), reducerer SIOC l\u00e6ngden af k\u00f8en til lunen p\u00e5 den p\u00e5g\u00e6ldende v\u00e6rt (DQLEN). L\u00e6s mere <noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2019\/03\/05\/dqlen-changes-what-is-going-on\/\">her<\/a><\/noindex>.<\/p>\n<p>Vi har styr p\u00e5 KAVG, nu lidt om <b>DAVG<\/b>. Her er det enkelt: DAVG er den forsinkelse, som det eksterne milj\u00f8 (dataoverf\u00f8rselsnetv\u00e6rk og storage system) medf\u00f8rer. I enhver moderne og mindre moderne storage har man sine pr\u00e6stationsm\u00e5linger. For at analysere problemer med DAVG giver det mening at se p\u00e5 dem. Hvis alt er i orden fra ESXi og storage, s\u00e5 tjek netv\u00e6rket.<\/p>\n<p>For optimal performance, choose the right Path Selection Policy (PSP) for your storage system. Almost all modern storage systems support the Round-Robin PSP (with ALUA, Asymmetric Logical Unit Access, or without it). This policy allows the use of all available paths to the storage system. In the case of ALUA, only the paths to the controller that owns the LUN are used. Not all storage systems on ESXi have default rules that set the Round-Robin policy. If your storage system lacks these rules, use the vendor\u2019s plugin to create the appropriate rule across all cluster hosts, or create the rule yourself. Details <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2053628\">her<\/a><\/noindex>.\u00a0<\/p>\n<p>Some storage system manufacturers also recommend changing the IOPS count per path from the standard value of 1000 to 1. In our experience, this has allowed us to 'squeeze' more performance from the storage system and significantly reduce the time required for failover in the event of controller failure or upgrade. Check with the vendor's recommendations, and if there are no contraindications, try changing this parameter. Details <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2069356\">her<\/a><\/noindex>.<\/p>\n<h3>Key performance counters for the virtual machine\u2019s disk subsystem<\/h3>\n<p>\nThe performance counters for the disk subsystem in vCenter are assembled in the Datastore, Disk, Virtual Disk sections:<\/p>\n<p><img decoding=\"async\" alt=\"Analyse af VM-ydeevne i VMware vSphere. Del 3: Lagring\" src=\"\/wp-content\/uploads\/2019\/07\/ae852a6a128914a7aff36f461c5f0721.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n <br \/>\nI sektionen <b>Datastore<\/b> contains metrics for vSphere disk storages (datastores) where the VMs' disks are located. Here you will find standard counters for:<\/p>\n<ul>\n<li>IOPS (Average read\/write requests per second),\u00a0<\/li>\n<li>throughput (Read\/Write rate),\u00a0<\/li>\n<li>latency (Read\/Write\/Highest latency).<\/li>\n<\/ul>\n<p>\nThe names of the counters are quite self-explanatory. I would like to emphasize that the statistics here are not for a specific VM (or VM disk), but general for the entire datastore. In my opinion, this statistics is more conveniently viewed in ESXTOP, particularly since the minimum measurement period there is 2 seconds.<\/p>\n<p>I sektionen <b>Disk<\/b> contains metrics for the block devices used by the VMs. Here, there are summation-type IOPS counters (the number of input\/output operations during the measurement period) and several counters related to block access (Commands aborted, Bus resets). In my opinion, this information is also more conveniently viewed in ESXTOP.<\/p>\n<p>Partition <b>Virtual Disk<\/b> \u2013 den mest nyttige for at identificere ydeevneproblemer i diskundersystemet for VMs. Her kan man se ydeevnen for hver virtuel disk. Denne information er n\u00f8dvendig for at forst\u00e5, om der er et problem med en bestemt virtuel maskine. Udover de standardm\u00e5l for antal input\/output operationer, l\u00e6se-\/skrivevolumen og forsinkelse, findes der nyttige m\u00e5linger i denne sektion, som viser blokst\u00f8rrelsen: L\u00e6se-\/skriveanmodningsst\u00f8rrelse.<\/p>\n<p>P\u00e5 billedet nedenfor er grafen for VM-diskens ydeevne, hvor man kan se antallet af IOPS, forsinkelser og blokst\u00f8rrelse.\u00a0<\/p>\n<p><img decoding=\"async\" alt=\"Analyse af VM-ydeevne i VMware vSphere. Del 3: Lagring\" src=\"\/wp-content\/uploads\/2019\/07\/36d2a4d006d2c1bfd4d9961c745f26b6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nYderligere kan ydeevnemetrikker ogs\u00e5 ses for hele datalageret, hvis SIOC er aktiveret. Her pr\u00e6senteres grundl\u00e6ggende information om gennemsnitlig latens og IOPS. Som standard kan denne information kun ses i realtid.<\/p>\n<p><img decoding=\"async\" alt=\"Analyse af VM-ydeevne i VMware vSphere. Del 3: Lagring\" src=\"\/wp-content\/uploads\/2019\/07\/7872dd131008dfdae09141553b4e42f6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>ESXTOP<\/h3>\n<p>\nI ESXTOP er der flere sk\u00e6rme, der pr\u00e6senterer information om hostens diskundersystem generelt, specifikke virtuelle maskiner og deres diske.<\/p>\n<p>Lad os starte med informationen om de virtuelle maskiner. Sk\u00e6rmen \"Disk VM\" aktiveres med tasten \"v\":<\/p>\n<p><img decoding=\"async\" alt=\"Analyse af VM-ydeevne i VMware vSphere. Del 3: Lagring\" src=\"\/wp-content\/uploads\/2019\/07\/793273e19fca1e4f19b96204202019fb.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>NVDISK<\/b> \u2013 antallet af diske for VM. For at se information om hver disk, tryk \"e\" og indtast GID for den \u00f8nskede VM.<\/p>\n<p>V\u00e6rdien af de andre parametre p\u00e5 denne sk\u00e6rm er tydelig ud fra deres navne.<\/p>\n<p>En anden nyttig sk\u00e6rm til at finde problemer er Disk adapter. Den aktiveres med tasten \"d\" (p\u00e5 billedet nedenfor er felterne A, B, C, D, E, G valgt):<\/p>\n<p><img decoding=\"async\" alt=\"Analyse af VM-ydeevne i VMware vSphere. Del 3: Lagring\" src=\"\/wp-content\/uploads\/2019\/07\/71a7f1e3f1e40f3dbacf61385a3c07cc.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>NPTH<\/b> \u2013 antallet af stier til lunerne, der kan ses fra denne adapter. For at f\u00e5 information om hver sti p\u00e5 adapteren, tryk \"e\" og indtast navnet p\u00e5 adapteren:<\/p>\n<p><img decoding=\"async\" alt=\"Analyse af VM-ydeevne i VMware vSphere. Del 3: Lagring\" src=\"\/wp-content\/uploads\/2019\/07\/12661003ce8be542ed4c5e262da77d90.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>AQLEN<\/b> \u2013 maksimal st\u00f8rrelse af k\u00f8en p\u00e5 adapteren.<\/p>\n<p>P\u00e5 denne sk\u00e6rm er der ogs\u00e5 m\u00e5linger for forsinkelser, som jeg tidligere har n\u00e6vnt: <b>KAVG\/cmd, GAVG\/cmd, DAVG\/cmd, QAVG\/cmd<\/b>. <\/p>\n<p>P\u00e5 sk\u00e6rmen Disk device, som aktiveres med tasten \"u\", pr\u00e6senteres information om individuelle blokenheder \u2013 lunerne (p\u00e5 billedet nedenfor er felterne A, B, F, G, I valgt). Her kan man se tilstanden p\u00e5 k\u00f8en til lunerne. <\/p>\n<p><img decoding=\"async\" alt=\"Analyse af VM-ydeevne i VMware vSphere. Del 3: Lagring\" src=\"\/wp-content\/uploads\/2019\/07\/6331ee64398fe7057c0eec015165f0a5.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>DQLEN<\/b> \u2013 st\u00f8rrelsen p\u00e5 k\u00f8en for blokenheden.<br \/>\n<b>ACTV<\/b> \u2013 antallet af input\/output kommandoer i kernen af ESXi.<br \/>\n<b>QUED<\/b> \u2013 antallet af input\/output kommandoer i k\u00f8en.<br \/>\n<b>%USD<\/b> \u2013 ACTV \/ DQLEN \u00d7 100%.<br \/>\n<b>LOAD<\/b> \u2013 (ACTV + QUED) \/ DQLEN.<\/p>\n<p>Hvis %USD er h\u00f8jt, b\u00f8r man overveje muligheden for at \u00f8ge k\u00f8en. Jo flere kommandoer i k\u00f8en, desto h\u00f8jere er QAVG, og derfor KAVG.<\/p>\n<p>P\u00e5 sk\u00e6rmen for disk enheden kan du se, om VAAI (vStorage API for Array Integration) fungerer p\u00e5 SAN'en. For at g\u00f8re dette skal du v\u00e6lge felterne A og O. <\/p>\n<p>VAAI-mekanismen g\u00f8r det muligt at flytte noget af arbejdet fra hypervisoren direkte til SAN'en, for eksempel nulstilling, blokkopiering eller l\u00e5sning.<\/p>\n<p><img decoding=\"async\" alt=\"Analyse af VM-ydeevne i VMware vSphere. Del 3: Lagring\" src=\"\/wp-content\/uploads\/2019\/07\/131342d74e69af9c0898a1b350e883c8.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nSom vist p\u00e5 billedet ovenfor, fungerer VAAI p\u00e5 denne SAN: primitivere som Zero og ATS bruges aktivt.<\/p>\n<h3>Tips til at optimere arbejdet med disk subsystemet p\u00e5 ESXi.<\/h3>\n<p><\/p>\n<ul>\n<li>V\u00e6r opm\u00e6rksom p\u00e5 blokst\u00f8rrelsen.<\/li>\n<li>Indstil den optimale k\u00f8st\u00f8rrelse p\u00e5 HBA.<\/li>\n<li>Glem ikke at aktivere SIOC p\u00e5 datastores.<\/li>\n<li>V\u00e6lg PSP i overensstemmelse med producentens anbefalinger for SAN.<\/li>\n<li>S\u00f8rg for, at VAAI fungerer.<\/li>\n<\/ul>\n<p>\n<b class=\"spoiler_title\">Nyttige artikler om emnet:<\/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>Kilde: <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.3 - 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\/da\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\n\t\t<meta property=\"og:locale\" content=\"da_DK\" \/>\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\/da\/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\udd47Analyse af VM-ydeevne i VMware vSphere. Del 3: Storage | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/da\/blog\/administrirovanie\/analiz-proizvoditelnosti-vm-v-vmware-vsphere-chast-3-storage","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"da_DK","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\/da\/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\/da\/wp-json\/wp\/v2\/posts\/36486","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/comments?post=36486"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/posts\/36486\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/media\/27306"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/media?parent=36486"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/categories?post=36486"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/da\/wp-json\/wp\/v2\/tags?post=36486"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}