If you notice that your application size is higher than expected, or you see the size changing frequently when your record catalogue is stable, there are several things you can check.
Review your indexing sources
If your application size is growing more than expected, start by reviewing your build logs. In the Dashboard, navigate to Logs and filter by Build, or retrieve the same information through the API. Open the relevant log entry to view detailed information about the build and identify any unexpected increases in index size.
We also recommend reviewing your indexing processes and data sources. Understanding which systems are contributing records to your indices can help you identify unexpected data growth, duplicate records, or changes in indexing behavior that may be increasing your application size.
Verify your indexing strategy
Once you have identified all of your indexing sources, review how records are being added and updated to ensure you aren't unintentionally creating duplicates.
For example, if the same source data is sent to Algolia multiple times using saveObject without a consistent objectID, each request creates a new record. Over time, this can significantly increase the number of records in your index and contribute to unexpected application growth.
To prevent duplicate records, ensure that records representing the same source data are indexed with a stable objectID so that existing records are updated rather than recreated.
Other causes of unexplained increases
Some indexing operations can cause temporary increases in application size while records are being processed. In many cases, this growth is expected and will resolve once the operation completes.
To help minimize temporary spikes, consider staggering large indexing jobs and reviewing your indexing workflows to ensure that batches do not contain unnecessary or duplicate operations.