In my project architecture, I will have an Ignition Standard application with a configured database and another Ignition Edge application, whose tags should be historized in the Standard application's database. They will be connected via the Gateway Network, and the settings in 'Remote History Sync Settings' have already been configured to point to the Standard's historical data provider. This communication and storage are working properly.
My question is: What happens when the local storage limit of 10 million data points in the Edge application is reached? Will it discard all stored data, leaving them only in the Standard database? Does it follow a FIFO principle? Where into the Ignition Edge gateway the data is storage?
It will drop incoming history values (entirely, not forwarding either) until the daily pruning operations clears some space, then stop when that is exhausted again. IIRC.
Don't allow your Edge scope to expand to hit the limit. If there is any possibility at all, convert to standard.
Do you know what's the size of each datapoint?
Why does that matter? (Numbers are 8 bytes, strings can be bigger.)
Pruning is by age, not disk space. Points over 35 days old will be discarded, and if your system had stopped at 10 million, the quantity pruned is the space you have for more.
It's for I buy the PC that will run the Edge app. Where did you find this number? I looked for it a lot, but I couldn't find.
The historian stores floats and doubles as double (8-bytes) and integral types as long (8-bytes). With some overhead, you can expect 24-32 bytes per point in history.
As currently implemented:
No later than every 60 seconds, the edge historian runs a maintenance task that finds the oldest timestamp in the historian, and then deletes all data older than (not equal to) that timestamp.
There is no logic I can see to evict new incoming data eagerly, so you absolutely could exceed the row "limit" for some period of time until records are evicted.
The tags.history.InternalHistorian.Engine logger on debug or trace would be informative to follow, OP.