In this code from BenTen:
https://usethinkscript.com/threads/...ort-resistance-indicator-for-thinkorswim.158/
Is this known to improve performance and reduce calls to the server?
Is there any other benefit for creating a local variable other than reducing server calls (like reducing variable lookups)?
The variable itself is used both for a single last value and as an IDataHolder when aggregated, such as highest(vHigh, n).
Does the script actually loads the IDataHolder for the entire chart once per render? What happens when a new bar arrives?
Which IDataHolders benefit from it? Do combinations like HL2 also need it, or are they calculated on the client from High and Low?
How does this work when the data holders are used with parameter, like
Ruby:
def vHigh = high; # creates the variable vHigh. Use of the variable reduce data calls to tos iData server
Is this known to improve performance and reduce calls to the server?
Is there any other benefit for creating a local variable other than reducing server calls (like reducing variable lookups)?
The variable itself is used both for a single last value and as an IDataHolder when aggregated, such as highest(vHigh, n).
Does the script actually loads the IDataHolder for the entire chart once per render? What happens when a new bar arrives?
Which IDataHolders benefit from it? Do combinations like HL2 also need it, or are they calculated on the client from High and Low?
How does this work when the data holders are used with parameter, like
high("SPX")
?
Last edited: