-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Sun, Dec 21, 2008 at 8:00 AM, Eric Kow wrote: > On Sun, Dec 21, 2008 at 00:28:01 -0500, Gwern Branwen wrote: >> So I'm happy to announce that raw performance, at least, no longer >> seems to be a problem! > > Thanks for keeping us in touch with these developments! > >> homepage http://www.haskell.org/http/ provides an example 'get.hs'. I >> installed the new HTTP, compiled get.hs with it, and ran a bulk >> download with it: >> >> gw...@craft:33333~>time wget -q >> http://www.haskell.org/ghc/dist/current/dist/ghc-6.7.20070401-i386-unknown-linux.tar.bz2 >> && time ./get >> http://www.haskell.org/ghc/dist/current/dist/ghc-6.7.20070401-i386-unknown-linux.tar.bz2 >> > ghc.bz2 && diff ghc-6.7.20070401-i386-unknown-linux.tar.bz2 ghc.bz2 >> && du -h ghc-6.7.20070401-i386-unknown-linux.tar.bz2 ghc.bz2 && rm >> ghc-6.7.20070401-i386-unknown-linux.tar.bz2 ghc.bz2 >> =wget -q 0.06s user 0.43s system 2% cpu 23.032 total >> ./get > ghc.bz2 3.10s user 0.67s system 15% cpu 24.518 total >> 22M ghc-6.7.20070401-i386-unknown-linux.tar.bz2 >> 22M ghc.bz2 > > Did you also try with the old HTTP package?
There was no need to; from when I was cabal fetch'ing Hackage, I know old HTTP used up 25% of CPU, several percent of RAM, and still took a while for even small tarballs. Performance would be even worse on a 22M file, and time-wise, nowhere near 20 seconds. >> I don't recommend trying to switch to HTTP right now, because as I >> said, I have no idea whether HTTP can handle Darcs's SSH and proxy >> needs. But this is worth noting for the future. > > Good foresight. I don't think SSH needs factor into this at all. But isn't one of the things curl provides ssh pipelining or whatever? > I remember Justin Bailey once submitted a patch to switch completely to > HTTP and I very enthusiastically supported it, only to be stilled by > wiser voices. Then one year later, I moved to the UK where all academic > institutions are apparently behind a proxy server, and where HTTP > basically just broke for me. Sure learned my lesson there! Indeed. Features can often seem unnecessary - until you need them. On the plus side, I've seen grumbling about cabal-install not handling proxies, which may motivate HTTP support. - -- gwern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREKAAYFAklOd1MACgkQvpDo5Pfl1oI4WQCfenYpMYDuohT/K31pY5sSXCZQ sysAn2RbMFGa+zFxuWc8p2UJF+nLcagA =zmQY -----END PGP SIGNATURE----- _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
