-
Notifications
You must be signed in to change notification settings - Fork 30
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
benchmark action? #426
Labels
new feature
New feature or request
Comments
I remember it now, it's Raphtory: |
Not a bad idea
…On Mon, Jul 24, 2023, 7:37 PM Maxime Lucas ***@***.***> wrote:
I remember it now, it's Raphtory:
https://pometry.github.io/Raphtory/dev/bench/
—
Reply to this email directly, view it on GitHub
<#426 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAILYAE7PF4HVUBLBBTPA2LXR2XFDANCNFSM6AAAAAA2V44LRY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I haven't been able to get this working over several PRs. This won't be fixed for quite a while unless we get dedicated development time for this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I saw a library (can't remember which one) that had automated benchmarks: there was a graph, automatically updated with each PR/commit, that showed the time taken to run certain core functions. We could implement this for a few functions, to see if our core functions are getting faster/slower with new changes. I can't remember how they did it in practice.
What do you think?
The text was updated successfully, but these errors were encountered: