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
Copy file name to clipboardExpand all lines: docs/en/operations/system-tables/trace_log.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,6 +37,8 @@ Columns:
37
37
-`MemorySample` represents collecting random allocations and deallocations.
38
38
-`MemoryPeak` represents collecting updates of peak memory usage.
39
39
-`ProfileEvent` represents collecting of increments of profile events.
40
+
-`JemallocSample` represents collecting of jemalloc samples.
41
+
-`MemoryAllocatedWithoutCheck` represents collection of significant allocations (>16MiB) that is done with ignoring any memory limits (for ClickHouse developers only).
-`query_id` ([String](../../sql-reference/data-types/string.md)) — Query identifier that can be used to get details about a query that was running from the [query_log](/operations/system-tables/query_log) system table.
42
44
-`trace` ([Array(UInt64)](../../sql-reference/data-types/array.md)) — Stack trace at the moment of sampling. Each element is a virtual memory address inside ClickHouse server process.
/// Memory can be allocated while resizing on queue.push_back.
78
-
/// The size of allocation can be in order of a few megabytes.
79
-
/// But this should not be accounted for query memory usage.
80
-
/// Otherwise the tests like 01017_uniqCombined_memory_usage.sql will be flaky.
78
+
79
+
/// Queue resize can allocate memory
80
+
/// - MemoryTrackerDebugBlockerInThread here due to the allocation can hit the limit for MemoryAllocatedWithoutCheck, let's suppress it.
81
+
/// - MemoryTrackerBlockerInThread here because this allocation should not be take into account in the query scope (since it will be freed outside of it)
0 commit comments