Zeronet files are highly fragmented on my drive (500 fragments per 500MB file)

Someone already reported that it helped them to speed up the Zeronet after defragmenting their Zeronet drive.
I am using this Zeronet instance for more than 2 years from version 2 to latest version 3.
And i have found that many files are highly fragmented, i mean like for example 500 fragments per 500MB file, reported by [Defraggler](https://www.ccleaner.com/defraggler) software.

some examples:
chart.db-wal, 54MB, 622 fragments
content.db-wal, 1GB, 234 fragments
content.db, 1GB, 10 fragments only (maybe due to recent rebuilding the file or such?)
ZeroMe.db, 46MB, 413 fragments
ZeroTalk.db, 35MB, 348 fragments
most fragmented file is one KopyKate video 1GB bigfile, 10 065 fragments.

Maybe no wonder why my HDD is maxed out for many minutes when starting ZN..

Defragmenting is slower than i thought. It taking days and i selected just fraction of files.

Is there any room for improving file handling, so the fragmentation is lower? Maybe there is already an optional feature to preallocate space to a file, i do not know. But i guess this won't be ideal since zeronet is badly made to retain content that is incomplete (no seeder) and it would mean much space wasted for incomplete files? Just publishing my thoughts there.

@HelloZeroNet

Start by examining the reported fragmentation in chart.db-wal, content.db-wal, content.db, ZeroMe.db, ZeroTalk.db, and the KopyKate video file. Compare how incomplete and rebuilt files are retained, then determine whether a file-handling change can reduce fragmentation without unnecessarily reserving space. Done means a measured improvement and coverage of the incomplete-content tradeoff.

Escrito por el modelo de indexación a partir del texto del issue.