<div class="gmail_extra">On Wed, Dec 5, 2012 at 8:58 AM, Kiss Gabor (Bitman) <span dir="ltr"><<a href="mailto:kissg@ssg.ki.iif.hu" target="_blank">kissg@ssg.ki.iif.hu</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":19d">DESCRIPTION<br>
realpath() expands all symbolic links and resolves references to /./,<br>
/../ and extra '/' characters in the null-terminated string named by<br>
path to produce a canonicalized absolute pathname. The resulting path-<br>
name is stored as a null-terminated string, up to a maximum of PATH_MAX<br>
bytes, in the buffer pointed to by resolved_path. The resulting path<br>
will have no symbolic link, /./ or /../ components.<br></div></blockquote></div><br>This is going to cause a LOT of stat() calls: O(commands * average dir depth)</div><div class="gmail_extra"><br></div><div class="gmail_extra">
I see your point, but it's probably better to do trivial string manipulations that don't hit the filesystem.</div><div class="gmail_extra">The whole point of rrdcached is to defer and collate I/O.<br></div><div class="gmail_extra">
<br></div><div class="gmail_extra">If you feel strongly about it, I encourage you to benchmark it with a non-trivial number of files (500,000) and command rate (1k/sec).</div><div class="gmail_extra"><br></div><div class="gmail_extra">
-- <br></div><div class="gmail_extra"> kevin brintnall<br><br>
</div>