I think it's time to refactor the functionality for cache files. We now run into issues when we try to load a cachefile created half a year ago, because certain timings or other fields are missing. Cache files are also used by multiple tools, such as the dashboard, so it makes sense to properly define them.
In terms of code we could group all related methods into a single object and module, as everything related to cache files is now in util.py.
It would also be good to properly define the format of cachefiles using a JSON schema with a version number and functionality to automatically convert cache files created using earlier versions of Kernel Tuner to newer versions.
I think it's time to refactor the functionality for cache files. We now run into issues when we try to load a cachefile created half a year ago, because certain timings or other fields are missing. Cache files are also used by multiple tools, such as the dashboard, so it makes sense to properly define them.
In terms of code we could group all related methods into a single object and module, as everything related to cache files is now in util.py.
It would also be good to properly define the format of cachefiles using a JSON schema with a version number and functionality to automatically convert cache files created using earlier versions of Kernel Tuner to newer versions.