You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need an empirical method and scale on which to measure the size and time ratings of Mutators. @cpbarker and I drafted a scale for size ratings, but time ratings have proved to be more difficult. The size scale that @cpbarker and I came up with needs to be documented, and agreed upon by the team. An automated script would be very handy for measuring time ratings, and after enough data from existed Mutators is gathered, a scale for time ratings needs be created and documented as well.
Re-write time & size measuring script in python (currently in bash)
Set up a box for time testing
Automate graphing (makes it easier to determine growth rate and assign a rating)
Implement arguments (Number of repeats and mutator to test)
Document time growth rate testing and assignment procedure
Document size growth rate testing and assignment procedure
Automate assigning time and size ratings based off of data
The text was updated successfully, but these errors were encountered:
@capnspacehook to set up a bench marking box. Folder and file glob data depends on disk write speeds, and we need a consistent platform to test them on.
We need an empirical method and scale on which to measure the size and time ratings of Mutators. @cpbarker and I drafted a scale for size ratings, but time ratings have proved to be more difficult. The size scale that @cpbarker and I came up with needs to be documented, and agreed upon by the team. An automated script would be very handy for measuring time ratings, and after enough data from existed Mutators is gathered, a scale for time ratings needs be created and documented as well.
The text was updated successfully, but these errors were encountered: