Improve update performance #799

bos opened this Issue May 24, 2012 · 2 comments


None yet
3 participants

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 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 thomasdziedzic added a commit to thomasdziedzic/cabal that referenced this issue May 20, 2013

@thomasdziedzic thomasdziedzic Improve update performance, see issue #799 547e7a3

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

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

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.

23Skidoo closed this Jun 4, 2013

hvr referenced this issue in haskell/hackage-server Oct 26, 2013


Send etag and last modified times, if possible #10

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