Allow user to configure the analyses they want to see about esmf-profiler

[rsdunlapiv]

We need to leave this one open since we have not yet implemented command line parameters for the user to define the analyses they want. But it is not part of a MVP.

[rsdunlapiv]

The user also needs to point the tool to the directory containing the binary (CTF) trace. So the commands above would have an additional argument such as:

$ ./esmf-profiler --load-balance=depth:4 /path/to/trace/directory

[rsdunlapiv]

Error checking will be needed:

$ ./esmf-profiler --memory=type:rss,pet:16  /path/to/my/tracedir

ERROR: A memory profile was requested for PET 16, but there is no memory information in the trace.

[rsdunlapiv]

@rlongio any thoughts on this?

[ryanlong1004]

Sorry for the delay.

Yes, these can all be implemented in the user layer rapidly once the backend logic is finished. It has an API that will allow the user to specify the data they need (filters, etc.) and how many layers depth to go, so if there is a cookie cutter high chart you'd like to use we can get something visually together quicker.

On a side note, after working with a larger binary trace, I did some profiling as the execution time was near 30 minutes. I was able to get that down to less than 5, but it required some refactoring (ie time in bt2 library is expensive).

I expect to finish this by today, or at least have a working MVP.

Regardless, this week I'm going to start sticking static data in the front end to explore some visuals.

The requested features will be either in the first iteration or will be put in as tasks for the second.

[rsdunlapiv]

Sounds good. Good work reducing the time. Some of the time in bt2 is just an artifact of file system access, so we may have limited options in optimizing that side, especially for large traces. However, that is not a showstopper as the user will have the expectation of waiting to post-process large traces.

For your first iteration, you are essentially delivering this, even if the CLI is not set up:

$ ./esmf-profiler --load-balance=depth:2  /path/to/trace

[ryanlong1004]

@rsdunlapiv Can we close this issue?