Update Apr 12, 2023 - It seems that Windows 11's poor performance may be due to conflicting BIOS/OS settings when dual-booting. We are investigating... Additionally, I have corrected the version of Windows 11 in the post from Home to Professional.

Update Apr 27, 2023 - Upon further investigation, it appears that the low efficiency of Windows on my laptop may be caused by a combination of factors, including a recent Windows 11 update, the MSI motherboard, and potentially the dual-boot configuration (e.g. with a disabled UEFI secure boot). Despite trying to adjust some settings in the BIOS, I was unable to improve the performance with Windows. While I have not yet decided to reinstall Windows due to time constraints, it seems to be the most viable solution to fix this issue. I may also consider downgrading to Windows 10. It's important to note that while the Linux timings in the benchmark are accurate, the Windows timings should not be taken as reliable due to the underlying issues. I will keep you updated on any progress and improvements once I have the time to reinstall Windows. Thank you for your understanding.

In this blog post, we explore the use of two SQL engines, and specifically their Python API, for querying files. The engines in focus are :

They both support SQL queries and prioritize the efficiency of analytical SQL queries. To evaluate their performance, we conducted the widely-used TPC-H benchmark on a laptop with a dual-boot Linux/Windows setup. We ran the same queries on the same hardware, applied to the same files, with the same libraries on both operating systems, namely Windows 11 Professional and Linux Mint 21.1 - based on Ubuntu 22.04 Jammy Jellyfish. Our findings include a comparison of the performance of each engine on Parquet and native files, allowing us to measure the performance gap between the two platforms.

The chosen scale factor of 10 corresponds to a dataset of modest/medium size. Let us list the different data files.


The TPC-H data used in this benchmark is generated using the DuckDB TPC-H extension and saved into :

  • Parquet files with default compression "snappy" and row group size 122880
  • an hyper database file
  • a duckdb database file

A scale factor of 10 is used for data generation. The benchmark comprises 8 tables. Each table is stored in a separate Parquet file. Here's a brief overview of each table:

Table nameRow countParquet file size
region51.0 kB
nation252.2 kB
supplier100 0008.0 MB
customer1 500 000126.3 MB
part2 000 00069.5 MB
partsupp8 000 000453.3 MB
orders15 000 000620.8 GB
lineitem59 986 0522.7 GB

The lineitem table is the largest, with about 60 million rows. The .duckdb database file has a size of 2.6 GB, while the .hyper database one is around 4.5 GB.

System information

The queries are executed on a laptop with the following features:

CPU : 12th Gen Intel© Core™ i9-12900H - 10 cores
RAM : 32 GB
Data disk : Samsung SSD 980 PRO 1TB

Package versions:

Python          : 3.11.0 | packaged by conda-forge  
DuckDB          : 0.7.2-dev1381  
TableauHyperAPI : 0.0.16638  

Files attachment to the engine

Parquet files

The Parquet attachment process is chosen in a way that the data is not scanned, being almost instantaneous.

  • Hyper

The Parquet files are attached to the Hyper process as temporary external tables:

CREATE TEMPORARY EXTERNAL TABLE region FOR 'path-to/table.parquet'

Here is a description of this attachment process from the Hyper SQL reference:

CREATE TEMPORARY EXTERNAL TABLE will create a new temporary external table, enabling to refer to external data [...] in a SQL query as if it was stored in a Hyper table [...]. However, no data will be stored in Hyper. Instead, Hyper will read from the external source whenever the external table is accessed in a query.

  • DuckDB

The Parquet files are attached to DuckDB as views:

CREATE VIEW region AS SELECT * FROM read_parquet('path-to/table.parquet')

Native file formats

For the native file formats, the database files are given as an argument to the connection constructor.

  • Tableau Hyper API
hyper = HyperProcess(telemetry=Telemetry.DO_NOT_SEND_USAGE_DATA_TO_TABLEAU)
conn = Connection(
  • DuckDB Python API
conn = duckdb.connect(database='path-to/data.duckdb')

Query execution time

In the following sections, we report the elapsed time for each of the 22 TPC-H queries. To ensure accuracy and reduce the impact of fluctuations, we executed each query three times and recorded the best elapsed time out of the three runs.

We did not include fetch time in the elapsed time. We only measure the query execution time. The data is fetched in a second step in order to check the number of returned rows.

DuckDB engine on the duckdb file


DuckDB engine on the Parquet files


Hyper engine on the hyper file


Hyper engine on the Parquet files


Total TPC-H run

We executed the entire TPC-H benchmark, consisting of 22 queries, on both operating systems and recorded the best elapsed time out of three runs. The resulting total Elapsed Time [E.T.] in seconds, is shown in the table below:

Engine - file typeLinux E.T. (s)Windows E.T. (s)
DuckDB - duckdb7.68811.923
DuckDB - parquet9.09614.784
Hyper - hyper2.7733.831
Hyper - parquet5.89610.625



Our results showed that both engines were more efficient on native file formats compared to Parquet files, with Hyper outperforming DuckDB on this specific TPC-H benchmark. Additionally, we observed that the total elapsed time on Windows was on average 40-80% longer than on Linux.