Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ardiadminguide:lookup [2016/11/20 10:07] optrix |
ardiadminguide:lookup [2018/12/11 02:17] (current) optrix |
||
|---|---|---|---|
| Line 22: | Line 22: | ||
| |12|Comms Lost| | |12|Comms Lost| | ||
| - | etc.. | + | ===Performance Warning=== |
| + | |||
| + | //Technical Section// | ||
| + | |||
| + | Why does ARDI have both an //enumeration// and a //lookup// type? The simple answer is **efficiency**. | ||
| + | |||
| + | When dealing with small numbers of options, it's quite easy to send the complete lookup table out to ARDI clients. When there are only a half-dozen options to choose from, the complete list is trivial to transmit. | ||
| + | |||
| + | However, when the list is significantly larger, it's puts a lot of load on the client and the network. Lookup properties instead push some of this additional work off to the driver, rather than loading-down the server and the client. | ||
| + | |||
| + | Please use enumerations where possible, as a large number of small lookup properties will cause additional server load that will negatively impact performance. | ||