public inbox for gentoo-performance@lists.gentoo.org
 help / color / mirror / Atom feed
From: lnxg33k <lnxg33k@gmail.com>
To: gentoo-performance@lists.gentoo.org
Subject: Re: [gentoo-performance] gentoo-performance (sync speedups)
Date: Fri, 20 Jan 2006 19:03:50 -0600	[thread overview]
Message-ID: <43D18876.6080304@gmail.com> (raw)
In-Reply-To: <43D18228.6070802@egr.msu.edu>

Alec Warner wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> lnxg33k wrote:
>> Thanks Alec Warner for the great explanation. It still seems like by not
>> having portions of the tree by using EXCLUDEFORM and deleting the local
>> dirs that you'd save some time in the --metadata part of sync as less
>> ebuilds are available to be checked. Is this simply a wrong misconception?
> 
> The portion that "updates metadata cache" has nothing to do with what
> ebuilds are in the tree.  It simply takes the server-side caches (
> pregenerated ) and sync them into your local cache.  You could RSYNC
> exclude the whole tree and this will still happen for every package,
> since the metadata is generated on the server ( and the server has the
> whole tree ).
> 
> Now if you were to rsync exclude metadata/ you would reduce the
> - --metadata portion...because it wouldn't happen ;)
> 
<snip>

Ah, ok. Hearing it again makes it sound more reasonable. I'll have to watch my 
rsync output a bit more closely. Thanks again for the explanation.
-- 
gentoo-performance@gentoo.org mailing list



  reply	other threads:[~2006-01-21  1:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20  0:40 [gentoo-performance] gentoo-performance Ken Robbins
2006-01-20  2:28 ` lnxg33k
2006-01-20  2:30   ` Chris
2006-01-20  2:50     ` lnxg33k
2006-01-20  3:32       ` Kyle Lutze
2006-01-20  4:39       ` Christopher Bergström
2006-01-20  5:21         ` Jeremy Brake
2006-01-20  5:26           ` lnxg33k
2006-01-20  5:46             ` Michael Liesenfelt
2006-01-20  5:43           ` darren kirby
2006-01-20  6:02             ` Christopher Bergström
2006-01-20  7:44               ` darren kirby
2006-01-20  6:35           ` Alec Warner
2006-01-20  6:53             ` Jeremy Brake
2006-01-20 16:48             ` [gentoo-performance] gentoo-performance (sync speedups) lnxg33k
2006-01-21  0:36               ` Alec Warner
2006-01-21  1:03                 ` lnxg33k [this message]
2006-01-20 13:51         ` [gentoo-performance] gentoo-performance Bill Roberts
2006-01-20 14:43           ` Christopher Bergström
2006-01-23 22:38             ` [gentoo-performance] How to get Maximum performance in Graphics on Nvidia Drivers XFry
2006-01-23 19:57               ` Roman Gaufman
2006-01-23 20:08                 ` prymitive
2006-01-23 20:41                   ` Pierrick Couturier
2006-01-24 19:23                     ` Re[2]: " XFry
2006-01-25  0:07                       ` Pierrick Couturier
2006-01-25  0:13                         ` Chris
2006-01-23 20:02               ` omghaai
2006-01-23 20:04                 ` [gentoo-performance] /proc/* under 2.6 Chris
2006-01-20  3:29     ` [gentoo-performance] gentoo-performance Alex Efros

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=43D18876.6080304@gmail.com \
    --to=lnxg33k@gmail.com \
    --cc=gentoo-performance@lists.gentoo.org \
    /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