From: "Philippe Lafoucrière" <lafou@wanadoo.fr>
To: John Nilsson <john@milsson.nu>
Cc: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] portage doc & cache
Date: Sat, 12 Jun 2004 11:01:28 +0200 [thread overview]
Message-ID: <40CAC668.6020100@wanadoo.fr> (raw)
In-Reply-To: <1087001708.28752.28.camel@newkid.milsson.nu>
> Mabey rfc2616 can be of some nice inspiration about caching.
> As always, I refer to Roy T. Fielding's "Architectural Styles and
> the Design of Network-based Software Architectures" as a must read.
I'll take a look at this. As you guys, I don't have enough spare time :p
> You have just described subversion...
> Anyway you might want to experiment with cvsup vs. rsync.
Freebsd is using cvsup. That's the reason for sure.
> Do some experiments and benchmarking. What if only the cache was
> downloaded at sync? Say you have a sql backend for portage, just sync
> that and download the ebuilds on demand.
That's the idea. If you look at debian package system (I know, it's far
different, but ideas can be used on both projects), an update will
only fetch the "cache", and then, package en demand (using apt-get install)
> Personally I like crazy =) I think you should have a better
> understanding of the current system before you criticise it though.
Of course, I don't criticise anything, or anyone. I know the maxim "If
you want it, do it" (Copyright Linus ;p ).
I'll spend sometime if I can to help you guys.
> <quote>rsync is a file transfer program for Unix systems. rsync uses the
> "rsync algorithm" which provides a very fast method for bringing remote
> files into sync. It does this by sending just the differences in the
> files across the link, without requiring that both sets of files are
> present at one of the ends of the link beforehand.</quote>
>
> rsync allready does it's best to only download new information.
There are too many files to consider now in portage. At start, portage
had just a few hundred of files, and rsync was doing its job quite well.
Now portage has more than 80 000 files. Rsync has to consider all of
them, and it's *REALLY* too long + painfull (my laptop is almost
unusable during rsyncing). Sound like a "select * from table" on a test
server with 15 test clients => will break in production environnement
with thousands of clients.
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-06-12 8:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 21:15 [gentoo-portage-dev] portage doc & cache Philippe Lafoucrière
2004-06-11 23:06 ` Nicholas Jones
2004-06-12 0:55 ` John Nilsson
2004-06-12 9:01 ` Philippe Lafoucrière [this message]
2004-06-12 22:25 ` Joseph Booker
2004-06-13 9:45 ` Philippe Lafoucrière
2004-06-13 15:41 ` Nicholas Jones
2004-06-13 18:39 ` Philippe Lafoucrière
2004-06-13 16:17 ` Hasan Khalil
2004-06-13 16:24 ` Joseph Booker
2004-06-13 16:46 ` Jeff Smelser
2004-06-13 22:45 ` John Nilsson
2004-06-20 18:54 ` Philippe Lafoucrière
2004-06-12 9:10 ` Philippe Lafoucrière
[not found] ` <1087033087.16266.8.camel@newkid.milsson.nu>
2004-06-13 9:35 ` Philippe Lafoucrière
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40CAC668.6020100@wanadoo.fr \
--to=lafou@wanadoo.fr \
--cc=gentoo-portage-dev@lists.gentoo.org \
--cc=john@milsson.nu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox