-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Add benchmark #126
Comments
I am not very sure what you mean. I guess you want to add tests with a Conv2D in this file, crypto_primitive_provider_test. Am I correct? @gmuraru |
Something like this maybe. |
Ahh..we want to add a benchmark action - like this that would trigger a benchmark test (like doing a feedforward through a ConvNet and will report the time on the graph) |
Okey, I started working on this. Now I understand the idea. I have done a first of learning and experimentation. I have some questions.
|
Also pinging @LaRiffle - he might want to be kept in the loop.
|
Yeah, the results are always stored locally sorry. I have never done a Github Page and I though that it required a different repository. Okey, then I guess that someone will need to create a Github Page. Anyway, with that information and my fork I think I am in good shape to start working. Thanks! |
I think it would be automatically corrected. @aanurraj, on Should I assign you the issue? |
Yeah, assign it to me, why not. I am already working on it. For what I am reading, I think the repository needs a GithubPage (in case you want to be able to visualize it) and a secret token to be able to do a commit with the new benchmarks. https://github.com/rhysd/github-action-benchmark#charts-on-github-pages-1. But the data will be created in the branch gh-pages, inside the dev/bench folder (by default). We can start with that, and if you want we change it. |
You don’t need any secret token! |
True, sorry. Seems to be fixed benchmark-action/github-action-benchmark#1. |
Feature Description
Add a simple convolutional network in the tests where we do a feedforward using
VirtualMachines
.Is your feature request related to a problem?
The text was updated successfully, but these errors were encountered: