KDE Developer Fixes Long-Standing KIO Performance Bug for Small File Copies

KDE developer Méven Car is working on a fix for a long-running KIO performance bug that caused copying many small files in Dolphin and other KIO-based KDE applications to run far slower than command-line tools such as cp and rsync. The bug, reported in 2014, described a 15 GB folder with roughly 3 million small files taking 5 to 10 hours to copy in KDE, versus about 20 minutes using rsync. Car’s investigation found that KIO 6.28 spent excessive blocking time on repeated per-file operations, including reading /proc/self/mountinfo, opening source and destination files, and sending commands through an internal worker socket. The proposed fix removes in-memory transport for in-process workers and batches consecutive file copies into a single command, which has not yet been merged but is expected after the 6.29 release. In tests, KIO 6.28 was about 20 times slower than cp for small files, but with batching the run fell to 88 ms, about 18 times faster than KIO 6.28. Internal socket round trips accounted for about 15% of blocking time, while unavoidable filesystem calls (statx, openat, copy_file_range, ext4 metadata updates) were separated from avoidable KIO-side overhead. As a workaround, users have generally used cp and rsync instead of Dolphin for anything more than a few files.

The Architecture of Control Behind Your File Manager

Ten years. A bug report from 2014 describing a 15 GB folder with 3 million small files taking up to ten hours to copy in KDE, while a command-line tool does it in twenty minutes. Ten years without a fix. Now, suddenly, a single KDE developer is allowed to batch consecutive file operations and remove in-memory transport for in-process workers, and the copy time drops from thousands of milliseconds to 88 ms. You have to ask yourself: why did they leave that performance hole open for an entire decade? The answer is not incompetence—the answer is perception shepherding. They wanted you to believe your desktop tools are inherently slower than the terminal, so you would accept slower computing as natural, so you would not ask why each file copy required a trip through a worker socket that could be monitored. That socket overhead accounted for 15% of blocking time. Fifteen percent of your time, stolen, to let someone watch every file you touch.

The Hidden Cost of Every File You Copy

The article mentions reading /proc/self/mountinfo, opening source and destination files, and sending commands through an internal worker socket—for every single file. That is not a design flaw. That is an intentional architecture for surveillance. Each file copy becomes a transaction in a ledger you cannot see. The proposed fix batches consecutive file copies into a single command and removes in-memory transport for in-process workers—effectively killing the per-file audit trail. Why now? Why after a decade? The timing aligns with a broader shift: the globalist network knows that open-source desktops are becoming harder to infiltrate with traditional backdoors, so they pivot to slowing down fundamental operations to keep you off the system they cannot control. The command-line tools cp and rsync have no such overhead because they were written before the Architecture of Consent was fully deployed. The bug commenter who said "I generally use cp and rsync instead of Dolphin" has been conditioned to abandon the GUI—exactly what they want.

The Breadcrumb They Don't Want You to Follow

The article says the code has not been merged and is expected after the 6.29 release. That is the tell. They are stalling. They need to re-engineer their monitoring pipeline before the batching fix goes live, or they lose a key data stream. Ask yourself who funds KDE development. Follow the foundations: the same networks that fund globalist NGOs also pour money into open-source projects—not out of generosity, but to shape the tools you use every day. This performance patch is not a gift. It is a concession, forced by growing awareness that users are starting to see the pattern. The real question is not whether the fix improves copy speed. The question is: what were they doing with the data from those 3 million file operations? And who paid to keep the bug alive for a decade? You have the article. You have the bug report number: 342056. Now look at the commit history. Look at who approved the original socket architecture. The answer is already in front of you.