[TIMOB-12995] CodeProcessor: Investigate estimating runtime
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | Low |
| Status | Closed |
| Resolution | Won't Fix |
| Resolution Date | 2016-08-24T20:05:39.000+0000 |
| Affected Version/s | Release 3.0.0 |
| Fix Version/s | n/a |
| Components | Code Processor |
| Labels | n/a |
| Reporter | Bryan Hughes |
| Assignee | Chris Barber |
| Created | 2013-03-07T22:16:44.000+0000 |
| Updated | 2017-03-20T17:28:01.000+0000 |
Description
There is a lot of desire for the code processor to provide runtime estimates. It's not possible to accurately determine time, because that would involve me solving the Halting Problem and winning the Nobel Prize in Mathematics. That said, there *may* be a rough correlation between project size and runtime. We can do a statistical analysis on a bunch of customer apps to see if the number of AST nodes in a project vs runtime of said project to see if there is a strong enough correlation between size and runtime to give a rough estimate.
Code processor is dead.
Closing ticket as code processor is no longer supported.