Balazs Jeszenszky created IMPALA-7478:
-----------------------------------------
Summary: Add timer to impalad-side of DDLs
Key: IMPALA-7478
URL: https://issues.apache.org/jira/browse/IMPALA-7478
Project: IMPALA
Issue Type: Improvement
Components: Backend
Affects Versions: Impala 3.0
Reporter: Balazs Jeszenszky
Currently, profiles include CatalogOpExecTimer, but aren't helpful if the time
is spent on the impalad side. A scoped timer to ProcessCatalogUpdateResult
would be useful for clarity.
This is what we've come across:
{code:java}
Query Timeline: 6s001ms
- Query submitted: 159.835us (159.835us)
- Planning finished: 1.686ms (1.526ms)
- Rows available: 5s999ms (5s997ms)
- First row fetched: 6s000ms (1.027ms)
- Unregister query: 6s000ms (709.442us)
ImpalaServer:
- CatalogOpExecTimer: 3s188ms
- ClientFetchWaitTimer: 1.690ms
- RowMaterializationTimer: 0.000ns
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
