I wonder if anyone ever considered using memcached as an optional backend for ccached?

Here is the issue we're considering. In our C++ project we have a number of developers doing their own local compilations. When any updates occurs (e.g. they update to the latest source code from scm) the compilations are the same for all the machines. Sure ccache is great when you re-do the compilation, but here the compilation being re-done on a number of machines. Using memcached would allow us to have a truly distributed cache that would both help developers and machines in the build farm to speed up work.

What do you guys think?

-- Henrik

ccache mailing list

Reply via email to