chore(controller): lower set_time_limit now that fetching is concurrent
Providers fetch in parallel now (cost ~= max, not sum), so the old 90s stopgap for the 3-sequential-providers-plus-pagination worst case can come back down toward the 30s default, with headroom for pagination and per-request HTTP timeouts.
This commit is contained in:
@@ -53,6 +53,7 @@ final class GraphController
|
|||||||
$svg = $this->cache->get($cacheKey, function (ItemInterface $item) use ($theme, &$cacheMiss): string {
|
$svg = $this->cache->get($cacheKey, function (ItemInterface $item) use ($theme, &$cacheMiss): string {
|
||||||
$cacheMiss = true;
|
$cacheMiss = true;
|
||||||
$item->expiresAfter(3600);
|
$item->expiresAfter(3600);
|
||||||
|
set_time_limit(30); // ponytail: providers fetch concurrently now (cost ~= max, not sum); GitLab pagination + per-request HTTP timeout (framework.yaml) still need headroom over the 30s default
|
||||||
|
|
||||||
return $this->renderer->render($this->aggregator->aggregate(), $theme);
|
return $this->renderer->render($this->aggregator->aggregate(), $theme);
|
||||||
});
|
});
|
||||||
|
|||||||
Reference in New Issue
Block a user