| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
hello folks. with portage .51 my machine takes 40-45 minutes to update |
| 5 |
metadata after a sync or by running 'emerge metadata'. ferringb |
| 6 |
suggested removing calls to portage_locks.lockfile() and |
| 7 |
portage_locks.unlockfile() in /usr/lib/portage/pym/portage_db_flat.py |
| 8 |
and sure enough, cache update times returned to a respectable 6-8 |
| 9 |
minutes. any ideas as to how to debug this slowdown? a profile |
| 10 |
generated using: |
| 11 |
|
| 12 |
for x in 1 2 3; do time /usr/lib/portage/bin/pemerge.py metadata \ |
| 13 |
- --quiet --nospinner &> /dev/null; done |
| 14 |
|
| 15 |
is at: <http://dev.gentoo.org/~rajiv/tmp/prof.bz2> |
| 16 |
|
| 17 |
machine specs: |
| 18 |
dual p3 933, 1gig ram |
| 19 |
quantum atlas V scsi drives |
| 20 |
/var, /tmp are reiserfs on lvm partitions |
| 21 |
|
| 22 |
-----BEGIN PGP SIGNATURE----- |
| 23 |
Version: GnuPG v1.2.3 (Darwin) |
| 24 |
|
| 25 |
iD8DBQFBkjwmnt0v0zAqOHYRAhtpAJ0UxM43xLCb9/F2khOltOELxnT2XwCfRIB+ |
| 26 |
qMktyLh+YyawngD27ShMf2k= |
| 27 |
=JLdw |
| 28 |
-----END PGP SIGNATURE----- |
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
gentoo-dev@g.o mailing list |
Archives