Use no caching mode for copy/move(=copy to a new media and remove) files operations

[mc-butler]

Important

This issue was migrated from Trac:

Origin	https://midnight-commander.org/ticket/2194
Reporter	birdie (aros@….com)
Mentions	gotar@….pl

For file(s) copy operation, please, consider using Linux syscall madvise()/fadvise() with DONTNEED parameter not to clog system RAM with unnecessary file caching. In absolutely most circumstances you copy file but you don't want these files to be cached.

Something like:

[X] Don't cache files being copied

PS This option does apply to "Move file(s)" operation when a new destination is a different media/FS/VFS.

[mc-butler]

Changed by ossi (@ossilator) on May 13, 2010 at 12:17 UTC (comment 1)

again, i disagree with a user-visible option. the mode should be simply automatically entered when the total size of the operation (i.e., sum of all file sizes) exceeds the smaller value of a) a certain percentage of the system's physical memory and b) possibly some fixed number representing a reasonable working set. this also fits the actual usage pattern, as it is more likely that a small amount of data is going to be used again soon than a big one.

[mc-butler]

Changed by birdie (aros@….com) on May 13, 2010 at 13:08 UTC (comment 2)

I was afraid MC developers would be against implementing it, but if there's a consent, I believe this feature could be enabled unconditionally.

[mc-butler]

Changed by gotar (gotar@….pl) on May 26, 2010 at 19:49 UTC (comment 3)

• Cc set to gotar@….pl

I'd like to have this as an option, because there's no heuristic that can guess if I need such files or not in a time. The only unquestionably case is file size>RAM (I've got Compute Totals disabled, so when sum of the files exceeds RAM it's already too late to worry aboud cache).

[mc-butler]

Changed by angel_il (@ilia-maslakov) on Jul 5, 2010 at 20:41 UTC (comment 4)

• Milestone changed from 4.7.3 to 4.7

[mc-butler]

Changed by birdie (aros@….com) on Mar 19, 2011 at 8:37 UTC (comment 5)

• Milestone changed from 4.7 to 4.8

In case someone thinks about implementation, it's very simple: for source files we have to use fadvise() or madvise() call.

[mc-butler]

Changed by andrew_b (@aborodin) on Jun 18, 2015 at 18:37 UTC (comment 6)

• Milestone changed from 4.8 to Future Releases
• Branch state set to no branch