Brian Harring wrote:
On Thu, Oct 13, 2005 at 10:17:26AM +0200, Nagatoro wrote:
Brian Harring wrote:
Curious about feedback from general usage, emerge -s, emerge -Dup
world, etc. timing runs would be appreciated
portage 2.0.53_rc5 - 3.0-cache-backport-experimental-7
emerge -s portage:
real 0m10.855s
user 0m2.610s
sys 0m0.537s
emerge -Dup:
real 0m40.443s
user 0m18.300s
sys 0m3.465s
Don't spose you could attempt the tests above with the cache patches,
plus the patch I've attached? It adds lastX caching back in, should
reduce sys a _bit_, although personally I'm not expecting a helluva
lot out of it.
Hmm, when trying to update the cache (emerge --metadata) I get this:
---
>>> Updating Portage cache:
Traceback (most recent call last):
File "/usr/bin/emerge", line 2734, in ?
cache.util.mirror_cache(source, cm, pdb.auxdb[porttree_root],
eclass_cache=ec, verbose_instance=noise_maker)
File "/usr/lib/portage/pym/cache/util.py", line 22, in mirror_cache
if not trg_cache.autocommits:
AttributeError: CachingDict instance has no attribute 'autocommits'
---
but if I remove the lastX patch it workes.
portage 2.0.53_rc5 - 3.0-cache-backport-experimental-7 + lastx
emerge -s portage:
real 0m12.891s
user 0m3.030s
sys 0m0.576s
After running this with and without the lastx patch I seem to get
slighly longer times (real and user) with it (~0.5s real and user) and
slightly shorter sys times (~0.2s).
emerge -Dup world:
real 0m38.113s
user 0m18.186s
sys 0m2.916s
And here I seem to get slightly shorter real and sys times but
slightly longer user times (~0.5s real and user, ~0.2s sys).
But the times varies way to much to "prove" this.
--
Naga
--
[email protected] mailing list
