Answer
Native compilation isn't something IFS itself particularly uses or recommends for typical IFS workloads, for a few reasons: it requires special additional tooling and consideration for how the Installer itself would interact with natively-compiled objects; natively compiled code can't be debugged in the usual way, which is a serious practical risk specifically when trying to diagnose a problem in production; and the performance gains from native compilation are mainly apparent in computation-heavy PL/SQL, like matrix-style number-crunching, rather than the I/O-bound, mostly-plain-SQL-statement style of code that makes up the vast majority of IFS's own business logic, with heavy numeric modules like MRP, MPS, and Costing being closer to plausible exceptions. This means the expected performance benefit for typical IFS custom code and standard IFS logic is likely much smaller than generic native-compilation benchmarks elsewhere might suggest — it remains an idea IFS has experimented with internally but hasn't found enough traction in to formally adopt or recommend.