Difference between revisions of "Cache (LogiX node)"
Jump to navigation
Jump to search
(Created page with "Cache Cache {{:NodeMenu}} <hr> File: LogiX Cache.jpg You will likely Never use this node. It's pretty much depreciated.") |
|||
(12 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
− | [[ | + | <languages></languages> |
− | [[Category: | + | <translate> |
+ | <!--T:1--> | ||
+ | {{Infobox Logix Node | ||
+ | | Name = Cache | ||
+ | | Image =[[File: CacheNode`1Node.png | noframe | 128px | 'Cache' LogiX node ]] | ||
+ | | Input0Type = Object | Input0Name = Value | ||
+ | | Output0Type = Object | Output0Name = Output | ||
+ | }} | ||
+ | |||
+ | <!--T:2--> | ||
+ | The '''Cache''' node can be used for performance optimization. If you have a complex or heavy calculation with result that's read by multiple other nodes, you can place this node at the end. This will make sure that the input is evaluated only once (per evaluation context) and the result reused for the other nodes. In most cases you don't need it and it doesn't change the functionality in any way. At some point in the future this is going to be handled automatically. | ||
+ | |||
+ | == Usage == <!--T:3--> | ||
+ | |||
+ | == Examples == <!--T:4--> | ||
+ | |||
+ | == Node Menu == <!--T:5--> | ||
+ | </translate> | ||
+ | [[Category:LogixStubs]] | ||
+ | [[Category:Generics{{#translation:}}]] | ||
+ | [[Category:LogiX{{#translation:}}|Cache]] | ||
{{:NodeMenu}} | {{:NodeMenu}} | ||
− | |||
− | |||
− |
Latest revision as of 08:07, 19 February 2022
Cache | ||
---|---|---|
Inputs | ||
Object | Value | |
Outputs | ||
Object | Output |
The Cache node can be used for performance optimization. If you have a complex or heavy calculation with result that's read by multiple other nodes, you can place this node at the end. This will make sure that the input is evaluated only once (per evaluation context) and the result reused for the other nodes. In most cases you don't need it and it doesn't change the functionality in any way. At some point in the future this is going to be handled automatically.