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
This funny error happens because pysail cannot be build earlier:
note: This error originates from a subprocess, and is likely not a problem with pip.
full command: /ClickBench/sail/myenv/bin/python3 /ClickBench/sail/myenv/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py build_wheel /tmp/tmplwdqskbg
cwd: /tmp/pip-install-lrtuoi63/pysail_b4807127b28440b597dd4db3ec033f35
Building wheel for pysail (pyproject.toml): finished with status 'error'
ERROR: Failed building wheel for pysail
Failed to build pysail
ERROR: Could not build wheels for pysail, which is required to install pyproject.toml-based projects
... which happens because parquet cannot be build successfully:
@alexey-milovidov For a bit of context, I'm one of the creators of Sail. The Python package is intended as a simple way for people to get started quickly, but for production environments we generally recommend building Sail from source.
For the ClickBench script, I chose to build Sail from source via the Python package simply because it kept the benchmark setup straightforward. If I were aiming to squeeze out maximum performance, I would skip PySail entirely.
Because of this, I’m not sure this should fall into the "tuned" category. Otherwise, by the same logic, every Rust-based engine would also be considered "tuned"?
Happy to adjust if you think there’s a better way to keep things consistent across engines.
Imho Joe Average user shouldn't be bothered with compiling any software from scratch. Compiling software is fine for development purposes. In the context of a benchmark, it opens the door for more specific optimizations, e.g. compiling specifically for the target machine (think march=native for GCC) which would be an unfair advantage over other databases (I am not saying that you are doing this EDIT: You aredoing this.).
I would prefer a plain and simple binary install as described in the Sail docs as well.
It will be okay if the official docs use it as the first (preferred) installation method; otherwise, it is a little bit strange.
Installation from source is the first sub-section in the docs. Imo first installation method should generally be geared towards quickly getting started and then immediately after it makes sense to talk about building for production.
Activity
shehabgamin commentedon Nov 12, 2025
Sail 0.4.1 likely resolves this:
#679
rschu1ze commentedon Nov 13, 2025
Running sail 0.41 (added here) on
t3a.smallfails withThis funny error happens because pysail cannot be build earlier:
... which happens because parquet cannot be build successfully:
which is probably because 2 cores and 2 GB DRAM are too little resources.
shehabgamin commentedon Nov 13, 2025
@rschu1ze Oh interesting, I guess building from source becomes problematic on instances with small resources
Although, when optimizing for performance, building Sail from source is the preferred installation method.
alexey-milovidov commentedon Nov 13, 2025
Use the default installation method, recommended in Sail's documentation: https://docs.lakesail.com/sail/latest/introduction/getting-started/
alexey-milovidov commentedon Nov 13, 2025
Otherwise, the system will fall into the "tuned" category.
shehabgamin commentedon Nov 13, 2025
@alexey-milovidov For a bit of context, I'm one of the creators of Sail. The Python package is intended as a simple way for people to get started quickly, but for production environments we generally recommend building Sail from source.
For the ClickBench script, I chose to build Sail from source via the Python package simply because it kept the benchmark setup straightforward. If I were aiming to squeeze out maximum performance, I would skip PySail entirely.
Using:
is essentially the same process used to build any Rust-based engine (for example, DataFusion’s ClickBench script).
Because of this, I’m not sure this should fall into the "tuned" category. Otherwise, by the same logic, every Rust-based engine would also be considered "tuned"?
Happy to adjust if you think there’s a better way to keep things consistent across engines.
rschu1ze commentedon Nov 14, 2025
Imho Joe Average user shouldn't be bothered with compiling any software from scratch. Compiling software is fine for development purposes. In the context of a benchmark, it opens the door for more specific optimizations, e.g. compiling specifically for the target machine (think
march=nativefor GCC) which would be an unfair advantage over other databases (I am not saying that you are doing this EDIT: You are doing this.).I would prefer a plain and simple binary install as described in the Sail docs as well.
alexey-milovidov commentedon Nov 14, 2025
It will be okay if the official docs use it as the first (preferred) installation method; otherwise, it is a little bit strange.
shehabgamin commentedon Nov 14, 2025
@rschu1ze I see, that reasoning makes sense to me.
With that in mind, this:
Can change to this:
A new version of Sail came out, so we can bump the version too.
I'm just getting offline now, but i'm happy to whip up a PR when I'm back online if needed.
shehabgamin commentedon Nov 14, 2025
Installation from source is the first sub-section in the docs. Imo first installation method should generally be geared towards quickly getting started and then immediately after it makes sense to talk about building for production.
https://docs.lakesail.com/sail/latest/introduction/installation/