Origin-pull merging can help increase the cache hit rate, so as to lower the load pressure during peak hours like big online promotion events.
Description
When multiple users request for the same resource that is not cached on the cache node, all requests are forward to the origin, leading to soaring bandwidth and connections. A slow or failed origin response that could affect access experience may even occur if the origin server reaches the performance limit.
When origin-pull merge is enabled, only one request is forwarded to the origin to retrieve the requested resource. Other similar requests are hold till the resource is ready on the cache node.
The following figure shows how this feature works. Three requests are sent to the same cache node requesting for the same resource. The first request is forwarded to the origin. The resource is then returned to the requester and cached on the cache node. Now, other awaiting requests can get the resource from the cache.
Limits
1. It only supports response status code 200, 206 and 304.
