Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Talking about compression of the ccache cache, ...
On Fri, 2011-09-09 at 11:35 -0500, Norbert Thiebaud wrote:

Well, my boxes are usually cpu bound (even with a fully hot ccache)
and I have plenty of space for my ccache, so that is not that clear a
choice to me.

So, unconditional compression is no good.

you can set that up with an env variable right ? so you can easily
make ccache behave the way you want, 'automatically', for you. (i.e
export CCACHE_COMPRESS=1 in your bashrc)

Yes, it is the existence of the envvar that controls.

Setting it in .bashrc makes a lot of sense in that the relative
availability of I/O capacity vs. CPU capacity does not depend on what
product the user is building.  The use of .bashrc is so easy and
natural (thank you for reminding me about it!) that I think LO should
not even provide a configuration option for compression.

I notice, BTW, that "How to build LibreOffice"
<http://wiki.documentfoundation.org/Development/How_to_build> no
longer says that we automatically enable ccache if it is found on the
system.  Should that statement be added back to the page, now that it
is true?


I don't do that in configure for the same reason we don't change
CCACHE_DIR or the cache dir size.
Using ccache if available is one thing... but trying to
'auto-magically' optimize ccache is another can of worms altogether...

Agree.  Especially so, considering that sometimes a cache may be
shared between different users and different systems.



Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.