diff options
| author | Brian Harring <ferringb@chromium.org> | 2011-10-14 02:40:00 -0700 |
|---|---|---|
| committer | Zac Medico <zmedico@gentoo.org> | 2011-10-14 16:50:20 -0700 |
| commit | 1e8870bd45a4e2a9c43e7f112701c6ae84b0fd56 (patch) | |
| tree | 7111ded6176c5a8f4a2b5a39bad04b2f560608ea /pym/portage/eclass_cache.py | |
| parent | 2ed1cb53cc4158af08c22d466b15b9a9a7767212 (diff) | |
| download | portage-1e8870bd45a4e2a9c43e7f112701c6ae84b0fd56.tar.gz portage-1e8870bd45a4e2a9c43e7f112701c6ae84b0fd56.tar.bz2 portage-1e8870bd45a4e2a9c43e7f112701c6ae84b0fd56.zip | |
layout.conf: add git friendly pregenerated cache format
Enabled via cache-format = md5-dict
This format is essentially just flat_hash, using md5 rather than mtime,
and dropping the path component from _eclasses_ entries.
From a speed standpoint, the md5 overhead is ~16% in comparison to mtime,
timed on a modern sandybridge; specifically, validating 29k nodes takes
~8.8s for flat_md5, while the pms norm is ~7.7s.
That said, the cache is /usable/ in places PMS is not; in those cases,
it can definitely be a win since even if the cache is partially old,
it's better than regenerating everything from scratch.
(cherry picked from commit 95ddf97e2f7e7d3f6a072604b2df5f77e9298558)
Change-Id: Ic3561369b7a8be7f86480f339ab1686fddea6dff
Diffstat (limited to 'pym/portage/eclass_cache.py')
0 files changed, 0 insertions, 0 deletions