Search Shortcut cmd + k | ctrl + k
Search cmd+k ctrl+k
1.0 (stable)
My Workload Is Slow

If you find that your workload in DuckDB is slow, we recommend performing the following checks. More detailed instructions are linked for each point.

  1. Do you have enough memory? DuckDB works best if you have 5-10GB memory per CPU core.
  2. Are you using a fast disk? Network-attached disks can cause the workload to slow down, especially for larger than memory workloads.
  3. Are you using indexes or constraints (primary key, unique, etc.)? If possible, try disabling them, which boosts load and update performance.
  4. Are you using the correct types? For example, use TIMESTAMP to encode datetime values.
  5. Are you reading from Parquet files? If so, do they have row group sizes between 100k and 1M and file sizes between 100MB to 10GB?
  6. Does the query plan look right? Study it with EXPLAIN.
  7. Is the workload running in parallel? Use htop or the operating system's task manager to observe this.
  8. Is DuckDB using too many threads? Try limiting the amount of threads.

Are you aware of other common issues? If so, please click the Report content issue link below and describe them along with their workarounds.

About this page

Last modified: 2024-07-20