Hi Mats,
There is a memcached branch here: https://github.com/ccache/ccache/pull/58
I've been running a previous version of this for years with great success,
and you can see that others also had success with it.
Event for 16 agent, you will probably begin to see performance improvment
compared to
>
>
> that isn't what i meant. i don't care about runtime config options but
> about (1) the code and (2) build time control. fs should remain in the
> source and memcache should be an additional configure flag which allows
> the user to select it at runtime.
>
Ah, ok then we are on the same page
Hi,
I like it very much. I think it adds great value for ccache, and to my old
memcached-only attempt.
I did not realize the use for moxi also as a connection "keep-alive"
mechanism, and a way to hide the syn-ack latency overhead. I think this is
what you mean by "avoid some of the network overhe
>
>
> i don't think getting rid out of the fs makes sense, but having memcache
> be available dynamically as an additional layer sounds fine.
>
It does make a lot of sense for me as I have a high performance network,
which is faster than local harddrive. So I would insist on keeping an
option for
On Thu, Aug 22, 2013 at 2:18 AM, tal zilcer wrote:
> hi,
>
> i recently started using ccache and i have a couple of questions.
>
> 1)i did a little experiment with different values of CCACHE_NLEVELS [..]
according to the build time results it seems it is better to use low
> NLEVELS value. when
