Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[cacher] Frequency of Release checks too high? #8

Closed
xipmix opened this issue Aug 6, 2016 · 1 comment · Fixed by #11
Closed

[cacher] Frequency of Release checks too high? #8

xipmix opened this issue Aug 6, 2016 · 1 comment · Fixed by #11

Comments

@xipmix
Copy link

xipmix commented Aug 6, 2016

The default is 15 seconds. My concern is, if this utility comes into widespread use, won't it put a large load on the upstream servers? The whole point of having an apt-cache is to reduce the load on the upstream servers.
Can you say what the rationale for 15s was? What would be the downsides of setting this to, say 3601s?

@xipmix xipmix changed the title Frequency of Release checks too high? [cacher] Frequency of Release checks too high? Aug 6, 2016
@ymmt2005
Copy link
Member

ymmt2005 commented Aug 6, 2016

The implication in the default 15 seconds was that go-apt-cacher is supposedly used
more often for (private) repositories with frequent updates.

That said, I agree the current default is a bit too short for public repositories.
I think changing the default to 600 seconds is safer.

ymmt2005 added a commit that referenced this issue Aug 15, 2016
from 15 seconds to 600 seconds, fixes #8.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants