system.tag.storeTagHistory practical limit on tags

Ignition
1

Is there a practical limit to the number of tags the system.tag.storeTagHistory can import? I have a project where I want to pull in data from a remote meter and files include a months data and about 30,000 lines, importing 10 tags. My first attempt imported the data, but the import took about an hour since I was calling the system.tag.storeTagHistory function for every line of data. I can put it all into one call by just appending the data and tag list, but I thought there’s probably a point where it’s better to do multiple calls. Is there a limit here I should be aware of. I can try to run 300,000 points, but I figured it there’s probably an optimal number of data points.

Also, another question about the storeTagHistory method. It appears if you try to import the same file twice it won’t import the data, is that correct? If so, that’s a nice feature, just want to determine if I need to prevent that in my scripting.

2

I would be sure to run any script from gateway scope (not the script console), so you can avoid an RPC hop that'll just add latency and challenges to the script.

I would be okay with up to 1e6 points in one go, but would be hesitant about much more than that. In theory nothing would go wrong, Java lists can accept billions of elements, in practice you're likely to hit some kind of issue going too much higher.

3

Paul,

Thanks for the quick reply as usual. I modified the script to run ~6,000 points at a time and the script went from importing in 1 hour to about 10 seconds. Good to know you think that 1M points should be fine. It’s running as a button script in the client in Vision and works fine that way. The application does require it to be in the client since a remote client will be where the file will be imported from.