Results of 1 - 5 of about 5 for spent (0.001 sec.)
- Metrics 12795
- DuckDB provides a set of metrics that can be used to monitor the performance and health of the database. Metrics are named ⟨group⟩.⟨metric⟩ , e.g., query.total_time or operator.timing . The set of collected metrics is controlled with the tr
...er query Metrics Metrics measured over the entire query. Name Type Unit Description query.cpu_time double seconds CPU time spent on the query query.sql string The SQL string of the query query.total_intermediate_rows uint64 rows Cumulative number of i...n query.total_rows_scanned uint64 rows Cumulative number of rows scanned by the query query.total_time double seconds Time spent executing the entire query system Metrics Metrics on system resources, such as memory and threads, used while running the...query. Name Type Unit Description system.blocked_thread_time double seconds Time spent waiting for a thread to become available system.peak_buffer_memory uint64 bytes Peak memory usage of the buffer manager sy... - https://man.mtool.work/duckdb/2.0/dev/metrics.html
- EXPLAIN ANALYZE: Profile Queries 8935
- Prepending a query with EXPLAIN ANALYZE both pretty-prints the query plan, and executes it, providing run-time performance numbers and the actual cardinality (number of rows produced) for every operator. EXPLAIN ANALYZE SELECT * FROM tbl; N
...ote that the cumulative wall-clock time that is spent on every operator is shown. When multiple threads are processing the query in parallel, the total processing time of the q...uery may be lower than the sum of all the times spent on the individual operators. For multi-file reads (e.g., reading multiple Parquet files), the output includes the file nam...─────────────────────────────────────────────────────────╯ Each operator shows the number of rows it produced and the time spent in it. Scan operators also show the number of row groups scanned and any dynamic filters that were pushed into them at run... - https://man.mtool.work/duckdb/2.0/guides/meta/explain_analyze.html
- Profiling Queries 8236
- DuckDB supports profiling queries via the EXPLAIN and EXPLAIN ANALYZE statements. EXPLAIN To see the query plan of a query without executing it, run: EXPLAIN ⟨query⟩; The output of EXPLAIN contains the estimated cardinalities for each opera
...statement runs the query, and shows the actual cardinalities for each operator, as well as the cumulative wall-clock time spent in each operator.... - https://man.mtool.work/duckdb/2.0/sql/statements/profiling.html
- Install Script 8070
- You can install the DuckDB CLI client using an install script. Linux and macOS To use the DuckDB install script on Linux and macOS, run: curl https://install.duckdb.org | bash Click to see the output of the install script. % Total % Receive
...d % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 13209 100 13209 0 0 126k 0 --:--:-- --:--:-- --:--:-- 127k *** DuckDB Linux/MacOS installation script, vers... - https://man.mtool.work/duckdb/2.0/operations_manual/installing_duckdb/install_sc...
- Release Cycle 7887
- This document outlines the DuckDB and core extension release cycle framework. It is intended for developers working on DuckDB extensions to better understand the underlying processes. Overview DuckDB follows Semantic Versioning ( v<MAJOR>.<
...y-codename Description The mid-cycle phase is the most common phase of the release cycle, with about 75% of the time being spent in this phase. It can be seen as business-as-usual , where the upcoming release is still far away and the team is working... - https://man.mtool.work/duckdb/2.0/dev/release_cycle.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work