{"id":34335,"date":"2019-10-31T21:57:43","date_gmt":"2019-10-31T18:57:43","guid":{"rendered":"https:\/\/prohoster.info\/blog\/analiz-proizvoditelnosti-virtualnoj-mashiny-v-vmware-vsphere-chast-1-cpu\/"},"modified":"2019-10-31T21:57:43","modified_gmt":"2019-10-31T18:57:43","slug":"analiz-proizvoditelnosti-virtualnoj-mashiny-v-vmware-vsphere-chast-1-cpu","status":"publish","type":"post","link":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/analiz-proizvoditelnosti-virtualnoj-mashiny-v-vmware-vsphere-chast-1-cpu","title":{"rendered":"Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere'is. Osa 1: CPU","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/0c077a1754c2e32c1f339999ceacf03a.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKui haldate virtuaalset infrastruktuuri VMware vSphere'i (v\u00f5i m\u00f5ne muu tehnoloogia virna) baasil, siis olete t\u00f5en\u00e4oliselt kuulnud kasutajatelt sageli kaebusi: \u201eVirtuaalmasin t\u00f6\u00f6tab aeglaselt!\u201c. Selles artiklite sarjas vaatan \u00fcle j\u00f5udlusn\u00e4itajaid ja r\u00e4\u00e4gin, mis ja miks \u201epidurdab\u201c ning kuidas sedasi ei juhtuks.<\/p>\n<p>Kaatlen j\u00e4rgmisi virtuaalmasinate j\u00f5udlusaspekte:<\/p>\n<ul>\n<li>CPU,<\/li>\n<li>RAM,<\/li>\n<li>DISK,<\/li>\n<li>V\u00f5rk.<\/li>\n<\/ul>\n<p>\nAlustan CPU-st.<\/p>\n<p>J\u00f5udluse anal\u00fc\u00fcsiks on meil vaja:<\/p>\n<ul>\n<li><b>vCenter Performance Counters<\/b> \u2013 j\u00f5udlusn\u00e4itajad, mille graafikuid saab vaadata vSphere kliendi kaudu. Teave nende n\u00e4itajate kohta on saadaval k\u00f5igis kliendi versioonides (\u201epaks\u201c klient C#-s, veebiklient Flexis ja veebiklient HTML5-s). Nendes artiklites kasutame ekraanipilte C#-klientist, sest need n\u00e4evad minipildis paremad v\u00e4lja:)<\/li>\n<li><b>ESXTOP<\/b> \u2013 t\u00f6\u00f6riist, mis k\u00e4ivitatakse ESXi k\u00e4surealt. Selle abil saab reaalajas vaadata j\u00f5udlusn\u00e4itajaid v\u00f5i laadida need teatud ajavahemikus .csv-faili edasiste anal\u00fc\u00fcside jaoks. J\u00e4rgmisena r\u00e4\u00e4gin sellest t\u00f6\u00f6riistast l\u00e4hemalt ja jagan mitmeid kasulikke linke dokumentatsioonile ja artiklitele.<\/li>\n<\/ul>\n<p>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Veidi teooriat<\/h3>\n<p>\n<img decoding=\"async\" alt=\"Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/bc415aace7653c45850d26b7104483c9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nESXi-s vastutab iga vCPU (virtuaalmasina tuum) t\u00f6\u00f6 eest eraldi protsess \u2013 world VMware terminoloogias. Samuti on olemas teenusprotsessid, kuid VM-i j\u00f5udluse anal\u00fc\u00fcsi seisukohalt on need v\u00e4hem huvitavad.<\/p>\n<p>Protsess ESXi-s v\u00f5ib olla \u00fches neljast olekust:<\/p>\n<ul>\n<li><b>K\u00e4ita<\/b> \u2013 protsess t\u00e4idab mingit kasulikku t\u00f6\u00f6d.<\/li>\n<li><b>Oota<\/b> \u2013 protsess ei tee mingit t\u00f6\u00f6d (idle) v\u00f5i ootab sisendi\/v\u00e4ljundi j\u00e4rgi.<\/li>\n<li><b>Costop<\/b> \u2013 seisund, mis tekib mitu s\u00fcdamikku sisaldavates virtuaalsetes masinates. See tekib, kui h\u00fcperviisori CPU ajakava (ESXi CPU Scheduler) ei suuda kavandada f\u00fc\u00fcsiliste serveri s\u00fcdamike samalaadset t\u00e4itmist k\u00f5igi aktiivsete virtuaalmasina s\u00fcdamike jaoks. F\u00fc\u00fcsilises maailmas t\u00f6\u00f6tavad k\u00f5ik protsessori s\u00fcdamikud paralleelselt, k\u00fclaline OS virtuaalmasina sees eeldab sarnast k\u00e4itumist, mist\u00f5ttu h\u00fcperviisor on sunnitud aeglustama virtuaalmasina s\u00fcdamikke, millel on v\u00f5imalus oma ts\u00fckli l\u00f5pule viia kiiremini. Kaasaegsetes ESXi versioonides kasutab CPU ajakava mehhanismi, mida nimetatakse relaxed co-scheduling: h\u00fcperviisor arvutab virtuaalmasina k\u00f5ige \u201ekiirema\u201c ja k\u00f5ige \u201eaeglasema\u201c s\u00fcdamiku (skew) vahe. Kui vahe \u00fcletab teatud piiri, muutub \u201ekiire\u201c s\u00fcdamik costop seisundisse. Kui virtuaalmasina s\u00fcdamikud veedavad palju aega selles seisundis, v\u00f5ib see tekitada j\u00f5udlusprobleeme.<\/li>\n<li><b>Valmis<\/b> \u2013 protsess liigub sellesse olekusse, kui h\u00fcperv\u00f5imekusel pole ressursse selle t\u00e4itmiseks. Suured ready v\u00e4\u00e4rtused v\u00f5ivad p\u00f5hjustada j\u00f5udlusprobleeme virtuaalmasinatele.<\/li>\n<\/ul>\n<p><\/p>\n<h3>Virtuaalmasina CPU j\u00f5udluse p\u00f5hikl\u00f6rid<\/h3>\n<p>\n<b>CPU Kasutus, %.<\/b> N\u00e4itab CPU kasutusprotsenti antud ajavahemiku jooksul.<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/7a5da7dcd45329c3aae8e394c5d35a30.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Kuidas anal\u00fc\u00fcsida?<\/b> Kui virtuaalmasin kasutab stabiilselt CPU-d 90% ulatuses v\u00f5i on harva 100% ulatuses, siis on meil probleem. Probleemid v\u00f5ivad avalduda mitte ainult virtuaalmasina sees oleva rakenduse \u201eaeglasena\u201c t\u00f6\u00f6tamises, vaid ka virtuaalmasina v\u00f5rgus puudumises. Kui j\u00e4lgimis\u00fcsteem n\u00e4itab, et virtuaalmasin katkeb perioodiliselt, p\u00f6\u00f6rake t\u00e4helepanu CPU Kasutuse graafiku t\u00f5usudele.<\/p>\n<p>On olemas standardne alarm, mis n\u00e4itab virtuaalmasina CPU koormust:<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/9bfd9bb5b43b9b02e8bbfac307d6c9f9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Mida teha?<\/b> Kui virtuaalmasina CPU Kasutus \u00fcletab pidevalt lubatud piire, tasub m\u00f5elda vCPU arvu suurendamisele (kahjuks ei aita see alati) v\u00f5i virtuaalmasina paigutamisele teadlikumate protsessoritega serverisse.<\/p>\n<h3>CPU Kasutus Mhz-des<\/h3>\n<p>\nvCenteris saab vaadata kasutatavust % ulatuses ainult kogu virtuaalmasina kohta, eraldi tuumade graafikuid ei ole (Esxtop n\u00e4itab protsentides tuumade v\u00e4\u00e4rtusi). Iga tuuma kohta saab vaadata Kasutust Mhz-des.<\/p>\n<p><b>Kuidas anal\u00fc\u00fcsida?<\/b> Occasionally, an application may not be optimized for a multi-core architecture: it uses only one core at 100%, while the others remain idle. For example, with default MS SQL backup settings, the process runs on just one core. As a result, the backup slows down not because of slow disk speeds (which is what the user initially complained about), but because the processor is overwhelmed. The issue was resolved by changing the parameters: backups began to run concurrently in multiple files (and consequently in several processes).<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/d1bce5fe5ef89a69c31a6a8f043d5d24.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Example of uneven core load.<\/i><\/p>\n<p>There can also be a situation (as shown in the above graph) where the cores are unevenly loaded, with some experiencing peaks of 100%. Just like when only one core is loaded, the CPU Usage alarm won't trigger (since it is for the entire VM), but performance issues will arise.<\/p>\n<p><b>Mida teha? <\/b>If the software in the virtual machine unevenly stresses the cores (using only one core or some cores), increasing their number is pointless. In this case, it's better to move the VM to a server with more powerful processors.<\/p>\n<p>You might also want to check the power settings in the server's BIOS. Many administrators enable the High Performance mode in BIOS, thereby disabling the energy-saving technologies C-states and P-states. Modern Intel processors employ Turbo Boost technology, which increases the frequency of individual processor cores at the expense of others. However, it only works when power-saving technologies are enabled. If we disable them, the processor cannot reduce the energy consumption of the cores that are not under load. <\/p>\n<p>VMware recommends not disabling energy-saving technologies on servers, but rather selecting modes that give the hypervisor maximum control over power consumption. In the hypervisor's power settings, it is necessary to choose High Performance. <\/p>\n<p>If you have separate VMs (or VM cores) in your infrastructure that require an increased CPU frequency, correctly configuring the power consumption can significantly improve their performance.<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/59aec2b77fa87e413d90371a11388629.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>CPU Ready (Readiness) <\/h3>\n<p>\nKui VM-i tuum (vCPU) on valmisoleku olekus, ei tee see kasulikku t\u00f6\u00f6d. See olek tekib siis, kui h\u00fcperviisor ei leia vabast f\u00fc\u00fcsilisest tuumast, kuhu saaks m\u00e4\u00e4rata vCPU protsessi virtuaalmasinas.<\/p>\n<p><b>Kuidas anal\u00fc\u00fcsida?<\/b> Tavaliselt, kui virtuaalmasina tuumad on valmisoleku olekus \u00fcle 10% ajast, m\u00e4rkate j\u00f5udlusprobleeme. Lihtsamalt \u00f6eldes ootab virtuaalmasin rohkem kui 10% ajast f\u00fc\u00fcsiliste ressursside k\u00e4ttesaadavust.<\/p>\n<p>vCenteris saab vaadata 2 m\u00f5\u00f5dikute arvu, mis on seotud CPU Ready-ga:<\/p>\n<ul>\n<li>Valmidus,<\/li>\n<li>Valmis.<\/li>\n<\/ul>\n<p>\nM\u00f5lema m\u00f5\u00f5dikute v\u00e4\u00e4rtusi saab vaadata nii kogu VM-i kohta kui ka eraldi tuumade kohta.<br \/>\nValmidus n\u00e4itab v\u00e4\u00e4rtust kohe protsentides, kuid ainult reaalajas (andmed viimase tunni jooksul, m\u00f5\u00f5tmisvahemaa 20 sekundit). Seda m\u00f5\u00f5dikut on parem kasutada ainult probleemide tuvastamiseks \"kuumadel j\u00e4lgedel\".<\/p>\n<p>Ready m\u00f5\u00f5dikute v\u00e4\u00e4rtusi saab vaadata ka ajalises perspektiivis. See on kasulik mustrite m\u00e4\u00e4ramiseks ja probleemi s\u00fcgavamaks anal\u00fc\u00fcsimiseks. N\u00e4iteks, kui virtuaalmasinaga tekivad j\u00f5udlusprobleemid kindlal ajal, saab v\u00f5rrelda t\u00f5stetud CPU Ready v\u00e4\u00e4rtuse vahemaid serveri \u00fcldise koormusega, kus see VM t\u00f6\u00f6tab, ja v\u00f5tta meetmeid koormuse v\u00e4hendamiseks (kui DRS ei ole toime tulnud).<\/p>\n<p>Ready, erinevalt Valmidusest, ei n\u00e4idata protsentides, vaid millisekundites. See on summatsioonimeeter, mis t\u00e4hendab, et see n\u00e4itab, kui kaua oli VM-i tuum m\u00f5\u00f5tmise perioodi jooksul valmisoleku olekus. Selle v\u00e4\u00e4rtuse protsentideks t\u00f5lgendamiseks v\u00f5ib kasutada lihtsat valemit:<\/p>\n<p>(CPU ready summation value \/ (chart default update interval in seconds * 1000)) * 100 = CPU ready %<\/p>\n<p>N\u00e4iteks virtuaalmasina jaoks j\u00e4rgnevas graafikus on k\u00f5rgeim Ready v\u00e4\u00e4rtus j\u00e4rgmine: <\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/3e2df8bca55b572502d88b838cbc306e.jpg\" style=\"display:block;margin: 0 auto;\" \/> <\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/f0371c9cd655c1e4785e90debde61dc8.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nReady v\u00e4\u00e4rtuste protsentide arvutamisel tasub t\u00e4helepanu p\u00f6\u00f6rata kahele asjaolule:<\/p>\n<ul>\n<li>Valmis v\u00e4\u00e4rtus kogu VM-i kohta on tuumade j\u00e4rgi Ready v\u00e4\u00e4rtuste summa.<\/li>\n<li>M\u00f5\u00f5tmisvahemaa. Reaalajas \u2013 see on 20 sekundit, kuid n\u00e4iteks p\u00e4evagraafikutes \u2013 see on 300 sekundit.<\/li>\n<\/ul>\n<p>\nT\u00f6\u00f6tamise ajal v\u00f5ib neid lihtsaid asjaolusid kergesti t\u00e4helepanuta j\u00e4tta ning kulutada v\u00e4\u00e4rtuslikku aega mitteeksisteerivate probleemide lahendamisele. <\/p>\n<p>Kalkuleerime Ready andmete alusel allolevalt graafikult. (324474\/(20*1000))*100 = 1622% tervele VM-ile. Kui vaadata tuumade kaupa, ei paista see enam nii kohutav: 1622\/64 = 25% tuuma kohta. Antud juhul on petliku v\u00e4\u00e4rtuse leidmine \u00fcsna lihtne: Ready v\u00e4\u00e4rtus on ebarealistlik. Kuid kui jutt on 10\u201320% tervele VM-ile mitme tuumaga, v\u00f5ivad iga tuuma v\u00e4\u00e4rtused olla normaalses vahemikus.<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/703ab2b1f1fab8bda10aad781c2cef78.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Mida teha? <\/b>K\u00f5rge Ready v\u00e4\u00e4rtus n\u00e4itab, et serveril ei ole virtuaalmasinate normaalseks t\u00f6\u00f6ks piisavalt protsessoriv\u00f5imsust. Sellises olukorras j\u00e4\u00e4b \u00fcle vaid v\u00e4hendada protsessori \u00fclepakkumist (vCPU:pCPU). Ilmselgelt on seda v\u00f5imalik saavutada olemasolevate VM-ide seadete v\u00e4hendamisega v\u00f5i osa VM-ide migreerimisega teistele serveritele.<\/p>\n<h3>Co-stop<\/h3>\n<p>\n<b>Kuidas anal\u00fc\u00fcsida?<\/b> Seda loenduri t\u00fc\u00fcpi nimetatakse samuti Summation ja see t\u00f5lgitakse protsentideks sarnaselt Ready-ga:<\/p>\n<p>(CPU co-stop summation value \/ (graafiku vaikeseadistuse uuendamise intervall sekundites * 1000)) * 100 = CPU co-stop %<\/p>\n<p>Siin tuleb samuti t\u00e4helepanu p\u00f6\u00f6rata tuumade arvule VM-is ja m\u00f5\u00f5tmise intervallile.<br \/>\nCo-stop olekus tuum ei tee kasulikku t\u00f6\u00f6d. \u00d5ige VM-i suuruse valiku ja serveri normaalse koormuse korral peaks co-stop loendur olema l\u00e4hedal nullile.<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/e226afbf91155c2d5d3fdc4571e7383a.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Antud juhul on koormus selgelt ebanormaalne :)<\/i><\/p>\n<p><b>Mida teha?<\/b> Kui \u00fchel h\u00fcperviisoril t\u00f6\u00f6tab mitu VM-i suure hulga tuumadega ja on CPU \u00fclepakkumine, v\u00f5ib co-stop loendur t\u00f5usta, mis toob kaasa j\u00f5udluse probleemid nende VM-ide osas. <\/p>\n<p>Samuti t\u00f5useb co-stop, kui aktiivsete tuumade jaoks \u00fchel VM-il kasutatakse \u00fchte f\u00fc\u00fcsilist tuuma serveris hyper-treadinguga. Selline olukord v\u00f5ib tekkida n\u00e4iteks siis, kui VM-il on rohkem tuumasid kui serveris, kus ta t\u00f6\u00f6tab, f\u00fc\u00fcsiliselt olemas, v\u00f5i kui VM-il on sisse l\u00fclitatud seade 'preferHT'. Selle seadistuse kohta saab lugeda <noindex><a rel=\"nofollow\" href=\"https:\/\/blogs.vmware.com\/vsphere\/2014\/03\/perferht-use-2.html\">siin<\/a><\/noindex>. <\/p>\n<p>Keskenduge VM-i suuruse valimisele vastavalt tarkvara tootja soovitustele, mis t\u00f6\u00f6tab sellel VM-il, ja f\u00fc\u00fcsilise serveri v\u00f5imalustele, millel VM t\u00f6\u00f6tab, et v\u00e4ltida j\u00f5udlusega seotud probleeme k\u00f5rge co-stop'i t\u00f5ttu. <\/p>\n<p>\u00c4rge lisage tuumasid varuks, see v\u00f5ib p\u00f5hjustada j\u00f5udluse probleeme mitte ainult VM-i enda, vaid ka selle naabrite jaoks serveris.<\/p>\n<h3>Teised kasulikud CPU m\u00f5\u00f5dikud<\/h3>\n<p>\n<b>K\u00e4ita<\/b> \u2013 kui kaua (ms) vCPU oli m\u00f5\u00f5tmise perioodil RUN olekus, see t\u00e4hendab, et see tegi tegelikult kasulikku t\u00f6\u00f6d.<\/p>\n<p><b>Idle<\/b> \u2013 kui palju aega (ms) m\u00f5\u00f5tmisperioodi jooksul vCPU oli olemises ootere\u017eiimis. Suured Idle v\u00e4\u00e4rtused ei ole probleem, lihtsalt vCPU-l ei olnud \"midagi teha\".<\/p>\n<p><b>Oota<\/b> \u2013 kui palju aega (ms) m\u00f5\u00f5tmisperioodi jooksul vCPU oli olekus Wait. Kuna see loendur h\u00f5lmab ka IDLE, ei t\u00e4henda k\u00f5rged Wait v\u00e4\u00e4rtused probleemide olemasolu. Kui aga k\u00f5rge Wait ja madal IDLE, t\u00e4hendab see, et VM ootas sisse-\/v\u00e4ljundoperatsioonide l\u00f5petamist, mis v\u00f5ib viidata k\u00f5vaketta v\u00f5i m\u00f5ne virtuaalse seadme j\u00f5udluse probleemidele.<\/p>\n<p><b>Max limited<\/b> \u2013 kui palju aega (ms) m\u00f5\u00f5tmisperioodi jooksul vCPU oli olekus Ready seoses seadistatud ressursipiiranguga. Kui j\u00f5udlus on arusaamatult madal, on kasulik kontrollida seda loendurit ja CPU piiri VM-i seadistustes. VM-il v\u00f5ivad olla seatud piirangud, millest te ei tea. N\u00e4iteks toimub see siis, kui VM on kloonitud mallist, millel oli CPU piirang.<\/p>\n<p><b>Swap wait<\/b> \u2013 kui palju aega m\u00f5\u00f5tmisperioodi jooksul vCPU ootas operatsiooni VMkernel Swapiga. Kui selle loenduri v\u00e4\u00e4rtused on \u00fcle nulli, siis on VM-il kindlasti j\u00f5udlusprobleemid. SWAPist r\u00e4\u00e4gime p\u00f5hjalikumalt m\u00e4lukalkulaatorite artiklis.<\/p>\n<h3>ESXTOP<\/h3>\n<p>\nKui vCenteri j\u00f5udlusloendurid on head ajalooliste andmete anal\u00fc\u00fcsimiseks, siis probleemide operatiivne anal\u00fc\u00fcs on parem teha ESXTOP'is. Siin on k\u00f5ik v\u00e4\u00e4rtused esitatud valmis kujul (ei pea midagi t\u00f5lkima) ja minimaalne m\u00f5\u00f5tmisperiood on 2 sekundit.<br \/>\nESXTOP ekraan CPU kohta avatakse klahviga \"c\" ja n\u00e4eb v\u00e4lja j\u00e4rgmine:<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/f4f3611bc383007bdbaa0948001923c4.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nMugavuse huvides v\u00f5ib j\u00e4tta n\u00e4htavaks ainult virtuaalmasinate protsessid, vajutades Shift-V.<br \/>\nKuna tahate vaadata eraldi VM-i tuumade m\u00f5\u00f5dikuid, vajutage \"e\" ja sisestage huvitava VM-i GID (30919 ekraanipildil allpool):<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/5f2c0226cee6e4e43128537bd4da843f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nK\u00e4in l\u00fchidalt \u00fcle tulbad, mis on vaikimisi esitatud. T\u00e4iendavaid tulbasid saab lisada, vajutades \"f\".<\/p>\n<p><b>NWLD (Number of Worlds)<\/b> \u2013 protsesside arv grupis. Et avada grupp ja n\u00e4ha m\u00f5\u00f5dikuid iga protsessi (n\u00e4iteks igas tuumas mitme s\u00fcdamiku VM) jaoks, vajutage \u201ce\u201d. Kui grupis on rohkem kui \u00fcks protsess, siis grupi m\u00f5\u00f5dikute v\u00e4\u00e4rtused on v\u00f5rdsed eraldi protsesside m\u00f5\u00f5dikute summaga.<\/p>\n<p><b>%USED<\/b> \u2013 kui palju serveri CPU ts\u00fckleid kasutab protsess v\u00f5i protsessigrupp.<\/p>\n<p><b>%RUN<\/b> \u2013 kui palju aega m\u00f5\u00f5tmisperioodi jooksul protsess viibis RUN olekus, st t\u00e4itis kasulikku t\u00f6\u00f6d. Erineb %USED-st selle poolest, et ei arvestata hyper-threadingi, sageduse skaleerimist ja aega, mis kulus s\u00fcsteemsete \u00fclesannete (%SYS) jaoks.<\/p>\n<p><b>%SYS<\/b> \u2013 aeg, mis kulus s\u00fcsteemsete \u00fclesannete, nagu katkestuste, sisendi\/v\u00e4ljundi, v\u00f5rgu t\u00f6\u00f6 jne, t\u00e4itmiseks. V\u00e4\u00e4rtus v\u00f5ib olla k\u00f5rge, kui VM-l on suur sisend\/v\u00e4ljund.<\/p>\n<p><b>%OVRLP<\/b> \u2013 kui palju aega f\u00fc\u00fcsiline tuum, millel protsess VM-is t\u00e4idab, kulutas teiste protsesside \u00fclesannetele.<\/p>\n<p>Need m\u00f5\u00f5dikud on omavahel seotud j\u00e4rgmiselt:<\/p>\n<p>%USED = %RUN + %SYS \u2014 %OVRLP.<\/p>\n<p>Tavaliselt on m\u00f5\u00f5dik %USED informatiivsem.<\/p>\n<p><b>%WAIT<\/b> \u2013 kui palju aega m\u00f5\u00f5tmisperioodi jooksul protsess viibis Wait olekus. K\u00e4tkeb IDLE-d.<\/p>\n<p><b>%IDLE<\/b> \u2013 kui palju aega m\u00f5\u00f5tmisperioodi jooksul protsess viibis IDLE olekus.<\/p>\n<p><b>%SWPWT<\/b> \u2013 kui palju aega m\u00f5\u00f5tmisperioodi jooksul vCPU ootas operatsiooni VMkernel Swapiga.<\/p>\n<p><b>%VMWAIT<\/b> \u2013 kui palju aega m\u00f5\u00f5tmisperioodi jooksul vCPU viibis ooteseisundis (tavaliselt sisendi\/v\u00e4ljundi). Sarnast loendurit ei ole vCenteris. Kerged k\u00f5rged v\u00e4\u00e4rtused viitavad probleemidele VM-i sisendi\/v\u00e4ljundi osas.<\/p>\n<p>%WAIT = %VMWAIT + %IDLE + %SWPWT.<\/p>\n<p>Kui VM ei kasuta VMkernel Swapi, on tootlikkuse probleemide anal\u00fc\u00fcsimisel m\u00f5istlik j\u00e4lgida %VMWAIT-i, kuna see m\u00f5\u00f5dik ei arvesta aega, mil VM ei teinud midagi (%IDLE).<\/p>\n<p><b>%RDY<\/b> \u2013 kui palju aega m\u00f5\u00f5tmisperioodi jooksul protsess viibis Ready olekus.<\/p>\n<p><b>%CSTP<\/b> \u2013 kui palju aega m\u00f5\u00f5tmisperioodi jooksul protsess viibis costop olekus.<\/p>\n<p><b>%MLMTD<\/b> \u2013 kui palju aega m\u00f5\u00f5tmisperioodi jooksul vCPU viibis Ready olekus, kuna ressursipiirang oli paika pandud.<\/p>\n<p>%WAIT + %RDY + %CSTP + %RUN = 100% \u2013 tuum VM-is viibib pidevalt m\u00f5nes neist neljast olekust.<\/p>\n<h3>CPU h\u00fcpervisoril<\/h3>\n<p>\nvCenteris on ka h\u00fcpervisoorele suunatud CPU tootlikkuse loendurid, kuid need ei ole midagi huvitavat \u2013 need on lihtsalt loendurite summa k\u00f5ikidest VM-idest serveris.<br \/>\nCPU seisundi j\u00e4lgimine serveris on k\u00f5ige mugavam vahekaardil Summary:<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/15b6b9a6da136d892fbaf7f80fc206c1.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nServeril ning virtuaalsel masinal on standardne Alarm:<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/c3ae19ce3acd55cfff40d71437ee3a08.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKui serveri CPU koormus on k\u00f5rge, tekivad probleemid nendele VM-idele, mis t\u00f6\u00f6tavad sellel.<\/p>\n<p>ESXTOPis CPU serveri koormusandmed kuvatakse ekraani \u00fclaosas. Lisaks standardsele CPU koormusele, mis h\u00fcperviisorite jaoks on v\u00e4hem informatiivne, on kolm muud m\u00f5\u00f5dikut:<\/p>\n<p><b>CORE UTIL(%)<\/b> \u2013 f\u00fc\u00fcsilise serveri tuuma koormus. See m\u00f5\u00f5dik n\u00e4itab, kui kaua tuum m\u00f5\u00f5tmisperioodi jooksul t\u00f6\u00f6d tegi.<\/p>\n<p><b>PCPU UTIL(%)<\/b> \u2013 kui hyper-threading on sisse l\u00fclitatud, peab igale f\u00fc\u00fcsilisele tuumale olema kaks voogu (PCPU). See m\u00f5\u00f5dik n\u00e4itab, kui kaua iga voog t\u00f6\u00f6d tegi.<\/p>\n<p><b>PCPU USED(%)<\/b> \u2013 sama, mis PCPU UTIL(%), kuid arvestab sageduse skaleerimist (kas tuuma sageduse v\u00e4hendamine energias\u00e4\u00e4stu eesm\u00e4rgil v\u00f5i tuuma sageduse suurendamine Turbo Boosti tehnoloogia abil) ja hyper-threadingut.<\/p>\n<p>PCPU_USED% = PCPU_UTIL% * efektiivne tuuma sagedus \/ nimisagedus.<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/dd8562ea91bee55bbf630358df26c217.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>Sellel ekraanipildil on m\u00f5nedel tuumadel Turbo Boost'i t\u00f5ttu USED v\u00e4\u00e4rtus \u00fcle 100%, kuna tuuma sagedus on k\u00f5rgem kui nimisagedus.<\/i><\/p>\n<p>M\u00f5ned s\u00f5nad hyper-threadingu arvestamise kohta. Kui protsessid t\u00f6\u00f6tavad 100% aega m\u00f5lemal f\u00fc\u00fcsilise tuuma voolul ja tuum t\u00f6\u00f6tab nimisagedusel, siis:<\/p>\n<ul>\n<li>CORE UTIL tuuma jaoks on 100%,<\/li>\n<li>PCPU UTIL m\u00f5lema voolu jaoks on 100%,<\/li>\n<li>PCPU USED m\u00f5lema voolu jaoks on 50%.<\/li>\n<\/ul>\n<p>\nKui m\u00f5lemad vood ei t\u00f6\u00f6tanud 100% aega m\u00f5\u00f5tmisperioodi jooksul, jagatakse PCPU USED tuumade jaoks nendel perioodidel, kui vood t\u00f6\u00f6tasid paralleelselt, pooleks.<\/p>\n<p>ESXTOPis on ka ekraan serveri CPU energia tarbimise parameetrite jaoks. Siit saab vaadata, kas server kasutab energias\u00e4\u00e4stutehnoloogiaid: C-states ja P-states. Kutsutakse esile klahviga \u00abp\u00bb:<\/p>\n<p><img decoding=\"async\" alt=\"Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere&#039;is. Osa 1: CPU\" src=\"\/wp-content\/uploads\/2019\/05\/531bf847b99f86bec0bd90e005919c79.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Standardprobleemid CPU j\u00f5udluses<\/h3>\n<p>\nL\u00f5petuseks toon v\u00e4lja t\u00fc\u00fcpilised p\u00f5hjused, miks VM-i CPU j\u00f5udlusprobleeme esineb ja annan l\u00fchikesed n\u00e4pun\u00e4ited nende lahendamiseks:<\/p>\n<p><b>Tuuma taktsagedus on liiga madal.<\/b> Kui VMi ei ole v\u00f5imalik viia v\u00f5imekamatele tuumadele, v\u00f5ib proovida muuta energiat\u00f5hususe seadeid, et Turbo Boost t\u00f6\u00f6taks paremini.<\/p>\n<p><b>VM vale suurus (liialt palju\/v\u00e4he tuumasid).<\/b> Kui tuumasid on liiga v\u00e4he, on VM-il k\u00f5rge CPU koormus. Kui neid on liiga palju, tekib k\u00f5rge co-stop.<\/p>\n<p><b>Serveri CPU \u00fclevaatus on liiga suur.<\/b> Kui VMil on k\u00f5rge Ready, v\u00e4hendage CPU \u00fclevaatust.<\/p>\n<p><b>Vale NUMA-topoloogia suurtele VM-idele.<\/b> NUMA-topoloogia, mida n\u00e4eb VM (vNUMA), peab vastama serveri NUMA-topoloogiale (pNUMA). Probleemi diagnoosimise ja v\u00f5imalike lahenduste kohta on kirjutatud n\u00e4iteks raamatuis. <noindex><a rel=\"nofollow\" href=\"https:\/\/pages.rubrik.com\/host-resources-deep-dive_request.html\">\u00abVMware vSphere 6.5 Host Resources Deep Dive\u00bb<\/a><\/noindex>. Kui te ei soovi s\u00fcveneda ja kui teil ei ole litsentsipiiranguid VM-is installitud operatsioonis\u00fcsteemi osas, tehke VM-is palju virtuaalseid sokkide, iga\u00fches \u00fche tuumaga. Suurt kaotust ei teki \ud83d\ude42<\/p>\n<p>Sellega on mul CPU teemal k\u00f5ik. Esitage k\u00fcsimusi. J\u00e4rgmises osas r\u00e4\u00e4gin operatiivm\u00e4\u00e4rast.<\/p>\n<p><b class=\"spoiler_title\">Kasulikud lingid<\/b><noindex><a rel=\"nofollow\" href=\"http:\/\/virtual-red-dot.info\/vm-cpu-counters-vsphere\/\">http:\/\/virtual-red-dot.info\/vm-cpu-counters-vsphere\/<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/kb\/1017926\">https:\/\/kb.vmware.com\/kb\/1017926<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"http:\/\/www.yellow-bricks.com\/2012\/07\/17\/why-is-wait-so-high\/\">http:\/\/www.yellow-bricks.com\/2012\/07\/17\/why-is-wait-so-high\/<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/communities.vmware.com\/docs\/DOC-9279\">https:\/\/communities.vmware.com\/docs\/DOC-9279<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/www.vmware.com\/content\/dam\/digitalmarketing\/vmware\/en\/pdf\/techpaper\/performance\/whats-new-vsphere65-perf.pdf\">https:\/\/www.vmware.com\/content\/dam\/digitalmarketing\/vmware\/en\/pdf\/techpaper\/performance\/whats-new-vsphere65-perf.pdf<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/pages.rubrik.com\/host-resources-deep-dive_request.html\">https:\/\/pages.rubrik.com\/host-resources-deep-dive_request.html<\/a><\/noindex><br \/>\n<br \/>Allikas: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/dataline\/blog\/452884\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0415\u0441\u043b\u0438 \u0432\u044b \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0438\u0440\u0443\u0435\u0442\u0435 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u0443\u044e \u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u0443 \u043d\u0430 \u0431\u0430\u0437\u0435 VMware vSphere (\u0438\u043b\u0438 \u043b\u044e\u0431\u043e\u0433\u043e \u0434\u0440\u0443\u0433\u043e\u0433\u043e \u0441\u0442\u0435\u043a\u0430 \u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0439), \u0442\u043e \u043d\u0430\u0432\u0435\u0440\u043d\u044f\u043a\u0430 \u0447\u0430\u0441\u0442\u043e \u0441\u043b\u044b\u0448\u0438\u0442\u0435 \u043e\u0442 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0435\u0439 \u0436\u0430\u043b\u043e\u0431\u044b: \u00ab\u0412\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u0430\u044f \u043c\u0430\u0448\u0438\u043d\u0430 \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u043c\u0435\u0434\u043b\u0435\u043d\u043d\u043e!\u00bb. \u0412 \u044d\u0442\u043e\u043c \u0446\u0438\u043a\u043b\u0435 \u0441\u0442\u0430\u0442\u0435\u0439 \u0440\u0430\u0437\u0431\u0435\u0440\u0443 \u043c\u0435\u0442\u0440\u0438\u043a\u0438 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0438 \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0443, \u0447\u0442\u043e \u0438 \u043f\u043e\u0447\u0435\u043c\u0443 \u00ab\u0442\u043e\u0440\u043c\u043e\u0437\u0438\u0442\u00bb \u0438 \u043a\u0430\u043a \u0441\u0434\u0435\u043b\u0430\u0442\u044c \u0442\u0430\u043a, \u0447\u0442\u043e\u0431\u044b \u043d\u0435 \u00ab\u0442\u043e\u0440\u043c\u043e\u0437\u0438\u043b\u043e\u00bb. \u0411\u0443\u0434\u0443 \u0440\u0430\u0441\u0441\u043c\u0430\u0442\u0440\u0438\u0432\u0430\u0442\u044c \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u0435 \u0430\u0441\u043f\u0435\u043a\u0442\u044b \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u044b\u0445 \u043c\u0430\u0448\u0438\u043d: CPU, RAM, DISK, [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":25892,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-34335","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.1.1 - 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\/et\/blog\/administrirovanie\/analiz-proizvoditelnosti-virtualnoj-mashiny-v-vmware-vsphere-chast-1-cpu\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.1.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"et_EE\" \/>\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 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0439 \u043c\u0430\u0448\u0438\u043d\u044b \u0432 VMware vSphere. \u0427\u0430\u0441\u0442\u044c 1: CPU | ProHoster\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/analiz-proizvoditelnosti-virtualnoj-mashiny-v-vmware-vsphere-chast-1-cpu\" \/>\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-31T18:57:43+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:57:43+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\udd47Virtuaalmasina j\u00f5udluse anal\u00fc\u00fcs VMware vSphere'is. Osa 1: CPU | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/analiz-proizvoditelnosti-virtualnoj-mashiny-v-vmware-vsphere-chast-1-cpu","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"et_EE","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 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u043e\u0439 \u043c\u0430\u0448\u0438\u043d\u044b \u0432 VMware vSphere. \u0427\u0430\u0441\u0442\u044c 1: CPU | ProHoster","og:url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/analiz-proizvoditelnosti-virtualnoj-mashiny-v-vmware-vsphere-chast-1-cpu","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-31T18:57:43+00:00","article:modified_time":"2019-10-31T18:57:43+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"34335","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-21 18:48:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:23:17","updated":"2026-01-21 18:48:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/34335","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/comments?post=34335"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/34335\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media\/25892"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=34335"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=34335"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=34335"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}