NATIVIZATION
NATIVIZATION
.
- There have been numerous efforts to nativize ninja through the years. One example, with LIVE-1, from user <@748517221608980631> - see this post: https://x.com/intaxTR/status/1737586471874236578
- While LIVE-1 fluidsim was already running on the GPU, the LIVE-1 system in general was CPU-bound (multiple heavy functions implemented in blueprints), and it made sense to nativize these functions.
- On the contrary, in LIVE-2, the most heavy parts have been lifted from the blueprint architecture, and implemented in the core Niagara System, running on the GPU. LIVE-2 is GPU bound.
- A recent user effort by <@263384635717844992> shows: nativized LIVE-2 blueprints consume ~15% less resources on the CPU. The nativized test setup eating 0.95 ms, while the original eating 1.15 ms (see attached picture and video):