<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Resource-Tracing on IOPS</title><link>https://iops.gitlabpages.inria.fr/tags/resource-tracing/</link><description>Recent content in Resource-Tracing on IOPS</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 30 May 2026 20:28:38 +0200</lastBuildDate><atom:link href="https://iops.gitlabpages.inria.fr/tags/resource-tracing/index.xml" rel="self" type="application/rss+xml"/><item><title>Measuring the runtime overhead of an I/O interception library</title><link>https://iops.gitlabpages.inria.fr/blog/toto-overhead-analysis/</link><pubDate>Sat, 30 May 2026 00:00:00 +0000</pubDate><guid>https://iops.gitlabpages.inria.fr/blog/toto-overhead-analysis/</guid><description>&lt;blockquote>
&lt;p>This study is part of our paper &lt;strong>&amp;ldquo;TOTO: Transparent I/O Tuning for HPC Applications&amp;rdquo;&lt;/strong>, accepted at &lt;strong>ICS 2026&lt;/strong> (International Conference on Supercomputing, Belfast, July 2026). The overhead measurements below were produced with IOPS.&lt;/p>
&lt;/blockquote>
&lt;p>When you intercept I/O system calls to analyze application behavior, how much overhead do you actually add? That&amp;rsquo;s the question we needed to answer for &lt;a href="https://gitlab.inria.fr/hpc_io/toto">TOTO&lt;/a> (Transparent and Online Tool for I/O), a library that hooks into I/O calls via &lt;code>LD_PRELOAD&lt;/code> to provide runtime analysis of parallel file system access patterns.&lt;/p></description></item></channel></rss>