Improve planning benchmark tool #17
Labels
No Label
aesthetic
benchmarks
bug
documentation
duplicate
enhancement
help wanted
invalid
question
suggestion
task
wontfix
No Milestone
No Assignees
1 Participants
Due Date
Dependencies
No dependencies set.
Reference: patrick/plasp#17
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
To make the planning benchmark tool more robust, I’d like to improve the following aspects:
Use a Git Repository as the Data Storage
By using a Git repository for storing the benchmark output and log files, we don’t need any further backup plan.
Additionally, this makes it easy to trace issues, as this brings versioning automatically.
Also, the benchmark status can be tracked by looking at the commit history.
Write an Analysis Tool
With a simple Python script, it should be easy to generate YAML files with the interesting information out of the benchmark output.
Render the Analysis Data on a Web Page
The resulting YAML files would then be processed into an HTML view, which could be easily viewed online.