Is there a compilation time difference between #include <filename.h> and #include “path/to/file/filename.h”?
<p>It seems that the compilers usually implement <code>#include "path/file.h"</code> by firstly searching a path relative to the currently processed source file folder.</p>

<p>So the question is: how does it influence in practice the compilation time when using <code>#include</code> with quotes versus triangular brackets?</p>

<p>The question is only for the case when the <code>"path/to/file/filename.h"</code> is a relative path to the currently processed header, because otherwise it would behave similar to <code>#include &lt;…&gt;</code>.</p>

<p>It seems that the correctly set <code>#include "…"</code> should be faster for your own files than <code>#include &lt;…&gt;</code> in a large project (500 files or more).</p>

<p><strong>Edit</strong>: Other questions about difference between <code>#include "…"</code> and <code>#include &lt;…&gt;</code> don't seem address compile time. Also, the standard is vague but most compilers do use <code>"…"</code> to search in the current folder first.</p>

<p><strong>Edit2</strong> Reworded the title and the question. I'll accept the answer for any of these C++ compilers: Visual Studio, Intel, Clang, Gcc.</p>