Call for real world benchmarks / use cases
Les mainteneurs répondent en général sous 1 jour
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 2/5
- Temps estimé
- 1-3 heures
- Accessibilité débutants
- 35/100
- Type d'issue
- Documentation
- Clarté
- Plutôt claire
- Activité
- Active
- Stack technique
- rust
- Domaine
- performance
Piste de recherche
Start with the benchmark examples linked in the issue and the contributor guidance. The requested work is to submit a real-world workload with a runnable reproducer, performance details, and one query pattern; contributors should reproduce it and post an analysis before proposing optimizations. The issue provides an example query but no specific workload to implement, so a code change cannot be scoped from this issue alone.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Background
A core value proposition for DataFusion is its performance.
We have lots of benchmarks, but there are many real world use cases that are not covered. For example, queries on STRUCTs / LISTSs and other nested types, but there are many more.
There are many people looking for ways to help, and I want optimization effort to go to workloads people actually run rather than over optimize benchmarks like ClickBench or random things.
Open Call / Request
To that end, I this is an open call for users of DataFusion to file issues describing queries they would like to go faster. Obviously we will not be able to help everyone, however, supplying the information below I think will maximize the chance of making it happen.
Why: Ensure DataFusion stays focused on real users and actual use cases.
Who: Real users of DataFusion -- you are using DataFusion and would like some particular workload to go faster.
How: Open a new issue with the following information
Format
Please provide the following information, concisely (please don't dump multiple pages of AI generated spew with every imaginable detail 🙏 ).
Use case: 1-2 sentences (max) describing how you are using DataFusion. Examples: "Log data analysis from Parquet files on S3", "Full text search engine on local Vortex files", etc.
Local reproducer:
-
Data files. In order of preference:
- a script that generates the data
- a synthetic or anonymized sample with the same shape as your real data
- a public URL to the files
Ideally the data is no more than 10s of GB and the query runs in under a minute on a laptop.
-
A simple benchmark command (ideally a
.sqlfile we can run indatafusion-cli) that runs against your data files. -
1-2 sentences explaining what the data and query mean in English (for example the query descriptions in our current benchmarks)
If you can not share data, the schema and EXPLAIN ANALYZE output may still be useful, but issues with a runnable reproducer are far more likely to get attention and be acted on.
Current performance:
- DataFusion version, and any non-default configuration settings
- How you run DataFusion (e.g. SQL or dataframe, do you have custom optimzer rules, etc)
- Hardware
- Why you think it could be faster (for example, the time another engine takes, or a profile / explain plan showing where the time goes)
Restrictions:
- Only include 1 query or query pattern in each issue (not your whole workload, please) to keep the conversation focused.
Then please post a link to the new ticket below.
For contributors
If you are looking for a way to help, check out any usses
The first thing is not to code (or have your agent code) Instead, you should reproduce reported performance and analyze where the time is going and post a writeup to the ticket. Please include flamegraphs, diagrams, etc , not walls of AI generated analysis.
Then, explore possible optimizations (AI tools are great at this). Review each idea carefully, and if you find one that looks general and improves performance write it up (1 paragraph) explaining the high level optimization, why it works, and what classes of queries are affected.
Example
Here is an example using ClickBench Q22.
Use case: Web analytics over a single Parquet table (ClickBench hits).
Data: 14 GB, 100M rows, 105 columns
wget https://datasets.clickhouse.com/hits_compatible/hits.parquet
Query (q22.sql, run with datafusion-cli -f q22.sql):
CREATE EXTERNAL TABLE hits STORED AS PARQUET LOCATION 'hits.parquet';
SELECT "SearchPhrase", MIN("URL"), MIN("Title"), COUNT(*) AS c, COUNT(DISTINCT "UserID")
FROM hits
WHERE "Title" LIKE '%Google%' AND "URL" NOT LIKE '%.google.%' AND "SearchPhrase" <> ''
GROUP BY "SearchPhrase" ORDER BY c DESC LIMIT 10;
How this matches my real use case: TODO 1-2 sentences
DataFusion Version: 56.0.0
- Langage dominant
- Rust
- Étoiles
- 9.6k
- Forks
- 2.6k
- Merge moyen
- 3 j 4 h
- PR mergées (30 j)
- 345
Préparer son environnement
Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.
- Aucun Dockerfile ni fichier Docker Compose
- Propose un modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de apache/datafusion
-
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
apache/datafusion#27315 · 2 commentaires ·
Les mainteneurs répondent en général sous 1 jour
-
bug
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100
apache/datafusion#27094 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
Substrait consumer doesn't recognise `shift_left` / `shift_right` from functions_arithmetic.yamlPeut-être pris @jonasHanhan l’a pris il y a 9 jours. Ouvertebug
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100
apache/datafusion#27059 ·
Les mainteneurs répondent en général sous 1 jour
-
`ProjectionExprs::project_statistics` computes approximate `Statistics::total_byte_size` ignoring column statsPeut-être pris @joseph-isaacs l’a pris il y a 10 jours. Ouvertebug
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
apache/datafusion#27050 ·
Les mainteneurs répondent en général sous 1 jour
-
physical-plan: decoding an Unnest or Explain node with an unset field panicsPeut-être pris @geoHeil l’a pris il y a 8 jours. Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 75/100
apache/datafusion#26999 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
Toutes les issues de apache/datafusion
Issues similaires
-
P3
Difficulté 2/5 1-3 heures Accessibilité débutants 70/100
HerringtonDarkholme/hd-lang#1770 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 82/100
jonathanong/no-mistakes#3332 ·
Les mainteneurs répondent en général sous 1 jour
-
bug
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
swc-project/swc-next-issues#310 ·
-
bug
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
swc-project/swc-ai-issues#653 ·
-
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
lbjlaq/Antigravity-Manager#3937 ·
Les mainteneurs répondent en général sous 1 jour