Content deleted Content added
ShelfSkewed (talk | contribs) m Disambiguate Just In Time to Just-in-time compilation |
Disambiguated: hardware → Computer hardware, run-time → run time (program lifecycle phase) |
||
Line 7:
===Advantages===
The main advantage of this method was that the stock of already compiled customer programs ([[object code]]) could be improved almost 'instantly' with minimum effort, reducing [[CPU]] resources at a fixed cost (the price of the [[proprietary software]]). A disadvantage was that new releases of COBOL, for example, would require (charged) maintenance to the optimizer to cater for possibly changed internal COBOL algorithms. However, since new releases of COBOL compilers frequently coincided with [[Computer hardware|hardware]] upgrades, the faster hardware would usually more than compensate for the application programs reverting to their pre-optimized versions (until a supporting optimizer was released).
===Other optimizers using the same concept===
Some binary optimizers seek to reduce only the ''size'' of binary files by eliminating duplicate library modules - without necessarily also improving their performance, while others utilize [[run time (program lifecycle phase)|run-time]] metrics to [[introspect]]ively improve performance using techniques similar to [[Just-in-time compilation|JIT]] compilers.
===Recent developments===
| |||