![\"AWR:](\"\/wp-content\/uploads\/2020\/09\/b0ca997a4bd415723ae56c183e2dd42f.jpeg\")
<\/p>\nMe k\u00ebt\u00eb post t\u00eb vog\u00ebl doja t\u00eb sqaroj nj\u00eb keqkuptim q\u00eb ka t\u00eb b\u00ebj\u00eb me analiz\u00ebn AWR t\u00eb bazave t\u00eb dh\u00ebnave q\u00eb punojn\u00eb n\u00eb Oracle Exadata. P\u00ebr gati 10 vjet kam hasur vazhdimisht pyetjen: cila \u00ebsht\u00eb kontributi i Exadata Software n\u00eb performanc\u00ebn? Apo, duke p\u00ebrdorur terma t\u00eb rinj: sa \u2018eksadatizohet\u2019 puna e nj\u00eb baze t\u00eb caktuar?<\/p>\n
<\/p>\n
Shpesh, p\u00ebrgjigjja ndaj k\u00ebtij pyetje t\u00eb sakt\u00eb, sipas mendimit tim, \u00ebsht\u00eb e gabuar dhe referohet n\u00eb statistikat AWR. Ato paraqesin nj\u00eb metod\u00eb t\u00eb pritjes s\u00eb sistemeve, q\u00eb interpreton koh\u00ebn e p\u00ebrgjigjes si shum\u00ebn e koh\u00ebs s\u00eb pun\u00ebs s\u00eb procesor\u00ebve (DB CPU) dhe koh\u00ebs s\u00eb pritjes p\u00ebr klasat e ndryshme.<\/p>\n
Me ardhjen e Exadata-s, n\u00eb statistikat AWR jan\u00eb shfaqur pritje specifike t\u00eb sistemit, t\u00eb lidhura me funksionimin e Exadata Software. Nj\u00eb rregull \u00ebsht\u00eb q\u00eb emrat e k\u00ebtyre pritjeve fillojn\u00eb me fjal\u00ebn \u201ccell\u201d (ku \u201ccell\u201d n\u00ebnkupton serverin e ruajtjes Exadata), dhe m\u00eb shpesh hasen pritje me emra dometh\u00ebn\u00ebs si \u201ccell smart table scan\u201d, \u201ccell multiblock physical read\u201d dhe \u201ccell single block physical read\u201d.<\/p>\n
N\u00eb shumic\u00ebn e rasteve, pjesa e k\u00ebtyre pritjeve Exadata n\u00eb koh\u00ebn totale t\u00eb p\u00ebrgjigjes \u00ebsht\u00eb e vog\u00ebl, dhe prandaj ato as nuk kapen n\u00eb seksionin Top10 Foreground Events by Total Wait Time (n\u00eb k\u00ebt\u00eb rast ato duhet t\u00eb k\u00ebrkohen n\u00eb seksionin Foreground Wait Events). Ne me v\u00ebshtir\u00ebsi zbuluam te klient\u00ebt tan\u00eb nj\u00eb rast t\u00eb AWR-s\u00eb p\u00ebr nj\u00eb dit\u00eb, ku pritjet Exadata u gjet\u00ebn n\u00eb seksionin Top10 dhe p\u00ebrb\u00ebnin rreth 5% t\u00eb gjithsej.<\/p>\n
Ngjarja<\/strong><\/p>\n Pritjet<\/strong><\/p>\n Koha Totale e Pritjes (sek)<\/strong><\/p>\n Mesatarja e Pritjes<\/strong><\/p>\n % Koha DB<\/strong><\/p>\n Klasifikimi i Pritjes<\/strong><\/p>\n DB CPU<\/p>\n <\/p>\n 115.2K<\/p>\n <\/p>\n 70.4<\/p>\n <\/p>\n SQL*Net m\u00eb shum\u00eb t\u00eb dh\u00ebna nga dblink<\/p>\n 670,196<\/p>\n 5471.5<\/p>\n 8.16ms<\/p>\n 3.3<\/p>\n Rrjeti\n regjistro log \/dev\/log local0\n regjistro log \/dev\/log local1 notice\n chroot \/var\/lib\/haproxy\n stats timeout 30s\n p\u00ebrdorues haproxy\n grup haproxy\n daemon\n\ndefaults\n log global\n mode http\n opsion httplog\n opsion dontlognull\n timeout connect 5000\n timeout client 50000\n timeout server 50000\n\nfrontend http_front\n bind *:80\n stats uri \/haproxy?stats\n default_backend http_back\n\nbackend http_back\n balance roundrobin\n server server_name1 private_ip1:80 check\n server server_name2 private_ip2:80 check<\/p>\n cell single block physical read<\/p>\n 5,661,452<\/p>\n 3827.6<\/p>\n 676.07us<\/p>\n 2.3<\/p>\n User I\/O<\/p>\n Sync ASM rebalance<\/p>\n 4,350,012<\/p>\n 3481.3<\/p>\n 800.30us<\/p>\n 2.1<\/p>\n Tjet\u00ebr<\/p>\n cell multiblock physical read<\/p>\n 759,885<\/p>\n 2252<\/p>\n 2.96ms<\/p>\n 1.4<\/p>\n User I\/O<\/p>\n direct path read<\/p>\n 374,368<\/p>\n 1811.3<\/p>\n 4.84ms<\/p>\n 1.1<\/p>\n User I\/O<\/p>\n SQL*Net mesazh nga dblink<\/p>\n 7,983<\/p>\n 1725<\/p>\n 216.08ms<\/p>\n 1.1<\/p>\n Rrjeti\n regjistro log \/dev\/log local0\n regjistro log \/dev\/log local1 notice\n chroot \/var\/lib\/haproxy\n stats timeout 30s\n p\u00ebrdorues haproxy\n grup haproxy\n daemon\n\ndefaults\n log global\n mode http\n opsion httplog\n opsion dontlognull\n timeout connect 5000\n timeout client 50000\n timeout server 50000\n\nfrontend http_front\n bind *:80\n stats uri \/haproxy?stats\n default_backend http_back\n\nbackend http_back\n balance roundrobin\n server server_name1 private_ip1:80 check\n server server_name2 private_ip2:80 check<\/p>\n cell smart table scan<\/p>\n 1,007,520<\/p>\n 1260.7<\/p>\n 1.25ms<\/p>\n 0.8<\/p>\n User I\/O<\/p>\n direct path read temp<\/p>\n 520,211<\/p>\n 808.4<\/p>\n 1.55ms<\/p>\n 0.5<\/p>\n User I\/O<\/p>\n enq: TM \u2014 kontestimi<\/p>\n 652<\/p>\n 795.8<\/p>\n 1220.55ms<\/p>\n 0.5<\/p>\n Application<\/p>\n Nga nj\u00eb statistik\u00eb t\u00eb till\u00eb AWR shpesh nxirren k\u00ebto p\u00ebrfundime:<\/p>\n 1. Kontributi i magjis\u00eb Exadata n\u00eb performanc\u00ebn e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave nuk \u00ebsht\u00eb i lart\u00eb \u2014 nuk e kalon 5%, dhe baza e t\u00eb dh\u00ebnave \u00abekzadatizohet\u00bb dob\u00ebt.<\/p>\n 2. N\u00ebse nj\u00eb baz\u00eb e till\u00eb transferohet nga Exadata n\u00eb arkitektur\u00ebn klasike \u00abserver + grumbull\u00bb, at\u00ebher\u00eb performanca nuk do t\u00eb ndryshoj\u00eb shum\u00eb. Sepse edhe n\u00ebse ky grumbull \u00ebsht\u00eb tri her\u00eb m\u00eb i ngadalsh\u00ebm se sistemi i ruajtjes Exadata (\u00e7ka \u00ebsht\u00eb shum\u00eb e pamundur p\u00ebr grumbujt modern\u00eb All Flash), duke shum\u00ebzuar 5% me tre do t\u00eb kemi nj\u00eb rritje t\u00eb d\u00ebshmive t\u00eb pritjes s\u00eb hyrjes-daljes deri n\u00eb 15% \u2014 nj\u00eb baz\u00eb e dh\u00ebnash me siguri do ta p\u00ebrballoj\u00eb k\u00ebt\u00eb!<\/p>\n T\u00eb dy k\u00ebto p\u00ebrfundime jan\u00eb t\u00eb pasakta; m\u00eb shum\u00eb, ato distortojn\u00eb kuptimin e ides\u00eb q\u00eb shprehet n\u00eb Exadata Software. Exadata nuk ofron vet\u00ebm I\/O t\u00eb shpejt\u00eb, ajo funksionon ndryshe n\u00eb krahasim me arkitektur\u00ebn klasike \u2018server + sistem ruajtjeje\u2019. N\u00ebse puna e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave me t\u00eb v\u00ebrtet\u00eb \u2018ekzadatizohet\u2019 \u2014 at\u00ebher\u00eb logjika SQL transferohet n\u00eb sistemin e ruajtjes. falas. Kjo \u00ebsht\u00eb vet\u00ebm nj\u00eb nga shum\u00eb privilegjet q\u00eb ofrojm\u00eb p\u00ebr klient\u00ebt tan\u00eb t\u00eb rinj t\u00eb web-hosting.<\/a> Ruajtja, fal\u00eb nj\u00eb sere mekanizmash t\u00eb ve\u00e7ant\u00eb (sidomos Exadata Storage Indexes, por jo vet\u00ebm), gjendet vet\u00eb t\u00eb dh\u00ebnat e nevojshme dhe i d\u00ebrgon ato n\u00eb serverat DB. Ata e b\u00ebjn\u00eb k\u00ebt\u00eb mjaft efektivisht, k\u00ebshtu q\u00eb pjesa e pritjeve tipike Exadata n\u00eb koh\u00ebn totale t\u00eb p\u00ebrgjigjes \u00ebsht\u00eb e vog\u00ebl. <\/p>\n Si do t\u00eb ndryshoj\u00eb kjo pjes\u00eb jasht\u00eb Exadata-s? Si do ta ndikoj\u00eb performanc\u00ebn e p\u00ebrgjithshme t\u00eb baz\u00ebs s\u00eb t\u00eb dh\u00ebnave? Testimi \u00ebsht\u00eb m\u00ebnyra m\u00eb e mir\u00eb p\u00ebr t\u00eb p\u00ebrgjigjur k\u00ebtyre pyetjeve. P\u00ebr shembull, pritja \u201ccell smart table scan\u201d jasht\u00eb Exadata-s mund t\u00eb shnd\u00ebrrohet n\u00eb nj\u00eb skanim t\u00eb r\u00ebnd\u00eb t\u00eb tabelave, aq sa I\/O mund t\u00eb marr\u00eb gjith\u00eb koh\u00ebn e p\u00ebrgjigjes dhe performanca t\u00eb p\u00ebrkeq\u00ebsohet dramatikisht. Prandaj, \u00ebsht\u00eb e gabuar gjat\u00eb analiz\u00ebs AWR t\u00eb konsiderosh procentin e p\u00ebrgjithsh\u00ebm t\u00eb pritjeve Exadata si nj\u00eb kontribut t\u00eb magjis\u00eb s\u00eb saj n\u00eb performanc\u00eb dhe akoma m\u00eb shum\u00eb ta konsiderosh k\u00ebt\u00eb p\u00ebrqindje p\u00ebr parashikimin e performanc\u00ebs jasht\u00eb Exadata-s. P\u00ebr t\u00eb kuptuar se sa \u2018ekzadatizohet\u2019 puna e nj\u00eb baze, duhet t\u00eb shqyrtohen statistikat AWR t\u00eb seksionit \u201cInstance Activity Stats\u201d (atje ka shum\u00eb statistika me emra dometh\u00ebn\u00ebs) dhe t\u2019i krahasosh ato me nj\u00ebra-tjetr\u00ebn.<\/p>\n Dhe p\u00ebr t\u00eb kuptuar se si do t\u00eb ndjehet baza e t\u00eb dh\u00ebnave jasht\u00eb Exadata-s, m\u00eb mir\u00eb \u00ebsht\u00eb t\u00eb b\u00ebhet nj\u00eb kopje e backup-it t\u00eb baz\u00ebs n\u00eb arkitektur\u00ebn e synuar dhe t\u00eb analizohet performanca e k\u00ebsaj kopje n\u00ebn ngarkes\u00eb. Kjo mund\u00ebsi zakonisht e kan\u00eb ata q\u00eb zot\u00ebrojn\u00eb Exadata.<\/p>\n