Concurrent indexing operations amplify memory consumption

Running concurrent indexing operations (e.g., initial bulk import alongside application updates) causes memory usage to spike significantly within 1-2 hours. Even with MEILI_MAX_INDEXING_THREADS=1 and memory limits configured, concurrent updates from multiple sources can push memory consumption to 25-31GB when limits are set to 20GB.

During initial bulk indexing or large reindex operations, disable concurrent updates from applications or other sources. Use MEILI_EXPERIMENTAL_MAX_NUMBER_OF_BATCHED_TASKS to limit concurrent batch processing. Wait for bulk operations to complete before enabling routine application updates. Monitor memory continuously during large indexing operations.