On 2014-12-02, Jungle Boogie <[email protected]> wrote: > Dear Stuart, > -------------------------------------------- > From: Stuart Henderson <[email protected]> > Sent: Tue, 2 Dec 2014 10:40:22 +0000 (UTC) > To: [email protected] > Subject: Re: Staying -current with cvsup or cvsync > > >> On 2014-11-28, Jungle Boogie <[email protected]> wrote: >>> Hello All, >>> >>> For the last several updates I've applied to my system, I've used plain CVS: >>> cvs -q up -Pd >>> >>> This is pretty slow for some reason, but I understand that's just how CVS >>> works. >> >> I just timed an update of /usr/ports on my laptop at 63 seconds. That's >> fetching >> from a good anoncvs server, with /usr/ports on SSD and mounted like this >> >> /dev/sd1j on /usr/ports type ffs (local, noatime, nodev, nosuid, softdep) > > 63 seconds is quite impressive! I've got a pata drive with only: > (local, nodev)
softdep can help a lot with big cvs updates, especially on disks which are slower to access. Lots of files involved in a ports or src cvs tree (especially ports) so there are a large number of inode changes that need to be written to disk, > How often do you fetch/rebuild? It varies, I probably update the entire ports tree on my laptop once or twice a week, and smaller parts if I'm working on them or if I see an update I want in the commit log. For base, the last full update I did was about 10 days ago, but again I've updated smaller parts more often and I often update the kernel every few days. There will be lots of differences between people (and at different times depending on what they're working on).
