From 0d0f48375aa6697effbd154b25b116b491b387da Mon Sep 17 00:00:00 2001 From: Joel Rosdahl Date: Sun, 14 Jun 2020 10:43:47 +0200 Subject: [PATCH] =?utf8?q?doc:=20Improve=20wording=20in=20=E2=80=9CSharing?= =?utf8?q?=20a=20cache=20on=20NFS=E2=80=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit (cherry picked from commit 293a9c8fb1b865ed355581d5cf4f90d985c8174f) --- doc/MANUAL.adoc | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/doc/MANUAL.adoc b/doc/MANUAL.adoc index 58e091f23..0b3cd1c71 100644 --- a/doc/MANUAL.adoc +++ b/doc/MANUAL.adoc @@ -1094,15 +1094,17 @@ filesystems), but keep in mind that: * Having the cache on NFS may slow down compilation. Make sure to do some benchmarking to see if it's worth it. * ccache hasn't been tested very thoroughly on NFS. -* If operating system versions is different then cache direct hit will be lesser, - and it will lead to slower cache preprocessor hits. sloppiness config can be set to - system_headers to ignore different system header and increase cache direct hits. - It is recommended to have same operating system version when using cache on NFS - to increase cache direct hits. A tip is to set *temporary_dir* to a directory on the local host to avoid NFS traffic for temporary files. +It is recommended to use the same operating system version when using a shared +cache. If operating system versions are different then system include files +will likely be different and there will be few or no cache hits between the +systems. One way of improving cache hit rate in that case is to set +<> to *system_headers* to ignore system +headers. + Using ccache with other compiler wrappers ----------------------------------------- -- 2.47.2