My last hackweek project was "melbot", a server-side automated system for running performance tests. This went from being a project to something the performance team now uses heavily. The volume of data it now produces is excessive and problems are easily missed. It's a short hackweek for me due to being on holiday for two of the days but there are three objectives to the hackweek project
- Rename melbot to marvin. The melbot name was a joke that has outlived its usefulness
- Unify the reporting. There was a lot of duplicated code due to initial design mistakes and it is a pre-requisite. This is more on the mmtests side
- Build some analysis that generates a single value representing goodness/badness. This is also more on the mmtest side.
- If 3 works, build a dashboard that displays good/bad over a range of tests and machines. This would then become part of Marvin if it works.
Item 3 is the experimental part, I'm not sure if it's even possible to do it in the general case but it's something I've wanted to try for a long time.
Looking for mad skills in:
Nothing? Add some keywords!
This project is part of:
Hack Week 11
This project is one of its kind!