- 최신
- 최다 투표
- 가장 많은 댓글
This is known as "cache pre-warming." Without significant additional information, it's difficult to recommend the best approach for you. However, I doubt that trying to pre-warm the cache will solve the problem. You would need to know where the majority of your users are in order to pre-warm the correct layers of cache. You also run the risk of objects aging out of cache before a user makes a request.
You might find that Origin Shield provides a better experience, if your users are highly globally distributed.
If you haven't already, I recommend reading this blog post which discusses caching strategy, including pre-warming and Origin Shield. It is targeted toward Gaming customers, but is equally relevant to your use case.
If your static content doesn't change between deployments, I strongly suggest that you try to (a) use an S3 bucket to store and serve the static content, and (b) don't change URIs unless the content also changes.
Finally, you may wish to review the docs on optimizing caching.
