[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 01/01: nginx: berlin: Disable narinfo caching altogether.
From: |
Mark H Weaver |
Subject: |
Re: 01/01: nginx: berlin: Disable narinfo caching altogether. |
Date: |
Thu, 21 Jun 2018 16:06:19 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) |
Hi Ludovic,
address@hidden (Ludovic Courtès) writes:
> civodul pushed a commit to branch master
> in repository maintenance.
>
> commit 8379ba4119e51151d93589a6ef57cb159d94e9f2
> Author: Ludovic Courtès <address@hidden>
> Date: Thu Jun 21 11:41:06 2018 +0200
>
> nginx: berlin: Disable narinfo caching altogether.
>
> This is a followup to ebbe4c7f402b6d9cf9c6c2ecf120f49697ab2c49.
>
> * hydra/nginx/berlin-locations.conf (.narinfo): Disable caching.
> * hydra/nginx/berlin.conf: Remove 'proxy_cache_path' directive
> for narinfos.
What's the rationale for this change?
Although 'guix publish' does its own caching, I would expect 'nginx' to
handle cache hits far more efficiently than guix publish. Therefore, I
expect this change to result in higher CPU usage for a given amount of
traffic. I also expect that cache hits on narinfos are an important
common case for our substitute servers.
Does this change bring advantages that outweigh the loss of efficiency?
Mark
- Re: 01/01: nginx: berlin: Disable narinfo caching altogether.,
Mark H Weaver <=