Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feat][Doc] Benchmarking C++/Spark readers with/without filter pushdown #403

Open
lixueclaire opened this issue Mar 15, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@lixueclaire
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Filter pushdown is a sophisticated feature available with C++/Spark readers that has the potential to enhance query performance. It's important to evaluate its effectiveness.

Describe the solution you'd like
To gauge the impact of filter pushdown, I propose using the LDBC dataset to benchmark the performance of reading operations. Specifically, we can measure how efficiently the C++/Spark readers can filter vertices or edges with certain property conditions when filter pushdown is enabled compared to when it is not.

Additional context
This request is in continuation of the discussion in issue #389

@lixueclaire lixueclaire added the enhancement New feature or request label Mar 15, 2024
@SemyonSinchenko
Copy link
Member

SemyonSinchenko commented Aug 12, 2024

I want to start working on Spark benchmark. What do you think guys, should it be a separate project or not? I want to start from basic read/write, read with pushdown, ego-nets.

I see it as a JMH-based benchmark cases, that uses the same data like we are using for tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants