PHP Compatibility Checker – plugin too big problem – server load

Problem Situation
PHP Compatibility Checker seems to think that some plugins are too big to check.
It seems to decide “after” it has already been scanning the plugin for a while.
At a guess, this is probably due to the plugin timing the scan, and deciding that it is taking too long.

In any case, I have found that some plugins have been reported as too big to scan on one scan, but not on a following scan. There was no change in the file between the two scans.

So the report should be more accurate and state the real reason why the scan for a plugin was stopped. The scan could report if it taking too long, or if the file was too big.
Or if the server was heavily loaded at the time.

Once the scan of a plugin is stopped, there is no attempt to re-scan it at a later point in the scan (say at the end).

Some Suggestions
1) Possibly gather some metrics to help fine tune the scans
e.g.
ave MB/hour
user scan time that can be tolerated per plugin, per MB, per total scan
2) Allow?Invite the user to confirm a re-scan of plugins that were not completed in their scans.
3) Record the stop point, in a plugin’s scan, and for a total scan, so that restarts from stop points can be done.
4) report the correct reason why a scan is stopped.
5) if scans are actually being stopped because the plugin is too big, then allow the user to set the size limit for them self, either as a general option, or on a plugin by plugin basis.
6) By use of the metrics in (1) estimate the current performance level of the server (shared servers may be temporarily slowed by heavy activity on the other shared sites), and adjust time or size limits in proportion. And make a live report to the user so they know that the scan is going to take longer (or shorter), and why, and be asked how they want the scanner to behave.