Comment 6 for bug 1171047

The SSL negotiation may be an issue, but I'm not sure it explains the 12 minute gap (unless there's something going on that doesn't cause output, which is feasible.)

It may or may not be related that plain transfers are also very slow. They rarely get above 60kB/s, often dropping below that. This especially sucks when a game is pushing a 2GB update. However I'd be surprised if a single operation was pushing enough data to take that long and notification wasn't occurring.

I'm trying it again, and seeing similar long times:

mei 09 22:48:13 Geraakt https://private-ppa.launchpad.net raring/main amd64 Packages
mei 09 22:48:13 Geraakt https://private-ppa.launchpad.net raring/main i386 Packages
mei 09 22:48:22 Geraakt https://private-ppa.launchpad.net raring/main amd64 Packages
mei 09 22:48:22 Geraakt https://private-ppa.launchpad.net raring/main i386 Packages
mei 09 22:48:31 Geraakt https://private-ppa.launchpad.net raring/main amd64 Packages
mei 09 22:48:31 Geraakt https://private-ppa.launchpad.net raring/main i386 Packages
mei 09 22:48:38 Geraakt https://private-ppa.launchpad.net raring/main amd64 Packages
mei 09 22:48:39 Geraakt https://private-ppa.launchpad.net raring/main i386 Packages

this isn't the really long one though, it hasn't got that far yet. The fact that the times group together surprises me too. I imagine it's one source, but given apt doesn't reuse connections and it's the same host, I'd expect a more even spread.

I could get a pcap of all the traffic to private-ppa if that'd be useful. Obviously it'd be a lot of SSL, but the timestamps and connection requests might be interesting when lined up against a log like above.