{"id":1916,"date":"2018-11-27T22:40:41","date_gmt":"2018-11-28T00:40:41","guid":{"rendered":"http:\/\/dbtimewizard.com.br\/blog\/?p=1916"},"modified":"2019-11-11T18:36:01","modified_gmt":"2019-11-11T21:36:01","slug":"tirando-um-raio-x-do-desempenho-do-codigo-plsql","status":"publish","type":"post","link":"http:\/\/dbtimewizard.com.br\/blog\/tirando-um-raio-x-do-desempenho-do-codigo-plsql\/","title":{"rendered":"Tirando um RAIO-X do desempenho do c\u00f3digo PL\/SQL"},"content":{"rendered":"

Voc\u00ea escreveu seu c\u00f3digo PL\/SQL (Procedure, Function ou Package) e na hora de testar descobre que o desempenho n\u00e3o esta satisfat\u00f3rio, e agora? o que fazer?\u00a0A vers\u00e3o do banco Oracle 11g disp\u00f5e do recurso Hierarchical Profiler<\/strong> que permite medir o desempenho de cada linha de c\u00f3digo do PL\/SQL, com a utiliza\u00e7\u00e3o desse recurso fica f\u00e1cil identificar o que precisa ser melhorado no seu c\u00f3digo.<\/span><\/p>\n

Neste artigo vamos ver um exemplo pr\u00e1tico de utiliza\u00e7\u00e3o do recurso Hierarchical Profiler<\/strong> utilizando a ferramenta gr\u00e1fica SQLDeveloper da Oracle.<\/span><\/p>\n

Para realizar esta simula\u00e7\u00e3o vamos:<\/span><\/p>\n

1) Configurar o usu\u00e1rio para utilizar o recurso HPROF<\/span><\/strong>
\n2) Executar a procedure utilizando HPROF<\/span><\/strong>
\n3) Identificar a linha da procedure com baixo desempenho<\/span><\/strong>
\n4) Alterar o c\u00f3digo da procedure com baixo desempenho<\/span><\/strong>
\n5) Verificar desempenho da procedure ap\u00f3s altera\u00e7\u00e3o do c\u00f3digo<\/span><\/strong><\/p>\n

1) Configurar o usu\u00e1rio para utilizar o recurso HPROF<\/span><\/h2>\n

Para utilizar o recurso Hierarchical Profiler precisamos configurar um diret\u00f3rio no servidor do banco, atribuir privil\u00e9gios de acesso neste diret\u00f3rio ao usu\u00e1rio no qual ser\u00e3o criados os c\u00f3digos PL\/SQL, permitir que este usu\u00e1rio execute o pacote DBMS_HPROF, criar as tabelas necess\u00e1rias ao recurso Hierarchical Profiler e criar uma PROCEDURE para realizarmos a simula\u00e7\u00e3o.<\/span><\/p>\n

A procedure utilizada nesta simula\u00e7\u00e3o foi criada somente para fins did\u00e1ticos e n\u00e3o deve ser considerada como melhores pr\u00e1ticas de programa\u00e7\u00e3o PL\/SQL.<\/span><\/p>\n

 <\/p>\n

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
<\/div><\/td>
[<\/span>oracle@<\/span>odbsrv01 oracle]<\/span>$ mkdir<\/span><\/a> \/<\/span>oracle\/<\/span>SH
\n[<\/span>oracle@<\/span>odbsrv01 oracle]<\/span>$ sqlplus \/<\/span> as<\/span> sysdba
\n
\nSQL*<\/span>Plus:<\/span> Release 11.<\/span>2.<\/span>0.<\/span>4.<\/span>0 Production on Fri Nov 23<\/span> 10<\/span>:<\/span>43<\/span>:<\/span>49<\/span> 2018<\/span>
\n
\nCopyright (<\/span>c)<\/span> 1982<\/span>,<\/span> 2013<\/span>,<\/span> Oracle.<\/span>  All rights reserved.<\/span>
\n
\n
\nConnected to:<\/span>
\nOracle Database 11g Enterprise Edition Release 11.<\/span>2.<\/span>0.<\/span>4.<\/span>0 -<\/span> 64bit Production
\nWith the Partitioning,<\/span> Real Application Clusters,<\/span> Automatic Storage Management,<\/span> OLAP,<\/span>
\nData Mining and Real Application Testing options
\n
\nSQL><\/span>
\nSQL><\/span> SELECT *<\/span> FROM V$VERSION<\/span> where rownum <<\/span> 2<\/span>;<\/span>
\n
\nBANNER
\n--------------------------------------------------------------------------------<\/span>
\nOracle Database 11g Enterprise Edition Release 11.<\/span>2.<\/span>0.<\/span>4.<\/span>0 -<\/span> 64bit Production
\n
\nSQL><\/span> create directory PLSHPROF_DIR as<\/span> '\/oracle\/SH'<\/span>;<\/span>
\n
\n
\nDirectory created.<\/span>
\n
\nSQL><\/span> -----------------------------------------------<\/span>
\nSQL><\/span> --<\/span> Atribuir os privil\u00e9gios para usu\u00e1rio SH
\nSQL><\/span> -----------------------------------------------<\/span>
\nSQL><\/span>
\nSQL><\/span> grant read,<\/span>write on directory PLSHPROF_DIR to SH;<\/span>
\n
\nGrant succeeded.<\/span>
\n
\nSQL><\/span> grant execute on DBMS_HPROF to SH;<\/span>
\n
\nGrant succeeded.<\/span>
\n
\nSQL><\/span> -----------------------------------------------<\/span>
\nSQL><\/span> --<\/span> Criar as<\/span> tabelas para HPROF no schema SH
\nSQL><\/span> -----------------------------------------------<\/span>
\nSQL><\/span> conn sh\/<\/span>sh
\nConnected.<\/span>
\nSQL><\/span> @<\/span>?\/<\/span>rdbms\/<\/span>admin\/<\/span>dbmshptab.<\/span>sql;<\/span>
\n
\nTable dropped.<\/span>
\n
\n
\nTable dropped.<\/span>
\n
\n
\nTable dropped.<\/span>
\n
\n
\nSequence dropped.<\/span>
\n
\n
\nTable created.<\/span>
\n
\n
\nComment created.<\/span>
\n
\n
\nTable created.<\/span>
\n
\n
\nComment created.<\/span>
\n
\n
\nTable created.<\/span>
\n
\n
\nComment created.<\/span>
\n
\n
\nSequence created.<\/span>
\n
\nSQL><\/span>
\nSQL><\/span> -----------------------------------------------<\/span>
\nSQL><\/span> --<\/span> Criar as<\/span> tabelas auxiliares
\nSQL><\/span> -----------------------------------------------<\/span>
\nSQL><\/span>
\nSQL><\/span> CREATE TABLE SH.<\/span>CUSTOMERS_COUNTRIES
\n  2<\/span>     (<\/span>       COUNTRY_NAME            VARCHAR2(<\/span>40<\/span> BYTE)<\/span>       NOT NULL<\/span> ENABLE,<\/span>
\n  3<\/span>     COUNTRY_REGION          VARCHAR2(<\/span>20<\/span> BYTE)<\/span>       NOT NULL<\/span> ENABLE,<\/span>
\n  4<\/span>     CUST_ID                 NUMBER                  NOT NULL<\/span> ENABLE,<\/span>
\n  5<\/span>     CUST_GENDER             CHAR(<\/span>1<\/span> BYTE)<\/span>            NOT NULL<\/span> ENABLE,<\/span>
\n  6<\/span>     CUST_STATE_PROVINCE     VARCHAR2(<\/span>40<\/span> BYTE)<\/span>       NOT NULL<\/span> ENABLE,<\/span>
\n  7<\/span>     CONSTRAINT cust_countr_pk PRIMARY KEY<\/span><\/a> (<\/span>CUST_ID)<\/span>
\n  8<\/span>     USING INDEX TABLESPACE USERS )<\/span>
\n  9<\/span>     TABLESPACE USERS ;<\/span>
\n
\nTable created.<\/span>
\n
\nSQL><\/span>
\nSQL><\/span> CREATE TABLE SH.<\/span>SALES_SUM
\n  2<\/span>     (<\/span>       CUST_ID                 NUMBER                  NOT NULL<\/span> ENABLE,<\/span>
\n  3<\/span>     AMOUNT_SOLD             NUMBER(<\/span>10<\/span>,<\/span>2<\/span>)<\/span>            NOT NULL<\/span> ENABLE,<\/span>
\n  4<\/span>     CONSTRAINT sale_sum_pk PRIMARY KEY<\/span><\/a> (<\/span>CUST_ID)<\/span>
\n  5<\/span>     USING INDEX TABLESPACE USERS )<\/span>
\n  6<\/span>     TABLESPACE USERS ;<\/span>
\n
\nTable created.<\/span>
\n
\nSQL><\/span>
\nSQL><\/span> -----------------------------------------------<\/span>
\nSQL><\/span> --<\/span> Criar uma procedure no schema SH
\nSQL><\/span> -----------------------------------------------<\/span>
\nSQL><\/span>
\nSQL><\/span> create or replace PROCEDURE PRC_REPORT_01(<\/span>
\n  2<\/span>  in_country_name    IN varchar2
\n  3<\/span>  )<\/span> IS
\n  4<\/span>
\n  5<\/span>  CURSOR c_cust_count IS
\n  6<\/span>          Select cu.<\/span>cust_id,<\/span> co.<\/span>country_name,<\/span> co.<\/span>country_region,<\/span> cu.<\/span>cust_gender,<\/span> cu.<\/span>cust_state_province
\n  7<\/span>            From customers cu,<\/span> countries co
\n  8<\/span>           Where cu.<\/span>country_id =<\/span> co.<\/span>country_id
\n  9<\/span>             and co.<\/span>country_name =<\/span> in_country_name
\n 10<\/span>        Order By cu.<\/span>cust_id;<\/span>
\n 11<\/span>
\n 12<\/span>  CURSOR c_sales_sum IS
\n 13<\/span>          Select s.<\/span>cust_id,<\/span> sum(<\/span>s.<\/span>amount_sold)<\/span> amount_sold
\n 14<\/span>            From sales s
\n 15<\/span>  --<\/span>          From sales s,<\/span> customers_countries cc
\n 16<\/span>  --<\/span>         Where s.<\/span>cust_id =<\/span> cc.<\/span>cust_id
\n 17<\/span>        Group By s.<\/span>cust_id
\n 18<\/span>        Order By s.<\/span>cust_id;<\/span>
\n 19<\/span>
\n 20<\/span>  CURSOR c_report IS
\n 21<\/span>          Select cc.<\/span>country_region,<\/span> cc.<\/span>country_name,<\/span> cc.<\/span>cust_state_province,<\/span> cc.<\/span>cust_gender,<\/span> sum(<\/span>ss.<\/span>amount_sold)<\/span> amount_sold
\n 22<\/span>            From customers_countries cc,<\/span>
\n 23<\/span>                 sales_sum ss
\n 24<\/span>           Where cc.<\/span>cust_id =<\/span> ss.<\/span>cust_id
\n 25<\/span>        Group By cc.<\/span>country_region,<\/span> cc.<\/span>country_name,<\/span> cc.<\/span>cust_state_province,<\/span> cc.<\/span>cust_gender
\n 26<\/span>        Order By cc.<\/span>country_region,<\/span> cc.<\/span>country_name,<\/span> cc.<\/span>cust_state_province;<\/span>
\n 27<\/span>
\n 28<\/span>
\n 29<\/span>  reg_cust_count   c_cust_count%<\/span>ROWTYPE;<\/span>
\n 30<\/span>
\n 31<\/span>  reg_sales_sum    c_sales_sum%<\/span>ROWTYPE;<\/span>
\n 32<\/span>
\n 33<\/span>  reg_report       c_report%<\/span>ROWTYPE;<\/span>
\n 34<\/span>
\n 35<\/span>  BEGIN
\n 36<\/span>
\n 37<\/span>     EXECUTE IMMEDIATE 'truncate table customers_countries'<\/span>;<\/span>
\n 38<\/span>     EXECUTE IMMEDIATE 'truncate table sales_sum'<\/span>;<\/span>
\n 39<\/span>
\n 40<\/span>     OPEN c_cust_count;<\/span>
\n 41<\/span>
\n 42<\/span>        LOOP
\n 43<\/span>            FETCH c_cust_count
\n 44<\/span>             INTO reg_cust_count;<\/span>
\n 45<\/span>
\n 46<\/span>            EXIT<\/span><\/a> WHEN c_cust_count%<\/span>NOTFOUND;<\/span>
\n 47<\/span>
\n 48<\/span>            INSERT INTO CUSTOMERS_COUNTRIES (<\/span>country_name,<\/span> country_region,<\/span> cust_id,<\/span> cust_gender,<\/span> cust_state_province)<\/span>
\n 49<\/span>                                      VALUES(<\/span>reg_cust_count.<\/span>country_name,<\/span> reg_cust_count.<\/span>country_region,<\/span> reg_cust_count.<\/span>cust_id,<\/span> reg_cust_count.<\/span>cust_gender,<\/span> reg_cust_count.<\/span>cust_state_province)<\/span>;<\/span>
\n 50<\/span>            COMMIT;<\/span>
\n 51<\/span>
\n 52<\/span>        END<\/span><\/a> LOOP;<\/span>
\n 53<\/span>
\n 54<\/span>     CLOSE c_cust_count;<\/span>
\n 55<\/span>
\n 56<\/span>     OPEN c_sales_sum;<\/span>
\n 57<\/span>
\n 58<\/span>        LOOP
\n 59<\/span>            FETCH c_sales_sum
\n 60<\/span>             INTO reg_sales_sum;<\/span>
\n 61<\/span>
\n 62<\/span>            EXIT<\/span><\/a> WHEN c_sales_sum%<\/span>NOTFOUND;<\/span>
\n 63<\/span>
\n 64<\/span>            INSERT INTO SALES_SUM (<\/span>cust_id,<\/span> amount_sold)<\/span>
\n 65<\/span>                            VALUES(<\/span>reg_sales_sum.<\/span>cust_id,<\/span> reg_sales_sum.<\/span>amount_sold)<\/span>;<\/span>
\n 66<\/span>            COMMIT;<\/span>
\n 67<\/span>
\n 68<\/span>        END<\/span><\/a> LOOP;<\/span>
\n 69<\/span>
\n 70<\/span>     CLOSE c_sales_sum;<\/span>
\n 71<\/span>
\n 72<\/span>     OPEN c_report;<\/span>
\n 73<\/span>
\n 74<\/span>        LOOP
\n 75<\/span>            FETCH c_report
\n 76<\/span>             INTO reg_report;<\/span>
\n 77<\/span>
\n 78<\/span>            EXIT<\/span><\/a> WHEN c_report%<\/span>NOTFOUND;<\/span>
\n 79<\/span>
\n 80<\/span>            dbms_output.<\/span>put_line(<\/span>reg_report.<\/span>country_region||<\/span>'_'<\/span>||<\/span>reg_report.<\/span>country_name||<\/span>'_'<\/span>||<\/span>reg_report.<\/span>cust_state_province||<\/span>'_'<\/span>||<\/span>reg_report.<\/span>cust_gender||<\/span>' => '<\/span>||<\/span> reg_report.<\/span>amount_sold)<\/span>;<\/span>
\n 81<\/span>
\n 82<\/span>            COMMIT;<\/span>
\n 83<\/span>
\n 84<\/span>        END<\/span><\/a> LOOP;<\/span>
\n 85<\/span>
\n 86<\/span>     CLOSE c_report;<\/span>
\n 87<\/span>
\n 88<\/span>
\n 89<\/span>
\n 90<\/span>  EXCEPTION
\n 91<\/span>     WHEN OTHERS THEN
\n 92<\/span>
\n 93<\/span>        DBMS_OUTPUT.<\/span>PUT_LINE(<\/span>'ERRO :'<\/span> ||<\/span> SQLCODE ||<\/span> ' - '<\/span> ||<\/span> SQLERRM)<\/span>;<\/span>
\n 94<\/span>
\n 95<\/span>        CLOSE c_cust_count;<\/span>
\n 96<\/span>        CLOSE c_sales_sum;<\/span>
\n 97<\/span>        CLOSE c_report;<\/span>
\n 98<\/span>
\n 99<\/span>  END<\/span><\/a> PRC_REPORT_01;<\/span>
\n100<\/span>  \/<\/span>
\n
\nProcedure created.<\/span>
\n
\nSQL><\/span><\/div><\/td><\/tr><\/tbody><\/table><\/div>\n

 <\/p>\n

2) Executar a procedure utilizando HPROF<\/span><\/h2>\n

Vamos abrir uma conex\u00e3o no banco Oracle com o usu\u00e1rio SH utilizando o SQLDeveloper, na lista de objetos do usu\u00e1rio SH vamos clicar com o bot\u00e3o direito na PROCEDURE PRC_REPORT_01 e clicar em PROFILE… conforme imagem abaixo:<\/span><\/p>\n

 <\/p>\n

\"01_acionar_HPROF\"<\/a><\/p>\n

 <\/p>\n

Na sequ\u00eancia ser\u00e1 aberta uma janela PERFIL PL\/SQL onde vamos informar o par\u00e2metro PA\u00cdS igual a “Canada”, conforme imagem abaixo:<\/span><\/p>\n

 <\/p>\n

\"02_Passar_variavel\"<\/a><\/p>\n

 <\/p>\n

3) Identificar a linha da procedure com baixo desempenho<\/span><\/h2>\n

 <\/p>\n

Ap\u00f3s a execu\u00e7\u00e3o da procedure algumas estat\u00edsticas ser\u00e3o exibidas, na imagem abaixo temos o tempo total de execu\u00e7\u00e3o da procedure em micro-segundos indicado pela seta vermelha 01, ao clicarmos nesse valor aparecer\u00e1 uma janela abaixo com as informa\u00e7\u00f5es estat\u00edsticas de cada linha do c\u00f3digo PL\/SQL executado, para identificarmos a linha que esta consumindo mais tempo no c\u00f3digo precisamos clicar na seta de ordena\u00e7\u00e3o descendente do campo FUNCTION % (seta vermelha 02), nesta simula\u00e7\u00e3o podemos ver que a linha 66 da procedure esta consumindo 70,2% do tempo total de execu\u00e7\u00e3o da procedure e essa linha foi executada 7059 vezes.<\/span><\/p>\n

 <\/p>\n

\"03_Estatisticas\"<\/a><\/p>\n

 
\n <\/p>\n

Clicando na aba C\u00d3DIGO e localizando a linha 66, conforme indicado pelas setas vermelhas na imagem abaixo, podemos observar que a linha 66 corresponde ao comando COMMIT, este comando esta dentro de um LOOP que foi executado 7059 vezes pois o cursor C_SALES_SUM selecionou 7059 linhas.<\/span><\/p>\n

 <\/p>\n

\"04_Linha_codigo\"<\/a><\/p>\n

 <\/p>\n

Uma forma de tornar a procedure mais r\u00e1pida seria diminuindo o numero de linhas selecionadas no cursor C_SALES_SUM, verificando a consulta utilizada neste cursor, conforme imagem abaixo, podemos observar que ela esta selecionando todos os registros da tabela SALES, pois n\u00e3o existe um filtro na cl\u00e1usula WHERE. Como o relat\u00f3rio criado por esta procedure visa recuperar somente as informa\u00e7\u00f5es referentes a um determinado PA\u00cdS, podemos alterar esta consulta fazendo um JOIN com a tabela CUSTOMERS_COUNTRIES para selecionar na tabela SALES somente os registros referentes ao PA\u00cdS especificado como par\u00e2metro na procedure. Na procedure que foi executa o c\u00f3digo deste JOIN estava comentado, conforme imagem abaixo:<\/span><\/p>\n

 <\/p>\n

\"05_Consulta\"<\/a><\/p>\n

 <\/p>\n

4) Alterar o c\u00f3digo da procedure com baixo desempenho<\/span><\/h2>\n

Vamos alterar o c\u00f3digo da procedure conforme imagem abaixo:<\/span><\/p>\n

 <\/p>\n

\"06_Consulta_alterada\"<\/a><\/p>\n

 
\n <\/p>\n

Na sequ\u00eancia vamos compilar a procedure no banco, clicando no \u00edcone de engrenagem e na op\u00e7\u00e3o COMPILAR, conforme imagem abaixo:<\/span><\/p>\n

\"07_Compilar_procedure\"<\/a><\/p>\n

 <\/p>\n

5) Verificar o desempenho da procedure ap\u00f3s altera\u00e7\u00e3o do c\u00f3digo<\/span><\/h2>\n

Ap\u00f3s a compila\u00e7\u00e3o da procedure vamos execut\u00e1-la novamente repetindo os passos da etapa 2 e na sequ\u00eancia conferir as estat\u00edsticas conforme imagem abaixo:<\/span><\/p>\n

 <\/p>\n

\"08_Estatisticas2\"<\/a><\/p>\n

 <\/p>\n

Na imagem acima podemos verificar que o tempo de execu\u00e7\u00e3o da procedure antes da altera\u00e7\u00e3o foi de 4.699.941 micro-segundos, ou 4,7 segundos. Na execu\u00e7\u00e3o ap\u00f3s a altera\u00e7\u00e3o da procedure o tempo de execu\u00e7\u00e3o caiu para 122.611 micro-segundos, ou 12 cent\u00e9simos de segundo.<\/span><\/p>\n

 <\/p>\n

Refer\u00eancias<\/span><\/h2>\n

https:\/\/oracle-base.com\/articles\/11g\/plsql-hierarchical-profiler-11gr1<\/a><\/span><\/strong><\/p>\n

 
\n 
\n 
\n\"Promo-D75L\"<\/a><\/p>\n

\"video-02\"<\/a>
\n 
\n 
\n 
\n 
\n 
\n 
\n 
\n 
\n 
\n 
\n 
\n <\/p>\n","protected":false},"excerpt":{"rendered":"

Voc\u00ea escreveu seu c\u00f3digo PL\/SQL (Procedure, Function ou Package) e na hora de testar descobre que o desempenho n\u00e3o esta satisfat\u00f3rio, e agora? o que fazer?\u00a0A vers\u00e3o do banco Oracle 11g disp\u00f5e do recurso Hierarchical Profiler que permite medir o desempenho de cada linha de c\u00f3digo do PL\/SQL, com a utiliza\u00e7\u00e3o desse recurso fica f\u00e1cil identificar o que precisa ser<\/p>\n","protected":false},"author":2,"featured_media":1907,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[211],"tags":[207,206,210,209,208],"class_list":["post-1916","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-plsql","tag-dbms_hprof","tag-hierarchical-profiler","tag-plsql-profiler","tag-plsql-tuning","tag-sqldeveloper"],"aioseo_notices":[],"_links":{"self":[{"href":"http:\/\/dbtimewizard.com.br\/blog\/wp-json\/wp\/v2\/posts\/1916","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/dbtimewizard.com.br\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/dbtimewizard.com.br\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/dbtimewizard.com.br\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/dbtimewizard.com.br\/blog\/wp-json\/wp\/v2\/comments?post=1916"}],"version-history":[{"count":16,"href":"http:\/\/dbtimewizard.com.br\/blog\/wp-json\/wp\/v2\/posts\/1916\/revisions"}],"predecessor-version":[{"id":2071,"href":"http:\/\/dbtimewizard.com.br\/blog\/wp-json\/wp\/v2\/posts\/1916\/revisions\/2071"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/dbtimewizard.com.br\/blog\/wp-json\/wp\/v2\/media\/1907"}],"wp:attachment":[{"href":"http:\/\/dbtimewizard.com.br\/blog\/wp-json\/wp\/v2\/media?parent=1916"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/dbtimewizard.com.br\/blog\/wp-json\/wp\/v2\/categories?post=1916"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/dbtimewizard.com.br\/blog\/wp-json\/wp\/v2\/tags?post=1916"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}