Sounds like the issue was just co-location of search index + other transactional data in the same table. If you had a table acting as your search index only the

Sounds like the issue was just co-location of search index + other transactional data in the same table. If you had a table acting as your search index only then would insert lag on that table matter? I could maybe see connections piling up, but with proper batching I bet it'd be fine.