Multitasking - while copying and moving (job queue)
Multitasking - while copying and moving (job queue)
Hello, I am a longtime user of freeCommander and I do enjoy the continuing progress made by the program.
One aspect I have been missing is the ability to copy large files and then keep on working with FC without having to wait for the large file transfer to be finished. I have the impression FC is using the built-in windows tools for actually carrying out the transfers and it does not seem to be able to multi-task or queue such processes.
Perhaps I am missing something? If not, this would be most important missing FC feature fo rme.[/b]
One aspect I have been missing is the ability to copy large files and then keep on working with FC without having to wait for the large file transfer to be finished. I have the impression FC is using the built-in windows tools for actually carrying out the transfers and it does not seem to be able to multi-task or queue such processes.
Perhaps I am missing something? If not, this would be most important missing FC feature fo rme.[/b]
-
- Posts: 4
- Joined: 18.01.2008, 22:17
Technically speaking, multi tasking copy operations will be faster only on different physical drives, on the same drives it will slow the copy process considerably (it's all about the hard drive discs reaching the next data block position).Mr-Fly wrote:Same here,
Would speed up copying a lot, especially when copying small files.
Regards
Thorsten
However it's nice (essential to me) to have a different thread on copy while you browse your computer for another file.
P.S.
I would really appreciate a feedback from one of the devs if this is even being considered.
Regards
daat99
I always try to help ;)
Sometimes I don't know how :(
Sometimes I don't know how :(
Where I see this is when copying over the network.
If you have a lot of small files, the performance really goes down a lot.
A multi-copy would help there a lot, while HDD is not an issue there.
Maybe the function should differentiate between copying locally and remote.
Regards
Thorsten
If you have a lot of small files, the performance really goes down a lot.
A multi-copy would help there a lot, while HDD is not an issue there.
Maybe the function should differentiate between copying locally and remote.
Regards
Thorsten
Using FC under: Win10 German (2004+), Server 2016, Server 2019 + Onedrive
Assuming your file server (or the computer that shares the files) doesn't limit the bandwidth per connection (most lan servers doesn't, it only happens on the internet) then opening multiple threads for copying will just stretch the same physical resource again.Mr-Fly wrote:Where I see this is when copying over the network.
If you have a lot of small files, the performance really goes down a lot.
A multi-copy would help there a lot, while HDD is not an issue there.
Maybe the function should differentiate between copying locally and remote.
Regards
Thorsten
Maybe it won't be your local hard drive but it will be either your server physical parameters or your lan limits.
The only real (physical) reason multi threaded copy/move operations are beneficial is the ability to keep doing what you're doing while it copies the files.
Starting multiple copy operations won't speed up the copy process but it will make it easier to handle.
It'll also make it easier to recover from copy errors where you don't have the appropriate permissions and the copy process stops unexpectedly.
In that particular situation it's best to copy each folder in its own process and then handle the problematic folder while the rest is being copied.
Again, it will never make copying faster, but it'll definitely make it a lot easier
P.S.
I hope you read this post as it is intended (to be beneficial and constructive) rather then rude (or destructive).
If you have some questions you can reach me in my icq/aim/msn (available via my profile).
Keep in mind that due to time differences and me working most of the day that you may get a real slow response, so if you need to log out just ask the full question and I'll reply when I get back.
Regards
daat99
I always try to help ;)
Sometimes I don't know how :(
Sometimes I don't know how :(
See also older thread:
http://forum.freecommander.com/viewtopic.php?t=584
To bypass all Windows copy/move limitations (especially when error occurs on one of the files) it is very important so the copy/move process may continue even if one file fails - no matter the reason.
To bypass all Windows copy/move limitations (especially when error occurs on one of the files) it is very important so the copy/move process may continue even if one file fails - no matter the reason.
Omer.
Free Commander is sooo good already, all the recent additions are adding only niceties (for my personal needs).
The only really important feature lacking (in my eyes) is for FreeCommander to use its own robust and queued filehandling, so that copying large files or multiple files does not imply automatically an extendended coffee break.
I certainly cannot complain about FreeCommander
(....Just found another thread discussing Teracopy etc; it seems like the native file copying is somewhere on the to-do-list) .
The only really important feature lacking (in my eyes) is for FreeCommander to use its own robust and queued filehandling, so that copying large files or multiple files does not imply automatically an extendended coffee break.
I certainly cannot complain about FreeCommander
(....Just found another thread discussing Teracopy etc; it seems like the native file copying is somewhere on the to-do-list) .
Who is online
Users browsing this forum: No registered users and 45 guests