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

Benchmarks #134

Open
filhodanuvem opened this issue Oct 13, 2021 · 0 comments
Open

Benchmarks #134

filhodanuvem opened this issue Oct 13, 2021 · 0 comments

Comments

@filhodanuvem
Copy link
Owner

The idea of this issue is exactly what we had on #23, I'm duplicating it as an upvote with the hope that we are getting some contribution on hacktoberfest21.

What we expect is to see some numbers on how gitql behaves with big repositories such as kubernetes. Does the queries with filtering take longer to respond?
Some ideas on how this could be achieved:

  • Use the go testing package to create some benchmarks from the source code point of view ( against the function runtime.runQuery() )
  • Any other benchmark tool (pure bash script is also accepted)
  • Run the benchmark on every merge on GitHub Actions, if possible mark the job as allow_failure.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant