Skip to content

Configurable runner script #27

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

Closed
8 of 13 tasks
m-fila opened this issue Jul 16, 2024 · 0 comments · Fixed by #29
Closed
8 of 13 tasks

Configurable runner script #27

m-fila opened this issue Jul 16, 2024 · 0 comments · Fixed by #29
Assignees
Labels
enhancement New feature or request

Comments

@m-fila
Copy link
Member

m-fila commented Jul 16, 2024

Adding a configurable runner script would be very helpful for development and experimenting with different graphs. Currently there is the examples/schedule that is a go-to script for experiments but it's all hard-coded
A new script could have the following arguments:

  • For scheduling:
    • dfg - data-flow graph in GraphML. Should be mandatory argument, it would be nice if this was also a positional argument
    • max-events - total number of events to be processed (currently we have a map of (name, graph) to schedule but we are mostly interested in running the same graph max-events times)
    • slots - number of events that can be processed concurrently (currently MAX_GRAPHS_RUN)
  • For tracing:
    • some option to get and save a gantt plot to a given file
    • some option to get and save a chrome trace to a given file (Add render/show_logs to chrome_trace JuliaParallel/Dagger.jl#540, should be available in Dagger 0.18.13)
    • some option to get dot or other format with the graph supposed to be scheduled
    • the same as above for the executed graphs (storing all of them might be a problem with large max-events)
    • option to write the logs to a txt file
  • For resources (both can be can be specified in julia so I think there is no need to repeat them in a script arguments):
    • procs
    • threads

It would be great if writing files was followed with some information like @info Written <whatever this file is supposed to be> to <filename>

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

Successfully merging a pull request may close this issue.

2 participants