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.

Sign up for GitHub

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

Jump to bottom

Develop performance-regression/acceptance tests #737

Closed
dsunder opened this issue Apr 19, 2017 · 2 comments
Closed

Develop performance-regression/acceptance tests #737

dsunder opened this issue Apr 19, 2017 · 2 comments
Assignees
@ndellingwood
Labels
Feature Request Create new capability; will potentially require voting
Milestone
2017-July-end

Comments

@dsunder
Copy link
Contributor

dsunder commented Apr 19, 2017 •
edited

Major features need to have performance tests. Tests need to be broken down into stages to help isolate diffs.
@dsunder dsunder added this to the 2017-June-end milestone Apr 19, 2017
@hcedwar
Copy link
Contributor

hcedwar commented Apr 19, 2017

Tier 1: Parallel For with Range Policy, Static Scheduling
Tier 2: Parallel Reduce and Scan with Range Policy, Static Scheduling
Tier 3: Parallel For with Team Policy, Static Scheduling
Tier 4: Parallel Reduce with Team Policy, Static Scheduling
Tier 5: Parallel For with Range Policy, Dynamic Scheduling
Tier 6: Parallel Reduce and Scan with Range Policy, Dynamic Scheduling
Tier 7: Parallel For with Team Policy, Dynamic Scheduling
Tier 8: Parallel Reduce with Team Policy, Dynamic Scheduling

@ibaned ibaned added the Feature Request Create new capability; will potentially require voting label Jun 6, 2017
@ibaned ibaned assigned crtrott and ndellingwood and unassigned crtrott Jun 14, 2017
ndellingwood added a commit to ndellingwood/kokkos that referenced this issue Jun 27, 2017
@ndellingwood
Policy performance tests: Added test and sample scripts
6d1a073 
This commit address Github issue kokkos#737
RangePolicy and TeamPolicy tests with nested parallelism added for
benchmarking performance - e.g. compare master vs develop prior

TODO The parallel_scan test fails to compile with Cuda 7.5; this is
either a bug in Kokkos or shortcoming of Cuda 7.5's lambda support.
Depending on which will determine resolution, if necessary.
@ndellingwood ndellingwood mentioned this issue Jun 27, 2017
Merged
@ndellingwood
Copy link
Contributor

PR in with performance tests and sample script to run tests organized by Tier's from Apr 19 comment above.

ndellingwood added a commit to ndellingwood/kokkos that referenced this issue Jun 27, 2017
@ndellingwood
Policy performance tests: Added test and sample scripts
da44a30 
This commit address Github issue kokkos#737
RangePolicy and TeamPolicy tests with nested parallelism added for
benchmarking performance - e.g. compare master vs develop

TODO The parallel_scan test fails to compile with Cuda 7.5; this is
either a bug in Kokkos or shortcoming of Cuda 7.5's lambda support.
Depending on which will determine resolution, if necessary.
ndellingwood added a commit to ndellingwood/kokkos that referenced this issue Jun 28, 2017
@ndellingwood
Policy performance tests: Added test and sample scripts
9205c7b 
This commit address Github issue kokkos#737
RangePolicy and TeamPolicy tests with nested parallelism added for
benchmarking performance - e.g. compare master vs develop

policy_performance: add functor for parallel_scan
ndellingwood added a commit to ndellingwood/kokkos that referenced this issue Jun 28, 2017
@ndellingwood
Policy performance tests: Added test and sample scripts
ec9c151 
This commit address Github issue kokkos#737
RangePolicy and TeamPolicy tests with nested parallelism added for
benchmarking performance - e.g. compare master vs develop

policy_performance: add functor for parallel_scan
@crtrott crtrott closed this as completed Jul 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ndellingwood ndellingwood

Labels
Feature Request Create new capability; will potentially require voting
Projects
None yet
Milestone
2017-July-end
Development

No branches or pull requests
5 participants
@ibaned @hcedwar @dsunder @crtrott @ndellingwood