You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
143857: explain: show "execution time" on EXPLAIN ANALYZE output r=yuzefovich a=yuzefovich
We've been tracking "execution time" statistic for most operators (except for vectorized KV-reading ones which get separate "KV time" stat) for many years now, but for some reason we only reported it on the DistSQL diagram. This commit fixes that oversight so that the stat is now included on `EXPLAIN ANALYZE` output when available.
Fixes: #143443.
Release note (sql change): New statistic `execution time` is now reported on EXPLAIN ANALYZE output for most operators. It was previously only available on the DistSQL diagrams (included in `EXPLAIN ANALYZE (DISTSQL)` output).
143859: explain: clarify "network usage" line of EXPLAIN ANALYZE r=yuzefovich a=yuzefovich
In "network statistics" (messages and bytes sent) we only include the network traffic between DistSQL components completely ignoring any traffic from KV layer to SQL layer. In order to clarify this a bit, this commit renames `network usage` top-level information to include "DistSQL" prefix.
Epic: None
Release note (sql change): `network usage` top-level statistic in EXPLAIN ANALYZE output has been renamed to `DistSQL network usage` to clarify that it only tracks network traffic between DistSQL components and completely ignores traffic from KV layer to DistSQL components.
143865: kv/bulk: close bulk-adder-monitor on error r=yuzefovich a=yuzefovich
Previously, we would have left the `bulk-adder-monitor` not closed if we hit an error in `MakeBulkAdder`, and this is now fixed. (The only error possible is actually not enough memory budget to reserve the buffer size.)
Fixes: #143862.
Release note: None
143867: explain: harden RU reporting for read-only queries r=yuzefovich a=yuzefovich
In a recent change 365dfa4 we made it possible to no longer report RU estimate in `planNodeToRowSource` if it wraps a non-mutation planNode. That change was a de-flaking fix that was later super-seded by 66065df, so we can revert the former. I think it makes the code more bullet-proof even though AFAICT we report consumed RUs for only for mutation planNodes.
Also this commit makes some minor fixes to `TestEstimateQueryRUConsumption` which is skipped unconditionally.
Epic: None
Release note: None
143868: memo: check `insert_fast_path` for staleness r=yuzefovich a=yuzefovich
Since we consult the value of `insert_fast_path` session variable in `CanUseUniqueChecksForInsertFastPath` (which is called during the exploration), we need to check the value for memo staleness, and this has been missing.
Epic: None
Release note: None
Co-authored-by: Yahor Yuzefovich <[email protected]>
Copy file name to clipboardExpand all lines: docs/generated/eventlog.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3222,10 +3222,10 @@ Fields in this struct should be updated in sync with apps_stats.proto.
3222
3222
3223
3223
| Field | Description | Sensitive |
3224
3224
|--|--|--|
3225
-
|`NetworkBytes`| NetworkBytes collects the number of bytes sent over the network. | no |
3225
+
|`NetworkBytes`| NetworkBytes collects the number of bytes sent over the network by DistSQL components. | no |
3226
3226
|`MaxMemUsage`| MaxMemUsage collects the maximum memory usage that occurred on a node. | no |
3227
3227
|`ContentionTime`| ContentionTime collects the time in seconds statements in the transaction spent contending. | no |
3228
-
|`NetworkMessages`| NetworkMessages collects the number of messages that were sent over the network. | no |
3228
+
|`NetworkMessages`| NetworkMessages collects the number of messages that were sent over the network by DistSQL components. | no |
3229
3229
|`MaxDiskUsage`| MaxDiskUsage collects the maximum temporary disk usage that occurred. This is set in cases where a query had to spill to disk, e.g. when performing a large sort where not all of the tuples fit in memory. | no |
3230
3230
|`CPUSQLNanos`| CPUSQLNanos collects the CPU time spent executing SQL operations in nanoseconds. Currently, it is only collected for statements without mutations that have a vectorized plan. | no |
0 commit comments