About zipping.. Default settings might not really be good idea - i think
that fastest might be even better. Considering that portage tree contains
same word again and again (like applications) it needs pretty small
dictionary to make it much smaller. Decompressing will not be reading from
disc,
Has anyone ever noticed that portage tree contains a lot of md5 hashes,
which are not at all important for using it? I think that it does not make
reliability or functionality smaller any bit if those would all stay in sync
servers - anyway, syncing would go much faster and this tree smaller. What
On Tue, Dec 2, 2008 at 4:42 AM, Tambet [EMAIL PROTECTED] wrote:
About zipping.. Default settings might not really be good idea - i think
that fastest might be even better. Considering that portage tree contains
same word again and again (like applications) it needs pretty small
dictionary to
On Tue, 2008-12-02 at 19:46 +0200, Tambet wrote:
Has anyone ever noticed that portage tree contains a lot of md5
hashes, which are not at all important for using it? I think that it
does not make reliability or functionality smaller any bit if those
would all stay in sync servers - anyway,
It might be that your hard drive is not that much slower than memory, then,
but I really doubt this one ...or it could mean that reading gzip out is
much slower than reading cat - and this one is highly probable. I mean, file
size of gzip.
Actually it's elementary logic that decompressing is
On Tue, Dec 02, 2008 at 07:46:13PM +0200, Tambet wrote:
Has anyone ever noticed that portage tree contains a lot of md5 hashes,
which are not at all important for using it? I think that it does not make
reliability or functionality smaller any bit if those would all stay in sync
servers -
