Results of 1 - 8 of about 8 for allocator (0.002 sec.)
- jemalloc 12561
- On supported platforms, DuckDB replaces the system's memory allocator with jemalloc . jemalloc is statically linked into DuckDB and cannot be installed or loaded during runtime. For technical reasons, we used to distribute jemalloc as an ex
...s -DENABLE_JEMALLOC=0 . macOS and Windows On macOS and Windows, jemalloc is not available. DuckDB uses the system's memory allocator on these platforms. Configuration Environment Variables The jemalloc allocator in DuckDB can be configured via the DUCKDB_...hreads By default, jemalloc's background threads are disabled. To enable them, use the following configuration option: SET allocator_background_threads = true; Background threads asynchronously purge outstanding allocations so that this doesn't have to be... - https://man.mtool.work/duckdb/2.0/internals/jemalloc.html
- Handle Results 10989
- Overview Beyond the standard JDBC ResultSet , the DuckDB driver can hand results to Apache Arrow , stream large results instead of materializing them, and expose raw columnar data chunks. This page covers each of these result-handling optio
...ngs. Each batch is loaded in turn, and its vectors are read from the VectorSchemaRoot . import org.apache.arrow.memory.RootAllocator; import org.apache.arrow.vector.ipc.ArrowReader; import org.duckdb.DuckDBResultSet; try (var conn = DriverManager.getConne...= conn.prepareStatement("SELECT * FROM generate_series(2000)"); var resultset = (DuckDBResultSet) stmt.executeQuery(); var allocator = new RootAllocator()) { try (var reader = (ArrowReader) resultset.arrowExportStream(allocator, 256)) { while (reader.load...ther table. import org.apache.arrow.c.ArrowArrayStream; import org.apache.arrow.c.Data; import org.apache.arrow.memory.RootAllocator; import org.apache.arrow.vector.ipc.ArrowStreamReader; import org.duckdb.DuckDBConnection; import org.duckdb.DuckDBResultS... - https://man.mtool.work/duckdb/2.0/clients/java/result_handling.html
- Configuration 9308
- DuckDB has a number of configuration options that can be used to change the behavior of the system. The configuration options can be set using either the SET statement or the PRAGMA statement . They can be reset to their original values usi
...ystem (locale) timezone access_mode Access mode of the database ( AUTOMATIC , READ_ONLY or READ_WRITE ). VARCHAR automatic allocator_background_threads Whether to enable the allocator background threads. BOOLEAN false allocator_bulk_deallocation_flush_thr...eshold If a bulk deallocation larger than this occurs, flush outstanding allocations. VARCHAR 512.0 MiB allocator_flush_threshold Peak allocation threshold at which to flush the allocator after completing a task. VARCHAR 134217728B allo...ry depends on them. BOOLEAN true binary_as_string In Parquet files, interpret binary data as a string. BOOLEAN false block_allocator_memory Physical memory that the block allocator is allowed to use. This memory is allocated once, never freed, and cannot... - https://man.mtool.work/duckdb/2.0/configuration/overview.html
- Environment 9308
- The environment where DuckDB is run has an obvious impact on performance. This page focuses on the effects of the hardware configuration and the operating system used. Hardware Configuration CPU DuckDB's officially supported architectures a
...re, it's recommended to use a Linux distribution with glibc for performance-oriented workloads when running DuckDB. Memory Allocator If you have a many-core CPU running on a system where DuckDB ships with jemalloc as the default memory allocator, consider...enabling the allocator's background threads .... - https://man.mtool.work/duckdb/2.0/guides/performance/environment.html
- Out of Memory Errors 7988
- DuckDB has a state of the art out-of-core query engine that can spill to disk for larger-than-memory processing. We continuously strive to improve DuckDB's scalability and prevent out of memory errors whenever possible. That said, you may s
...oryException Most of the time DuckDB runs out of memory with an OutOfMemoryException followed by a message from the memory allocator. For example: Out of Memory Error: failed to pin block of size 256.0 KiB (476.7 MiB/476.8 MiB used) OOM Reaper (Linux) Man... - https://man.mtool.work/duckdb/2.0/guides/troubleshooting/oom_errors.html
- Building Extensions 7627
- Extensions can be built from source and installed from the resulting local binary. Building Extensions To build using extension flags, set the BUILD_EXTENSIONS flag to the list of extensions that you want to be built. For example: BUILD_EXT
...XTENSIONS (see Linking Extensions ). Special Extension Flags BUILD_JEMALLOC This flag controls whether the jemalloc memory allocator is linked into DuckDB. Unlike TPC-H and TPC-DS, jemalloc is not an extension. It is only supported on 64-bit Linux, where... - https://man.mtool.work/duckdb/2.0/dev/building/building_extensions.html
- Profile and Monitor 7392
- Overview The JDBC driver exposes several ways to observe a running or completed query: cancelling and timing out queries, polling query progress, retrieving profiling output, and emitting memory-usage events through Java Flight Recorder . T
...supplied identifier, the jdbc_jfr_memory_monitor value. tag String DuckDB memory tag, such as BASE_TABLE , HASH_TABLE , or ALLOCATOR . dbAddress long Native address of the DuckDB instance, a stable per-instance identifier. memoryUsageBytes long Bytes curr... - https://man.mtool.work/duckdb/2.0/clients/java/profiling.html
- DuckDB_% Metadata Functions 7030
- DuckDB offers a collection of table functions that provide metadata about the current database. These functions reside in the main schema and their names are prefixed with duckdb_ . The resultset returned by a duckdb_ table function may be
...TABLE , PARQUET_READER , CSV_READER , ORDER_BY , ART_INDEX , COLUMN_DATA , METADATA , OVERFLOW_STRINGS , IN_MEMORY_TABLE , ALLOCATOR , EXTENSION . VARCHAR memory_usage_bytes The memory used (in bytes). BIGINT temporary_storage_bytes The disk storage used... - https://man.mtool.work/duckdb/2.0/sql/meta/duckdb_table_functions.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work