-
Notifications
You must be signed in to change notification settings - Fork 2
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
Graph Times #24
Comments
To further expand on the above, In the latest series of tests (22/11/16) the reference timings are inconsistent with those obtained by myself. I have seen a case where code hasn't been touched at all, and the graph has shown a substantial speed-up |
Also @Szypicyn did your last test produce graphs? I only have the tarball pushed to my repo, but no graphs. |
See #25 about the lack of graphs - there should be new ones based on a fresh Regarding the timing, pay careful attention to exactly what the spec says I'm (hopefully) measuring that metric - are you sure that is what you are measuring, |
@m8pple I'm measuring Would it be possible to add in a reference line just so we can know what the speed-up is compared to the reference? |
I used the logs too and the times match the times show in the excel sheet. However the times dont match the times shown in the graphs. I think the axis of the graphs is off. @m8pple, @jeremych1000 could that be the case? |
@pm1113 I think that is the case too. If you look in all.log in the tarballs,
Doesn't match too. |
Sorry, hadn't realised this was still active. I mis-understood the question, I thought this was between people seeing I'd only looked at the graphs as a relative measure of performance, I think it is simply the scale of the graph is off by 1000, so probably |
Hello, @m8pple, Is it possible to push graphs for the final implementations ? We'd like to see how much what we have done today is useful. |
Hello,
I was wondering how you are timing the code.
I am consistency getting times that are about 100-1000 times greater than what my individual graph shows me.
Best,
Pranav
The text was updated successfully, but these errors were encountered: