Comment 28 for bug 651482

(In reply to comment #31)
> Ok, yeh. I hadn't realized the yum working parts was so fast already ... was
> the first test with 3.2.8 or 3.0.l?
>

The slower one was 3.0.1 the faster one 3.2.17

> Post depsolving there's work we can do in yum, but I'd guess that most of the
> work actually needs to be done in rpm. Yum stages are roughly:
>
> 1. init - read configs. etc.
>
> 2. Run command
> . Possibly download any metadata
>
> 3. If command is doing install/remove/update/etc. do a depsolving run
> . Possibly download any metadata
>
> 4. Do package downloads
> . We basically do "for pkg in pkgs: download(pkg)"
> . This is also not non-piplined, so each pkg add the latency of the request
> response.
>
> 5. Call "run rpm transaction", this is all inside rpm.
>
>
> ...AIUI from your last post you are getting to #4 in ~2m, and then taking over
> 3hrs for #4 and #5.

Indeed #4 takes not so long as I use a local http server but pipelined downloads will speed things up.