Project

General

Profile

Cleanup #1872

Move performance tests and benchmarks from "make test" to a new "make benchmark"

Added by Evan Ramos over 1 year ago. Updated 4 months ago.

Status:
Implemented
Priority:
Normal
Assignee:
Category:
Build & Test Automation
Target version:
Start date:
04/17/2018
Due date:
% Done:

0%


Description

A non-trivial portion of "make test" jobs is spent on performance testing. These tests should be moved to a separate "make benchmark" so that automated unit and integration testing can complete more quickly.


Related issues

Related to Charm++ - Support #2031: Add a new target (potentially benchmarks) for Vesta autobuilds to avoid maximum execution time from exceeding In Progress 11/19/2018

History

#1 Updated by Sam White over 1 year ago

And at least some of the results of "make benchmark" should be plotted online somewhere every night based on some of the autobuilds whose performance we care about tracking. It would be useful for diagnosing performance regressions. We already do this for netlrts charm++ pingpong on the PPL wiki page.

I would want example/ampi/pingpong and tests/charm++/pingpong at a minimum. Potentially some reduction/broadcast tests, Converse/LRTS tests, and maybe some example programs to all have that.

This could be a good Charmworks intern task.

#2 Updated by Eric Bohm about 1 year ago

  • Assignee set to Shane Neary

#3 Updated by Evan Ramos 12 months ago

  • Status changed from New to Implemented

#4 Updated by Eric Bohm 11 months ago

  • Assignee changed from Shane Neary to Evan Ramos

#5 Updated by Evan Ramos 10 months ago

  • Target version set to 6.9.1

#6 Updated by Evan Ramos 6 months ago

  • Target version changed from 6.9.1 to 6.10.0

#7 Updated by Nitin Bhat 4 months ago

  • Related to Support #2031: Add a new target (potentially benchmarks) for Vesta autobuilds to avoid maximum execution time from exceeding added

#8 Updated by Evan Ramos 4 months ago

We should merge the 6.10-targeted Zero Copy patches, and as many other patches under review that add new tests/examples as possible, before I proceed with this reorganization.

Also available in: Atom PDF