[ALOY-366] Alloy compile benchmarking with process.hrtime()
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | Medium |
| Status | Resolved |
| Resolution | Fixed |
| Resolution Date | 2012-11-30T18:11:02.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Alloy 0.3.3, 2012 Sprint 24 |
| Components | XML |
| Labels | n/a |
| Reporter | Tony Lukasavage |
| Assignee | Unknown |
| Created | 2012-11-05T20:42:19.000+0000 |
| Updated | 2018-03-07T22:25:43.000+0000 |
Description
Would be good to have more insight into what are the most processor intensive sections of the alloy compile process. Will make it easier to focus efforts on speeding up that process. It may not seem critical now, but as the complexity of projects grows and the introduction of rapid deployment techniques (like TiShadow) are introduced, the compile time will more evident.
Benchmarking is in place and can be used to check where the overhead is in the compile process