Major slowdown while copying large files
Moderators: white, Hacker, petermad, Stefan2
Major slowdown while copying large files
Hi,
maybe you have noticed your system slows down (swaps out almost everything) when you copy large (eg. iso) files to the hdd.
Dear developers, is the O_SEQUENTIAL flag set when you open() the source / destination file?
Best regards
maybe you have noticed your system slows down (swaps out almost everything) when you copy large (eg. iso) files to the hdd.
Dear developers, is the O_SEQUENTIAL flag set when you open() the source / destination file?
Best regards
Re: Major slowdown while copying large files
Even on NT OS's ???lukit wrote:Hi,
maybe you have noticed your system slows down (swaps out almost everything) when you copy large (eg. iso) files to the hdd.
It sure happens on 98se but does it happen also on an xp pro? ... Did you tested on an xp pro?
Re: Major slowdown while copying large files
yep, 2K & XP does it, too.Sam York wrote:Even on NT OS's ???lukit wrote:Hi,
maybe you have noticed your system slows down (swaps out almost everything) when you copy large (eg. iso) files to the hdd.
It sure happens on 98se but does it happen also on an xp pro? ... Did you tested on an xp pro?
Being an user of 98se & xp pro these will not come as a good news
Did you test it? But how about the computer's memory? Those settings will not use a lot of memory resources?aguirRe wrote:Maybe Christian should answer this one but I believe that using the INI file settings CopyHuge*/CopyBlock* will completely circumvent the OS file caching, thus eliminating such behaviour.
- ghisler(Author)
- Site Admin
- Posts: 48088
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
2Sam York
These settings use excactly the memory you specify in the copyblocksize* options. The block is only allocated when needed (during copying).
These settings use excactly the memory you specify in the copyblocksize* options. The block is only allocated when needed (during copying).
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
But wouldn't this be the same thing since the slowdown appears in the moment you copy/move files with the settings mentions not applied?ghisler(Author) wrote:2Sam York
These settings use excactly the memory you specify in the copyblocksize* options. The block is only allocated when needed (during copying).
- ghisler(Author)
- Site Admin
- Posts: 48088
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
I have no idea where the slowdown comes from in your case. I can only guess that the drivers weren't correctly written, so they seem to work OK with Explorer, but if the functions are called in a different order like in TC, the driver fails.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
Re: Major slowdown while copying large files
Unfortunately is not in my case only or on only one OS ...lukit wrote:yep, 2K & XP does it, too.Sam York wrote:Even on NT OS's ???lukit wrote:Hi,
maybe you have noticed your system slows down (swaps out almost everything) when you copy large (eg. iso) files to the hdd.
It sure happens on 98se but does it happen also on an xp pro? ... Did you tested on an xp pro?
Do you set O_SEQUENTIAL bit when you open the source file? It specifies the file access will be mainly sequential.ghisler(Author) wrote:I have no idea where the slowdown comes from in your case. I can only guess that the drivers weren't correctly written, so they seem to work OK with Explorer, but if the functions are called in a different order like in TC, the driver fails.
I wrote a little program: it makes a copy of a file via 50K buffer. If I don't define O_SEQUENTIAL - windows will swap the hell out, will slow down heavily. If I use O_SEQUENTIAL, the copy process and the system will be fine. I gladly give you the source files to see the difference.
- SanskritFritz
- Power Member
- Posts: 3693
- Joined: 2003-07-24, 09:25 UTC
- Location: Budapest, Hungary
Wow, can I please have it? I am very curious about the time differences. My assuption is, that the O_SEQUENTIAL version is slower. But to maintain system response, IMHO is more important than speed when copying in the background.I wrote a little program: it makes a copy of a file via 50K buffer. If I don't define O_SEQUENTIAL - windows will swap the hell out, will slow down heavily. If I use O_SEQUENTIAL, the copy process and the system will be fine. I gladly give you the source files to see the difference.
I switched to Linux, bye and thanks for all the fish!
- ghisler(Author)
- Site Admin
- Posts: 48088
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Yes I do!Do you set O_SEQUENTIAL bit when you open the source file?
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com