Comment #10 on issue 6626 by megazzt: Cache files are subject to massive fragmentation http://code.google.com/p/chromium/issues/detail?id=6626
"We could do something here but we would be a) increasing the memory footprint due to extra buffering, or b) increasing the wasted disk space due to additional requested-but- not-used space." Many web servers report the size of a requested file in the response headers... this could be used to reserve an exact chunk for the file (Firefox does this for downloads IIRC). If the file ends up being smaller you could just truncate the file when the download finishes. Might want to put a limit on the size you reserve in this way though, although on Windows NTFS has some useful functions that could remove the need for a limit... "sparse files" I think the feature is called? "As a side note, even if we ask for 10 MB from the OS, that doesn't mean we're getting a single chunk of consecutive disk space." True but in that case there's not much one can do, might as well let the OS handle it. Besides getting a slightly defragmented 10MB chunk is still an improvement over a ton of unfragmented 32kb chunks all over the drive, imo. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
