Precompiled Data
When engaging with Blueprints, you may observe that certain data is labeled as 'fast'. This denotes precompiled data, which is designed to enhance the efficiency and speed of blueprints.
Precompiling for Enhanced Performance
To ensure blueprints operate at peak efficiency, we focus on determining the output values of blocks in advance. This involves pre-building functions and blocks, a process that saves execution time in the long run. We refer to this optimized data as precompiled, a term you'll encounter frequently in our documentation.
Each time a blueprint is saved, a signal is sent to all production nodes to discard the existing precompiled data. Additionally, if a blueprint hasn't been executed on a node for at least 6 hours, the node will automatically clear its precompiled information to conserve memory.
We recommend reusing the same block for identical values within a blueprint, as more connections are technically more cost-effective. When dealing with functions, it's beneficial to limit the use of custom object data. For instance, instead of passing an entire object to a function, modal, or queue item, only pass the necessary elements like the guid when that's all you need.
Precompiled value
In the example provided below, you can observe a precompiled value, marked by a green icon. This icon signifies that the value was precompiled during a previous execution and has been stored for efficient use in future operations.
Frequently asked
What does the fast label on blueprint data mean in RUAL?
It marks precompiled data: RUAL pre-builds the output values of blocks in advance to save execution time. A green icon on a value signifies it was precompiled during a previous execution and stored for efficient use in future runs.
When does RUAL discard precompiled data?
Every time a blueprint is saved, a signal tells all production nodes to discard its existing precompiled data, and a node automatically clears precompiled information for blueprints it has not executed for at least 6 hours, to conserve memory.
How do I make my RUAL blueprint faster?
Reuse the same block for identical values instead of duplicating blocks, because more connections to one block are more cost-effective, and pass only the data a function, modal or queue item needs, for example just the guid instead of an entire object.