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
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.
The text was updated successfully, but these errors were encountered:
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:
runtime.runQuery()
)allow_failure
.The text was updated successfully, but these errors were encountered: