Wrong. Updating the screen is a significant cost when you update continously and determining the filename isn't a trivial operation either (physical filename != displayed filename).. obviously both things aren't much of a problem if you copy one large file, but when it's mostly small files those things do matter.No. The transfer includes all that regardless of whether or not you choose to view it in the display.
Wrong. Updating the screen is a significant cost when you update continously and determining the filename isn't a trivial operation either (physical filename != displayed filename).. obviously both things aren't much of a problem if you copy one large file, but when it's mostly small files those things do matter.
And there I even mentioned "(physical filename != displayed filename)", but alas some people really need everything in exhausting detail: Showing a filename in Windows isn't just a truncate file operation, because you really don't want to show someone with a chinese localisation a file called "notepad.lnk" (or much more fun, the french filename to a german user [yeah that could happen, ultimate versions are great]), because well they're used to seeing the correct name. So we have to check if someone called this nice function here on the specific file and if yes get the localized name.If you somehow manage to have a machine where truncating a string and updating the contents of a text box have an appreciable affect on anything, I doubt you'd run Win7 and if you did you'd already have the most patience of anyone I know.
And there I even mentioned "(physical filename != displayed filename)", but alas some people really need everything in exhausting detail: Showing a filename in Windows isn't just a truncate file operation, because you really don't want to show someone with a chinese localisation a file called "notepad.lnk" (or much more fun, the french filename to a german user [yeah that could happen, ultimate versions are great]), because well they're used to seeing the correct name. So we have to check if someone called this nice function here on the specific file and if yes get the localized name.
And updating a textbox a thousand times per second (we're talking small files here as I already mentioned) doesn't cost any resources? Yep, sure.
We're not talking about from 1minute to an hour changes, but loosing an amount of time larger than a few ms if you copy a large folder with lots of small files? Completely possible.
Iiirc Raymond Chen actually blogged about all this stuff some time ago and also had some code that demonstrated the principle. But I'm sure one of the most experienced people on the MS shell team also just has no idea what he's talking about, right?
Let's see if I can find it.
Edit: Ok, that was way easier than expected. Featured by my almighty googling skills: http://blogs.msdn.com/b/oldnewthing/archive/2010/05/25/10014185.aspx
You're more than welcome to compile the small program there and look at the results yourself - just set the counter a bit higher since we're talking about lots of files here and that example was written 4 years ago..
But your article clearly shows that the small program you would have us compile, is not what is happening when Win7 displays " More information ".......
Edit: Ok, that was way easier than expected. Featured by my almighty googling skills: http://blogs.msdn.com/b/oldnewthing/archive/2010/05/25/10014185.aspx
You're more than welcome to compile the small program there and look at the results yourself - just set the counter a bit higher since we're talking about lots of files here and that example was written 4 years ago..
Wait, where does it show that? The small program shows the effect of redrawing the screen excessively, which is exactly the same for the copy dialog. Not more not less. We ignore the problem of checking/getting localized file names, but that can at best make the program faster not slower.But your article clearly shows that the small program you would have us compile, is not what is happening when Win7 displays " More information "..
If you don't have anything to do but watch the screen while files transfer, what difference does a few seconds matter, much less a few milliseconds ?Wait, where does it show that? The small program shows the effect of redrawing the screen excessively, which is exactly the same for the copy dialog. Not more not less. We ignore the problem of checking/getting localized file names, but that can at best make the program faster not slower.
And the problem with just copying a large amount of small files several times is, that that's extremely hard to bench reliable with all those caches in between.
Does this slow down the transfer?
Not if your Heisenberg Compensators are properly alligned.
I believe they are. However, I am wearing a red shirt. Does that mean anything?