You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After we remove remaining issues in indexer slow down, we may still be hitting latency of just having a single global indexer.
We may want to deploy up to 5 global indexers to give ourselves the best TTFB we can get. Cost to run these is relatively low (few hundred a month), especially if we drop the cache size significantly, which currently looks pretty doable.
Let's hold on doing this till all other optimizations ship, but this may be the next required step.
We'd need to setup Route 53 to intelligently route people to the closest indexer, but this is definitely available as a pretty standard Lambda feature
Alternatively, we can consider putting cloud front in front (as we currently do with content claims), but that will likely be more expensive and less like the ultimate network topology
The text was updated successfully, but these errors were encountered:
What
After we remove remaining issues in indexer slow down, we may still be hitting latency of just having a single global indexer.
We may want to deploy up to 5 global indexers to give ourselves the best TTFB we can get. Cost to run these is relatively low (few hundred a month), especially if we drop the cache size significantly, which currently looks pretty doable.
Let's hold on doing this till all other optimizations ship, but this may be the next required step.
We'd need to setup Route 53 to intelligently route people to the closest indexer, but this is definitely available as a pretty standard Lambda feature
Alternatively, we can consider putting cloud front in front (as we currently do with content claims), but that will likely be more expensive and less like the ultimate network topology
The text was updated successfully, but these errors were encountered: