| 1 |
The twirl twirl is cache updating - it happens after any files that are synced scroll by and after it says updating cache. Sync isn't the problem. It's cache updating and that has been brought up in previous threads. Maybe portage NG will address this. |
| 2 |
|
| 3 |
|
| 4 |
> |
| 5 |
> From: Tom St Denis <tom@×××××××××××××.net> |
| 6 |
> Date: 2004/04/12 Mon PM 05:21:56 GMT |
| 7 |
> To: gentoo-dev@l.g.o |
| 8 |
> Subject: Re: [gentoo-dev] Idea for the portage maintainers |
| 9 |
> |
| 10 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 11 |
> Hash: SHA1 |
| 12 |
> |
| 13 |
> On April 12, 2004 01:19 pm, Norberto Bensa wrote: |
| 14 |
> > Tom St Denis wrote: |
| 15 |
> > > I started using gentoo [~60k files in portage] to now [~80k files in |
| 16 |
> > > portage] it's definitely not just a linear amount slower. |
| 17 |
> > |
| 18 |
> > rsync isn't slow. "emerge --sync" is slow in the portage cache updates |
| 19 |
> > stage (I really want to know what portage cache update does :-/ ) |
| 20 |
> |
| 21 |
> Syncs can be slow too. Sometimes they zoom but sometimes it will say things |
| 22 |
> like |
| 23 |
> |
| 24 |
> 200 files ...... |
| 25 |
> |
| 26 |
> and twirl..... and twirl......and twirl...... |
| 27 |
> |
| 28 |
> Point is portage is useable and works decent. Updating is a bitch and |
| 29 |
> occasionally a "world" update takes way too long [to get the package list]. |
| 30 |
> It's a manner of being scaleable. Portage isn't. |
| 31 |
> |
| 32 |
> Tom |
| 33 |
> -----BEGIN PGP SIGNATURE----- |
| 34 |
> Version: GnuPG v1.2.4 (GNU/Linux) |
| 35 |
> |
| 36 |
> iD8DBQFAetA0sP+tEsHHY0ARAuJIAJ9jfAozHPtz2o49wiNQdni1FYU5FgCZAefS |
| 37 |
> +qb63BEv19W73J6HN6v06WA= |
| 38 |
> =CRvw |
| 39 |
> -----END PGP SIGNATURE----- |
| 40 |
> |
| 41 |
> -- |
| 42 |
> gentoo-dev@g.o mailing list |
| 43 |
> |
| 44 |
> |
| 45 |
|
| 46 |
|
| 47 |
-- |
| 48 |
gentoo-dev@g.o mailing list |
Archives