-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 shmuel siegel wrote: > The article also hints at our problem. We ARE doing the compression on > the end user side. So the compression is costing us 3 minutes to save 24 > megabytes of transmission. This actually slows things down for most > broadband users. > Since when was yum-presto about time? I thought it was about bandwidth usage. Here, the dorm connections are capped at 600kb/s (well, not a hard cap, but it can be annoying anyways). At one university I know (with over 20k students on the main campus), there is (or was last year at least) a cap at 2GB / week. Go over and you're capped at 56k for the rest of the semester. I can't imagine Fedora on such a restriction (and I have 4 machines to update, 2 with largely non-overlapping package sets, the other 2 are similar and a caching server would help) and that's a lot of students that would be hard pressed to use Fedora at college. CPU time is cheaper than bandwidth these days. Maybe I'm mistaken about what yum-presto was aiming to solve? - --Ben -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iQIcBAEBCAAGBQJKu3NrAAoJEKaxavVX4C1XRJIP/0ELUuNd/35Q+CXePgeJR2HN UnUdp2OyApqTwqWtTQ4sPcICKAcJKo8wct0G3JK11t1x4FOZA/O26Hs815DpzWkj kHzV02MRQpa0B4ZKnMlZ/WDpVrPehi6nwqnxjL5k8g+OuVdSaEXGlQQTG+LK0KER DdRMKKnop/fZEWbTYj1OMf8Nv7KeXW92EPdyaHVJGKOSW+SVi7scXbHHxsSkhqe6 7zG6HvnUt7aNAcH7NMM3dlNDMKJwiU1Q3r266XBcVtu4inogkZ9xwMkmKqr2QMel aReynuAg8tKk6M8Drwbgj7VWLtjZRMjKuICslw3lj+2w0bXMJ20P7g7gTcObp8ki KfjeHTXQZHnQpCAbOsRCUrmNSz3hfyfB3HsaB7DI9Txa05aJva6pis8ajanc0zSe Ob8kvduhDriEdk1sp/3UEng5AYfggr2O5+uTnWsc4pfqJVNwZvPOT0GBnG7XaY/+ YsOo7k2JM0vbL/FEgJPL9Y/h0jgJpGWhZPdVWC+iPOg6uRau7Npso3mbenJXpOz4 9MLb/58HRmoPDTo5PKuWQnenbNzgVyJA3TNUavhihIoVrIhCCnzj5Sh9sharzuVX UKe7K0Xd0mf2s6GCfGqf5f4j14UdySxEC/PT0NP+U18SRWqwKq+llE+iv1gEpIJH ipdaPtQVekcIoM7LKJo4 =it9Q -----END PGP SIGNATURE----- -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
