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

Improve update performance #799

Closed
bos opened this Issue May 24, 2012 · 2 comments

Comments

Projects
None yet
3 participants
@bos
Copy link
Contributor

bos commented May 24, 2012

(Imported from Trac #809, reported by @bos on 2011-03-07)

I have an automated package build set up using Hudson, and it tries to build my code as often as once every 5 minutes. Right now, that means running cabal update before every build, which takes at least 30 seconds. It would be great if cabal update used the ETag and If-Modified-Since HTTP headers to do conditional fetches of the metadata, so that there would be far less of a performance hit to both the Hackage server and my client.

@bos

This comment has been minimized.

Copy link
Contributor

bos commented May 24, 2012

(Imported comment by @dcoutts on 2011-03-07)

More generally there is the incremental update idea as in ticket #428 so that it'll use much less bandwidth even when there are changes.

This is a rather weaker feature request so not strictly a duplicate. Even so it's probably better to go the whole hog on this one. It shouldn't be that much more work.

thomasdziedzic pushed a commit to thomasdziedzic/cabal that referenced this issue May 20, 2013

23Skidoo added a commit that referenced this issue May 26, 2013

Merge pull request #1341 from gostrc/master
Improve update performance (#799)
@thomasdziedzic

This comment has been minimized.

Copy link
Contributor

thomasdziedzic commented Jun 4, 2013

I think this bug can be closed since my pull request was accepted.

The incremental update ticket #428 is still there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment