Getting near to deploying our custom Node app with ROS into production and we’re seeing enormous Realm file size growth server side. We’re monitoring/tracking deployed IoT devices that updates its data frequently: About every 30 seconds.
For just one IoT endpoint (corresponds to one Realm file), there are 12 schemas with a total of about 500 entries for the endpoint. Mix of short strings and ints. Flat file size is well under 100KB, but we’re seeing growth of 50MB per day per Realm Database file (one IoT endpoint). If we look at all our endpoints we want to track, that’s nearly 50 Terabytes per year and isn’t realistic.
The only thing connected to ROS is our servers via GraphQL and the node app that is reacting to realm changes. We’ve turned off the Realm Studio to see if that helped…it didn’t seem to have any impact.
With frequent updating data, I’m guessing that the file is full of transaction logs…but with no clients connected…why does Realm need to store all this history?
In reading other posts, it’s possible that this space is a lot of empty/unused space. What is the best practice here to keep these on-disk file sizes compacted/compressed? Or at the very least, what options do we have to limit the file size here?
ROS v3.1.0 RC1