Leo,
I'm talking 40gb files here... there no chance of caching causing the HUGE discrepancy. It's not hardware, driver or network. Xplorer2 does not have this issue.
I already explained what my tests were, very large files being copied from one folder to another on the same iSCSI drive connection.
Considering that many others seem to be seeing this issue with OPUS I have to assume it's OPUS and certainly not my system. To be frank I'm not interested in messing around with settings (unless you can point ones out that can improve performance 10 fold) to figure this out. It should perform roughly equivalent to Explorer and other file managers (as I mentioned I tested xplorer2 to validate) out of the box imo. That it is consistently slow only in OPUS and not elsewhere pretty much tells me it's not my system.
Don't mean to be argumentative here but I'm a software engineer myself and I understand how software "should" work and if this is a "settings" issue then it should have been identified a long time ago and the information on correcting it should be available. If it was environmental then that also should be well known by now as it appears others have had the same issue (those that have reported back and/or tested.)
As for every program should be the same... that is completely untrue. You are using your own code for the main manager interface and for the copy process (you aren't using the Windows Explorer APIs to copy the files for example) and so it's your copy code that is the problem. I've tested both Xyplorer and Xplorer2 and neither of those products has a problem.
I really want this to be a resolvable problem. I love Directory Opus overall but this is a deal breaker. Any ideas (other than setting the copy buffer size as I've tried 1mb to 9mb and no joy) would be appreciated. If I can't get Explorer copy speeds then Opus won't work for me.
Thanks.