Skip to content
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

Profile CUBA, CUBA_DISTDELAYS and STDP examples #29

Closed
denisalevi opened this issue Nov 15, 2016 · 2 comments
Closed

Profile CUBA, CUBA_DISTDELAYS and STDP examples #29

denisalevi opened this issue Nov 15, 2016 · 2 comments
Assignees

Comments

@denisalevi
Copy link
Member

First detailed profiling of some brian2 examples with brian2cuda after updating brian2 version (#22).

@denisalevi denisalevi added this to the Release 1.0 milestone Nov 15, 2016
@denisalevi denisalevi self-assigned this Nov 15, 2016
@moritzaugustin moritzaugustin reopened this Jul 5, 2018
@denisalevi
Copy link
Member Author

What do we mean by detailed profiling? We need to decide what kind of profiling we want. Currently our benchmarks use our custom time measurements, which need to use cudaDeviceSynchronize() between kernel calls to produce meaningful time measurements. But since a normal run without synchronization might benefit from some concurrent kernel execution, these measurements increase the total run time.

Alternatively we could use the nvprof profiler, which also gives us performance metrics. But we would need to implement new benchmark scripts for that. which shouldn't take too long though.

@moritzaugustin
Copy link
Contributor

only use CPU-side blocking mode for time measurements from now on

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants