November 2017 Codechecker Performance Report

This is the fourth post in the series of posts detailing Codechecker, specifically on scale, performance and security aspects. You can read all the posts here in our codechecker posts.

Our effort in parallelizing the running of test cases has been helping us, but given that we are running it for a sample set of our submissions, we are yet to see the true potential of the parallelism. The average turn around time is expected to go down further in upcoming months.

Note: We lost a good amount of data (just the log data and not the actual run results) during this amount. The total number of submissions is misleading and not a true indicator of what happened in this month.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.