I do have temp and incoming on two different file systems.
wxwidget's copyfile implementation (which is used as a generic fallback in this scenario on Linux) is rather dumb, as it uses only a 4 KB buffer ( https://github.com/wxWidgets/wxWidgets/blob/f12b247d26b6a1f2d48e88f2892c51988acbb578/src/common/filefn.cpp#L369 ).
This results in a slow file copy (about 13 MB/s) on my case. Yep, I'm still using NFSv3, but I even used sshfs for long time. A copy with "normal" tools (cp command, midnight commander) archive over 50 MB/s.
Sadly, the 4096 bytes are hard coded in wxWidgets's copyfile, and it is not even configurable it seems...
I do have temp and incoming on two different file systems.
wxwidget's copyfile implementation (which is used as a generic fallback in this scenario on Linux) is rather dumb, as it uses only a 4 KB buffer ( https://github.com/wxWidgets/wxWidgets/blob/f12b247d26b6a1f2d48e88f2892c51988acbb578/src/common/filefn.cpp#L369 ).
This results in a slow file copy (about 13 MB/s) on my case. Yep, I'm still using NFSv3, but I even used sshfs for long time. A copy with "normal" tools (cp command, midnight commander) archive over 50 MB/s.
Sadly, the 4096 bytes are hard coded in wxWidgets's copyfile, and it is not even configurable it seems...