# Ignition Edge Local Storage Limit: What Happens When 10 Million Data Points Are Reached?

**URL:** <https://forum.inductiveautomation.com/t/ignition-edge-local-storage-limit-what-happens-when-10-million-data-points-are-reached/104469>\
**Category:** Ignition\
**Tags:** ignition81, database, edge\
**Created:** [March 31, 2025, 5:42pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-local-storage-limit-what-happens-when-10-million-data-points-are-reached/104469 "2025-03-31T17:42:38Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [March 31, 2025, 10:56pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-local-storage-limit-what-happens-when-10-million-data-points-are-reached/104469/7 "2025-03-31T22:56:43Z")

</div>

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.

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-edge-local-storage-limit-what-happens-when-10-million-data-points-are-reached/104469)._