Speed up issue creation for clash tests
Currently when syncing clash tests with the issue tracker, the great majority of time is spent creating issues, which is done at a rate of roughly 1.5-2 seconds per issue on a brand new top-end Alienware laptop with Revizto using over 50% of the CPU. With over 200 clash tests on the project, this translates to roughly 2-6 hours to run clashes and export issues and makes me always think twice about whether I can afford to do it that day. The data associated with each issue cannot possibly be large enough to truly need a full second or more worth of processor time, so it seems like there should be a way to significantly optimize the speed of the issue creation process.
-
The processing time is not for the data, but to create the snapshot image that gets created when a clash is turned into an issue. The first time an issue is created will take the most processing time, but you can adjust the subsequent markup settings so minimize the need to update the screenshots.
Please sign in to leave a comment.
Comments
1 comment