Project

General

Profile

Cleanup #1059

Unify Data Collection in Charm++

Added by Ronak Buch about 3 years ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Tracing
Start date:
05/06/2016
Due date:
% Done:

0%


Description

Currently, things like load balancing, PICS, BigSim, and tracing (for Projections) all collect data in their own unique way. This causes unnecessary duplication of code and data. This will likely get worse in the future as we add more detail for things like heterogeneous load balancing and energy aware scheduling.

Thus, we should move towards a model of unified data collection. One module in Charm++ should collect information in a sort of generic database, and those services that use the data can get it from this unified system. This should help reduce the complexity of the code, memory usage, and overhead and simplify the development of new runtime features.

A wrinkle in this is that it will be a lot of software engineering work for no externally visible impact, but it's work worth doing.

History

#1 Updated by Sam White over 2 years ago

  • Category set to Tracing
  • Target version set to 6.9.0

#2 Updated by Phil Miller almost 2 years ago

Ronak, could you make the scheduling decision on this, and maybe identify incremental subtasks that could be scheduled sooner if the overall thing won't be done so soon?

#3 Updated by Eric Bohm over 1 year ago

  • Assignee set to Ronak Buch

#4 Updated by Ronak Buch over 1 year ago

  • Target version changed from 6.9.0 to 7 (Next Generation Charm++)

Also available in: Atom PDF