@mavenlin, I observed no significant difference among pure CPU timer, CPU timer with cudaDeviceSynchronize, and cudaEvent_t based GPU timer. Are these what you called weird results?

Reopen to simplify future benchmark works.

Please rebase on the latest dev and we'll merge. Thanks.

@shelhamer, it has been rebased and polished with the newly added cpplint.

So sorry, but this needs another rebase because of a complicated merge. If it's any consolation, this has prepared the reconciliation of the MKL and non-MKL versions of Caffe and brought in support for DAGs, improved documentation, and a better organization of the project.

We are adopting a new development strategy that will not have a constant need for rebasing. It will be documented shortly, but the bottom line is that we will no longer rewrite the history of dev.

I am glad that Caffe is approaching version 1.0. The workflow that I used to rebase on the most recent merge is as follows.

git remote update upstream
git checkout -b Timer upstream/dev
git cherry-pick ...[first commit of this issue]
git cherry-pick ...[second commit of this issue]
...
git push -f origin Timer:cuda_timing

Absolutely clean history.

@shelhamer, this utility class is rebased and tested again. Please merge it for those who are interested in benchmarking run time. Thanks!

@kloudkl Thanks! We're catching up on PRs now, so hope to merge lots of the new developments soon.