Don&#x27;t forget the Pi (generally) uses flash. So seek speeds are irrelevant.<p>If you&#x27;re writing the following in 1ms:<p><pre><code>    Apr  4 22:50:59 heating kernel: [14572.940927] Unhandled prefetch abort: breakpoint debug exception (0x002) at 0x00008438
</code></pre>
By my count that&#x27;s ~1 kilobit.<p>That means that you&#x27;re writing to flash at ~1 Mb&#x2F;s. (~125KB&#x2F;s) That&#x27;s slow, to put it mildly. (~5% of what it should be, according to <a href="http:&#x2F;&#x2F;ozzmaker.com&#x2F;2012&#x2F;12&#x2F;27&#x2F;how-to-test-the-sd-card-speed-on-your-raspberry-pi&#x2F;" rel="nofollow">http:&#x2F;&#x2F;ozzmaker.com&#x2F;2012&#x2F;12&#x2F;27&#x2F;how-to-test-the-sd-card-speed...</a> ) I could see that kind of speed if it was causing a disk seek every write (although if it was doing that you&#x27;re probably using the wrong file system), but again, the Pi uses flash.<p>So what gives? Is there braindead sync behavior that&#x27;s causing it? Is it hitting a pathological case in the flash controller? Or what?<p>(For that matter: is there a file system that is optimized for log files?)