![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Much faster...
Oct. 28th, 2005 02:09 pmI faced the daunting task of updating all my PC's running Gentoo Linux (because a new version of Gimp is out) -- and it looks like I would most likely kill my bandwidth repeatedly. But as usual, I would dread updating the laptops because Portage cache is very slow to update on them.
So, I try http-replicator and python-cdb (I already have a local rsyncd mirror). The former would conserve bandwidth similar to what I did in Slackware (although I just NFS-mounted it's cache) -- http proxy. The latter actually puts the portage cache in a simplistic database instead of a filesystem mapping abstraction.
The difference is night and day. Updating Protage's cache just ZOOMS on my laptops and sub-half-Ghz systems. It doesn't wedge itself at 50% and trudge though that muck. It speeds through like it's not time for a lunch break just yet.
Now for compiling...
So, I try http-replicator and python-cdb (I already have a local rsyncd mirror). The former would conserve bandwidth similar to what I did in Slackware (although I just NFS-mounted it's cache) -- http proxy. The latter actually puts the portage cache in a simplistic database instead of a filesystem mapping abstraction.
The difference is night and day. Updating Protage's cache just ZOOMS on my laptops and sub-half-Ghz systems. It doesn't wedge itself at 50% and trudge though that muck. It speeds through like it's not time for a lunch break just yet.
Now for compiling...
