Big files

[jeevan]

Do you think tha big files (like system images, big archives and so on) should be fully defragmented, on a standard run?

When a big file is split, say, into 2 big parts -
isn't it sometimes better to leave the file as it is - instead of moving one part to join the other?  Usually in these cases, the usage of the file is limited (- in resoration processes or such), and my guess is that it can be left as it is.. no?

Please give me your thoughts on this -
And if you think the same - couldn't there be a configuration parameter that sets a threshold in size for different processing of large files

Thank you!  

[jeroen]

Thanks for sharing your thoughts, I appreciate it! Yes, it's not very useful to defragment very big files, the gain does not outweigh the effort. In the next major version of JkDefrag this will be possible, because there will be a small scripting language that will make just about anything possible, including the skipping of a file when it has no fragments of less than a specified size. This will never be default, though, because users expect (and demand) a defragger to fully defrag all files.

[jeevan]

Thanks for replying so quickly


this is great news
Can you tell me when is that next major version expected to be released?

bye
:j

[jeroen]

I am working on it... at least a month. There will be a new v3 release first.