Skip to contentSkip to conversation

Why the DOS has many ntfs read and write driver,but the linux can't for a long time

DISCUSSION Robert Hancock 13 participants 27 messages Jan 9, 2006 – Jan 10, 2006 4 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#4 lore raw
Quoted 1 line · Yaroslav Rastrigin

Well, I could find more or less reasonable explanation of this behaviour - different VM policies of two OSes and strangely strong and persistent belief "Free RAM is a wasted RAM" among kernel devs. Free RAM is not a wasted RAM, its a memory waiting to be used ! Whenever it is needed by apps I'm launching or working with.

There is no different VM policy here, Windows behaves quite similarly. It does not leave memory around unused, it uses it for disk cache.

Signature · 3 lines
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
#5 lore raw

Am Montag, 9. Januar 2006 15:18 schrieb Robert Hancock:

Quoted 7 lines
Quoted 3 lines · Yaroslav Rastrigin

Well, I could find more or less reasonable explanation of this behaviour - different VM policies of two OSes and
strangely strong and persistent belief "Free RAM is a wasted RAM" among kernel devs. Free RAM is not a wasted RAM, its a memory waiting to be used ! Whenever it is needed by apps I'm launching or working with.

There is no different VM policy here, Windows behaves quite similarly. It does not leave memory around unused, it uses it for disk cache.

That doesn't mean that the rate of eviction is the same. Is it possible that read-ahead is not aggressive enough?

Regards
Oliver

#6 lore raw
Quoted 11 lines · Oliver Neukum

Am Montag, 9. Januar 2006 15:18 schrieb Robert Hancock:

Quoted 7 lines
Quoted 3 lines · Yaroslav Rastrigin

Well, I could find more or less reasonable explanation of this behaviour - different VM policies of two OSes and
strangely strong and persistent belief "Free RAM is a wasted RAM" among kernel devs. Free RAM is not a wasted RAM, its a memory waiting to be used ! Whenever it is needed by apps I'm launching or working with.

There is no different VM policy here, Windows behaves quite similarly. It does not leave memory around unused, it uses it for disk cache.

That doesn't mean that the rate of eviction is the same. Is it possible that read-ahead is not aggressive enough?

Enough for what? What is the exact problem you are trying to solve?

Lee

#7 lore raw

Am Montag, 9. Januar 2006 16:15 schrieb Lee Revell:

Quoted 7 lines · Oliver Neukum
Quoted 6 lines

Am Montag, 9. Januar 2006 15:18 schrieb Robert Hancock:

Quoted 5 lines
Quoted 3 lines · Yaroslav Rastrigin

Well, I could find more or less reasonable explanation of this behaviour - different VM policies of two OSes and
strangely strong and persistent belief "Free RAM is a wasted RAM" among kernel devs. Free RAM is not a wasted RAM, its a memory waiting to be used ! Whenever it is needed by apps I'm launching or working with.

Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

There is no different VM policy here, Windows behaves quite similarly. It does not leave memory around unused, it uses it for disk cache.

That doesn't mean that the rate of eviction is the same. Is it possible that read-ahead is not aggressive enough?

Enough for what? What is the exact problem you are trying to solve?

Quicker application startup.

Regards
Oliver

#8 lore raw
Quoted 11 lines · Oliver Neukum

Am Montag, 9. Januar 2006 16:15 schrieb Lee Revell:

Quoted 10 lines · Oliver Neukum
Quoted 9 lines

Am Montag, 9. Januar 2006 15:18 schrieb Robert Hancock:

Quoted 7 lines
Quoted 3 lines · Yaroslav Rastrigin

Well, I could find more or less reasonable explanation of this behaviour - different VM policies of two OSes and
strangely strong and persistent belief "Free RAM is a wasted RAM" among kernel devs. Free RAM is not a wasted RAM, its a memory waiting to be used ! Whenever it is needed by apps I'm launching or working with.

There is no different VM policy here, Windows behaves quite similarly. It does not leave memory around unused, it uses it for disk cache.

Quoted 6 lines
Quoted 4 lines
Quoted 2 lines

That doesn't mean that the rate of eviction is the same. Is it possible that read-ahead is not aggressive enough?

Enough for what? What is the exact problem you are trying to solve?

Quicker application startup.

Why do you look to the kernel first? The obvious explanation is that Linux desktop apps are more bloated than their Windows counterparts.

Lee

#9 lore raw

Am Montag, 9. Januar 2006 17:04 schrieb Lee Revell:

Quoted 15 lines · Oliver Neukum
Quoted 14 lines

Am Montag, 9. Januar 2006 16:15 schrieb Lee Revell:

Quoted 13 lines · Oliver Neukum
Quoted 11 lines

Am Montag, 9. Januar 2006 15:18 schrieb Robert Hancock:

Quoted 7 lines
Quoted 3 lines · Yaroslav Rastrigin

Well, I could find more or less reasonable explanation of this behaviour - different VM policies of two OSes and
strangely strong and persistent belief "Free RAM is a wasted RAM" among kernel devs. Free RAM is not a wasted RAM, its a memory waiting to be used ! Whenever it is needed by apps I'm launching or working with.

There is no different VM policy here, Windows behaves quite similarly. It does not leave memory around unused, it uses it for disk cache.

That doesn't mean that the rate of eviction is the same. Is it possible that read-ahead is not aggressive enough?

Quoted 6 lines
Quoted 3 lines
Quoted 1 line

Enough for what? What is the exact problem you are trying to solve?

Quicker application startup.

Why do you look to the kernel first? The obvious explanation is that Linux desktop apps are more bloated than their Windows counterparts.

It is the most efficient place. An improvement to the kernel will improve all starting times.

Regards
Oliver

#10 lore raw
Quoted 18 lines · Oliver Neukum

Am Montag, 9. Januar 2006 17:04 schrieb Lee Revell:

Quoted 17 lines · Oliver Neukum
Quoted 16 lines

Am Montag, 9. Januar 2006 16:15 schrieb Lee Revell:

Quoted 14 lines · Oliver Neukum
Quoted 11 lines

Am Montag, 9. Januar 2006 15:18 schrieb Robert Hancock:

Quoted 7 lines
Quoted 3 lines · Yaroslav Rastrigin

Well, I could find more or less reasonable explanation of this behaviour - different VM policies of two OSes and
strangely strong and persistent belief "Free RAM is a wasted RAM" among kernel devs. Free RAM is not a wasted RAM, its a memory waiting to be used ! Whenever it is needed by apps I'm launching or working with.

There is no different VM policy here, Windows behaves quite similarly. It does not leave memory around unused, it uses it for disk cache.

That doesn't mean that the rate of eviction is the same. Is it possible that read-ahead is not aggressive enough?

Enough for what? What is the exact problem you are trying to solve?

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

Quicker application startup.

Why do you look to the kernel first? The obvious explanation is that Linux desktop apps are more bloated than their Windows counterparts.

It is the most efficient place. An improvement to the kernel will improve all starting times.

I think you'll get at most a 10% or 20% speedup by improving the kernel, while some of these apps (think Nautilus vs Windows Explorer) will need to be 1000% faster to seem reasonable to a Windows user.

Lee

Lee

#11 lore raw
Quoted 24 lines · Lee Revell
Quoted 23 lines · Oliver Neukum

Am Montag, 9. Januar 2006 17:04 schrieb Lee Revell:

Quoted 21 lines · Oliver Neukum
Quoted 11 lines

Am Montag, 9. Januar 2006 16:15 schrieb Lee Revell:

Quoted 10 lines · Oliver Neukum
Quoted 9 lines

Am Montag, 9. Januar 2006 15:18 schrieb Robert Hancock:

Quoted 7 lines
Quoted 3 lines · Yaroslav Rastrigin

Well, I could find more or less reasonable explanation of this behaviour - different VM policies of two OSes and
strangely strong and persistent belief "Free RAM is a wasted RAM" among kernel devs. Free RAM is not a wasted RAM, its a memory waiting to be used ! Whenever it is needed by apps I'm launching or working with.

There is no different VM policy here, Windows behaves quite similarly. It does not leave memory around unused, it uses it for disk cache.

Quoted 6 lines
Quoted 4 lines
Quoted 2 lines

That doesn't mean that the rate of eviction is the same. Is it possible that read-ahead is not aggressive enough?

Enough for what? What is the exact problem you are trying to solve?

Quicker application startup.

Why do you look to the kernel first? The obvious explanation is that Linux desktop apps are more bloated than their Windows counterparts.

Quoted 6 lines
Quoted 2 lines

It is the most efficient place. An improvement to the kernel will improve all starting times.

I think you'll get at most a 10% or 20% speedup by improving the kernel, while some of these apps (think Nautilus vs Windows Explorer) will need to be 1000% faster to seem reasonable to a Windows user.

That's easy: Just start nautilus, OOorg, Firefox, a java-vm and GNOME/KDE infrastructure at login time in the background (*eg* and mlockall() the more important ones so that the are surely in RAM) and "starting the app" is only a small program connecting to the respective process to get a fork() there (e.g. like the "-remote" parameter in the Mozilla family).

Bernd

Signature · 3 lines
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services
#12 lore raw
Quoted 32 lines · Bernd Petrovitsch
Quoted 24 lines · Lee Revell
Quoted 23 lines · Oliver Neukum

Am Montag, 9. Januar 2006 17:04 schrieb Lee Revell:

Quoted 21 lines · Oliver Neukum
Quoted 11 lines

Am Montag, 9. Januar 2006 16:15 schrieb Lee Revell:

Quoted 10 lines · Oliver Neukum
Quoted 9 lines

Am Montag, 9. Januar 2006 15:18 schrieb Robert Hancock:

Quoted 7 lines
Quoted 3 lines · Yaroslav Rastrigin

Well, I could find more or less reasonable explanation of this behaviour - different VM policies of two OSes and
strangely strong and persistent belief "Free RAM is a wasted RAM" among kernel devs. Free RAM is not a wasted RAM, its a memory waiting to be used ! Whenever it is needed by apps I'm launching or working with.

There is no different VM policy here, Windows behaves quite similarly. It does not leave memory around unused, it uses it for disk cache.

Quoted 6 lines
Quoted 4 lines
Quoted 2 lines

That doesn't mean that the rate of eviction is the same. Is it possible that read-ahead is not aggressive enough?

Enough for what? What is the exact problem you are trying to solve?

Quicker application startup.

Why do you look to the kernel first? The obvious explanation is that Linux desktop apps are more bloated than their Windows counterparts.

Quoted 6 lines
Quoted 2 lines

It is the most efficient place. An improvement to the kernel will improve all starting times.

I think you'll get at most a 10% or 20% speedup by improving the kernel, while some of these apps (think Nautilus vs Windows Explorer) will need to be 1000% faster to seem reasonable to a Windows user.

Quoted 6 lines

That's easy: Just start nautilus, OOorg, Firefox, a java-vm and GNOME/KDE infrastructure at login time in the background (*eg* and mlockall() the more important ones so that the are surely in RAM) and "starting the app" is only a small program connecting to the respective process to get a fork() there (e.g. like the "-remote" parameter in the Mozilla family).

Have you tried this? I suspect it still takes at least twice as long as on windows.

For example on my system there was already a "nautilus" process but "Places -> Home Folder" still took ~2 seconds to display anything, and ~8 seconds to completely render the window and icons. On Windows this takes much less than a second.

Lee

#13 lore raw

Am Montag, 9. Januar 2006 17:41 schrieb Lee Revell:

Quoted 40 lines · Bernd Petrovitsch
Quoted 32 lines · Lee Revell
Quoted 24 lines · Oliver Neukum
Quoted 23 lines

Am Montag, 9. Januar 2006 17:04 schrieb Lee Revell:

Quoted 21 lines · Oliver Neukum
Quoted 11 lines

Am Montag, 9. Januar 2006 16:15 schrieb Lee Revell:

Quoted 10 lines · Oliver Neukum
Quoted 9 lines

Am Montag, 9. Januar 2006 15:18 schrieb Robert Hancock:

Quoted 7 lines
Quoted 3 lines · Yaroslav Rastrigin

Well, I could find more or less reasonable explanation of this behaviour - different VM policies of two OSes and
strangely strong and persistent belief "Free RAM is a wasted RAM" among kernel devs. Free RAM is not a wasted RAM, its a memory waiting to be used ! Whenever it is needed by apps I'm launching or working with.

There is no different VM policy here, Windows behaves quite similarly. It does not leave memory around unused, it uses it for disk cache.

Quoted 6 lines
Quoted 4 lines
Quoted 2 lines

That doesn't mean that the rate of eviction is the same. Is it possible that read-ahead is not aggressive enough?

Enough for what? What is the exact problem you are trying to solve?

Quicker application startup.

Why do you look to the kernel first? The obvious explanation is that Linux desktop apps are more bloated than their Windows counterparts.

Quoted 6 lines
Quoted 2 lines

It is the most efficient place. An improvement to the kernel will improve all starting times.

I think you'll get at most a 10% or 20% speedup by improving the kernel, while some of these apps (think Nautilus vs Windows Explorer) will need to be 1000% faster to seem reasonable to a Windows user.

Quoted 6 lines

That's easy: Just start nautilus, OOorg, Firefox, a java-vm and GNOME/KDE infrastructure at login time in the background (*eg* and mlockall() the more important ones so that the are surely in RAM) and "starting the app" is only a small program connecting to the respective process to get a fork() there (e.g. like the "-remote" parameter in the Mozilla family).

Quoted 7 lines

Have you tried this? I suspect it still takes at least twice as long as on windows.

For example on my system there was already a "nautilus" process but "Places -> Home Folder" still took ~2 seconds to display anything, and ~8 seconds to completely render the window and icons. On Windows this takes much less than a second.

Does the Windows Explorer draw icons based only on name and metadata?

Regards
Oliver

#14 lore raw
Quoted 44 lines · Oliver Neukum

Am Montag, 9. Januar 2006 17:41 schrieb Lee Revell:

Quoted 43 lines · Bernd Petrovitsch
Quoted 32 lines · Lee Revell
Quoted 24 lines · Oliver Neukum
Quoted 23 lines

Am Montag, 9. Januar 2006 17:04 schrieb Lee Revell:

Quoted 21 lines · Oliver Neukum
Quoted 11 lines

Am Montag, 9. Januar 2006 16:15 schrieb Lee Revell:

Quoted 10 lines · Oliver Neukum
Quoted 9 lines

Am Montag, 9. Januar 2006 15:18 schrieb Robert Hancock:

Quoted 7 lines
Quoted 3 lines · Yaroslav Rastrigin

Well, I could find more or less reasonable explanation of this behaviour - different VM policies of two OSes and
strangely strong and persistent belief "Free RAM is a wasted RAM" among kernel devs. Free RAM is not a wasted RAM, its a memory waiting to be used ! Whenever it is needed by apps I'm launching or working with.

There is no different VM policy here, Windows behaves quite similarly. It does not leave memory around unused, it uses it for disk cache.

Quoted 6 lines
Quoted 4 lines
Quoted 2 lines

That doesn't mean that the rate of eviction is the same. Is it possible that read-ahead is not aggressive enough?

Enough for what? What is the exact problem you are trying to solve?

Quicker application startup.

Why do you look to the kernel first? The obvious explanation is that Linux desktop apps are more bloated than their Windows counterparts.

Quoted 6 lines
Quoted 2 lines

It is the most efficient place. An improvement to the kernel will improve all starting times.

I think you'll get at most a 10% or 20% speedup by improving the kernel, while some of these apps (think Nautilus vs Windows Explorer) will need to be 1000% faster to seem reasonable to a Windows user.

Quoted 6 lines

That's easy: Just start nautilus, OOorg, Firefox, a java-vm and GNOME/KDE infrastructure at login time in the background (*eg* and mlockall() the more important ones so that the are surely in RAM) and "starting the app" is only a small program connecting to the respective process to get a fork() there (e.g. like the "-remote" parameter in the Mozilla family).

Have you tried this? I suspect it still takes at least twice as long as on windows.

Quoted 6 lines
Quoted 4 lines

For example on my system there was already a "nautilus" process but "Places -> Home Folder" still took ~2 seconds to display anything, and ~8 seconds to completely render the window and icons. On Windows this takes much less than a second.

Does the Windows Explorer draw icons based only on name and metadata?

No idea. All i know is it's fast enough to be usable and Nautilus isn't.

Lee

#15 lore raw
In reply to Oliver Neukum
Quoted 3 lines · Oliver Neukum

Does the Windows Explorer draw icons based only on name and metadata?

From what I can see it does icons on non-executable entirely based on

the extension and nothing else on the first pass. Executables are looked inside for an icon (and there seems to be cache effects at times, especially visible on the desktop). Then for images a second pass generates icons depending on the contents (with, once again, a cache hidden somewhere).

Not a bad strategy, too. Doing a file(1) on everything can only be slow given the random disk accesses it generates. Maybe a file(1) as a _second_ pass would work.

OG.

#16 lore raw
Quoted 10 lines · Olivier Galibert
Quoted 3 lines · Oliver Neukum

Does the Windows Explorer draw icons based only on name and metadata?

From what I can see it does icons on non-executable entirely based on

the extension and nothing else on the first pass. Executables are looked inside for an icon (and there seems to be cache effects at times, especially visible on the desktop). Then for images a second pass generates icons depending on the contents (with, once again, a cache hidden somewhere).

Quoted 3 lines

Not a bad strategy, too. Doing a file(1) on everything can only be slow given the random disk accesses it generates. Maybe a file(1) as a _second_ pass would work.

Gack, does Nautilus really do file(1) on everything? That's unspeakably awful.

Lee

#17 lore raw
Quoted 11 lines · Lee Revell
Quoted 10 lines · Olivier Galibert
Quoted 3 lines · Oliver Neukum

Does the Windows Explorer draw icons based only on name and metadata?

From what I can see it does icons on non-executable entirely based on

the extension and nothing else on the first pass. Executables are looked inside for an icon (and there seems to be cache effects at times, especially visible on the desktop). Then for images a second pass generates icons depending on the contents (with, once again, a cache hidden somewhere).

Quoted 6 lines
Quoted 3 lines

Not a bad strategy, too. Doing a file(1) on everything can only be slow given the random disk accesses it generates. Maybe a file(1) as a _second_ pass would work.

Gack, does Nautilus really do file(1) on everything? That's unspeakably awful.

I believe it does a lot worse things. It actually reads a picture file for example, then resizes the picture down to an icon sized one and then displays the icon, then on to the next file and for text files it displays the beginning of the text file in the icon, etc... Totally unnecessary and brings total slowdown. But of course as with Windows Explorer this is configurable and you can just use list view without icons...

Best regards,

Anton

Signature · 4 lines
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
#18 lore raw

File type by extension is evil (was Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time)

In reply to Olivier Galibert
Quoted 6 lines · Olivier Galibert
Quoted 1 line

From what I can see it does icons on non-executable entirely based on

the extension and nothing else on the first pass.

Not a bad strategy, too. Doing a file(1) on everything can only be slow given the random disk accesses it generates. Maybe a file(1) as a _second_ pass would work.

That may be a good strategy if you have user conditioned to all the effects you get by this (i.e. if you only focus on Windows users and want them provide with a system as broken as they know it) and programs adopted to cope with the most ill effects (ever asked why some browsers always foozle the name of downloaded files with some .html or the like?)

For everyone else looking at the file is the only sane way to know the type of file.

Bernhard R. Link

#19 lore raw

Re: File type by extension is evil (was Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time)

Quoted 8 lines · Bernhard R. Link
Quoted 6 lines · Olivier Galibert
Quoted 1 line

From what I can see it does icons on non-executable entirely based on

the extension and nothing else on the first pass.

Not a bad strategy, too. Doing a file(1) on everything can only be slow given the random disk accesses it generates. Maybe a file(1) as a _second_ pass would work.

Quoted 8 lines

That may be a good strategy if you have user conditioned to all the effects you get by this (i.e. if you only focus on Windows users and want them provide with a system as broken as they know it) and programs adopted to cope with the most ill effects (ever asked why some browsers always foozle the name of downloaded files with some .html or the like?)

For everyone else looking at the file is the only sane way to know the type of file.

OK so it's prohibitively expensive to get the file type so this is not something Nautilus should be doing to every file before even starting to display the icons.

Lee

#20 lore raw
In reply to Oliver Neukum
Quoted 44 lines · Oliver Neukum

Am Montag, 9. Januar 2006 17:41 schrieb Lee Revell:

Quoted 43 lines · Bernd Petrovitsch
Quoted 32 lines · Lee Revell
Quoted 24 lines · Oliver Neukum
Quoted 23 lines

Am Montag, 9. Januar 2006 17:04 schrieb Lee Revell:

Quoted 21 lines · Oliver Neukum
Quoted 11 lines

Am Montag, 9. Januar 2006 16:15 schrieb Lee Revell:

Quoted 10 lines · Oliver Neukum
Quoted 9 lines

Am Montag, 9. Januar 2006 15:18 schrieb Robert Hancock:

Quoted 7 lines
Quoted 3 lines · Yaroslav Rastrigin

Well, I could find more or less reasonable explanation of this behaviour - different VM policies of two OSes and
strangely strong and persistent belief "Free RAM is a wasted RAM" among kernel devs. Free RAM is not a wasted RAM, its a memory waiting to be used ! Whenever it is needed by apps I'm launching or working with.

There is no different VM policy here, Windows behaves quite similarly. It does not leave memory around unused, it uses it for disk cache.

Quoted 6 lines
Quoted 4 lines
Quoted 2 lines

That doesn't mean that the rate of eviction is the same. Is it possible that read-ahead is not aggressive enough?

Enough for what? What is the exact problem you are trying to solve?

Quicker application startup.

Why do you look to the kernel first? The obvious explanation is that Linux desktop apps are more bloated than their Windows counterparts.

Quoted 6 lines
Quoted 2 lines

It is the most efficient place. An improvement to the kernel will improve all starting times.

I think you'll get at most a 10% or 20% speedup by improving the kernel, while some of these apps (think Nautilus vs Windows Explorer) will need to be 1000% faster to seem reasonable to a Windows user.

Quoted 6 lines

That's easy: Just start nautilus, OOorg, Firefox, a java-vm and GNOME/KDE infrastructure at login time in the background (*eg* and mlockall() the more important ones so that the are surely in RAM) and "starting the app" is only a small program connecting to the respective process to get a fork() there (e.g. like the "-remote" parameter in the Mozilla family).

Have you tried this? I suspect it still takes at least twice as long as on windows.

Quoted 6 lines
Quoted 4 lines

For example on my system there was already a "nautilus" process but "Places -> Home Folder" still took ~2 seconds to display anything, and ~8 seconds to completely render the window and icons. On Windows this takes much less than a second.

Does the Windows Explorer draw icons based only on name and metadata?

Depends on the "View" of that directory and what you mean with "metadata":
- There are view types that display such mini-icons and/or file details and/or contents for images.
- "Metadata" in the Windows-hell means "extension" which you get cheap with the filename anyways. There is no thing like "file" or a similar attempt to guess the type of contents automagically just for doing graphiocal "ls".

Bernd

Signature · 3 lines
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services
#21 lore raw
In reply to Oliver Neukum
Quoted 1 line · Oliver Neukum

Does the Windows Explorer draw icons based only on name and metadata?

Sort of. It also plays tricks on the human by working out what icons are visible and loading those first then filling in while the user thinks it is ready

#22 lore raw
Quoted 7 lines · Alan Cox
Quoted 1 line · Oliver Neukum

Does the Windows Explorer draw icons based only on name and metadata?

Sort of. It also plays tricks on the human by working out what icons are visible and loading those first then filling in while the user thinks it is ready

See, I don't think that's a trick, isn't it just a form of demand paging? It seems silly to make the user wait to see the visible icons until it's done rendering the hidden stuff. Otherwise navigating the file system speeds up and slows down based on how many files are in each directory, even if the number of visible icons remains constant.

Do most Linux GUI apps really render everything without regard to what's obscured and what's visible?

Lee

#23 lore raw
Quoted 3 lines

Do most Linux GUI apps really render everything without regard to what's obscured and what's visible?

Yes. Naive usage of backing store is right now pretty much the norm. However the problem isn't the fact that the rendering occurs. The problem is that it occurs synchronously and that composition is serializing with event handling.

#24 lore raw
In reply to Alan Cox

Am Montag, 9. Januar 2006 18:31 schrieb Alan Cox:

Quoted 6 lines · Oliver Neukum
Quoted 1 line

Does the Windows Explorer draw icons based only on name and metadata?

Sort of. It also plays tricks on the human by working out what icons are visible and loading those first then filling in while the user thinks it is ready

That's lazy evaluation. Actually quite clever.

Regards
Oliver

#25 lore raw
In reply to Alan Cox
Quoted 13 lines · Alan Cox
Quoted 3 lines · Oliver Neukum

Does the Windows Explorer draw icons based only on name and metadata?

Sort of. It also plays tricks on the human by working out what icons are visible and loading those first then filling in while the user thinks it is ready

And the mouse driver is biased to always get access to CPU cycles so the cursor will always be visible and working even when the system is totally locked up. NTFS performance is also totally abysimal when volumes reach 2TB sizes due to fragmentation of the NTFS archtiecture. A problem not shared with EXT3 FS's.

J

Quoted 8 lines

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#26 lore raw
In reply to Lee Revell
Quoted 2 lines · Lee Revell
Quoted 1 line · Bernd Petrovitsch

On Mon, 2006-01-09 at 11:19 -0500, Lee Revell wrote:

[....]

Quoted 11 lines
Quoted 10 lines
Quoted 3 lines

I think you'll get at most a 10% or 20% speedup by improving the kernel, while some of these apps (think Nautilus vs Windows Explorer) will need to be 1000% faster to seem reasonable to a Windows user.

That's easy: Just start nautilus, OOorg, Firefox, a java-vm and GNOME/KDE infrastructure at login time in the background (*eg* and mlockall() the more important ones so that the are surely in RAM) and "starting the app" is only a small program connecting to the respective process to get a fork() there (e.g. like the "-remote" parameter in the Mozilla family).

Quoted 2 lines

Have you tried this? I suspect it still takes at least twice as long as on windows.

No, I don't run all on them at once (only xemacs, firefox and the above forgotten evolution on XFCE) and if, the hosts I'm usually working on have probably not enough RAM for mlockall(MCL_CURRRENT).
And AFAIK there are no small starter programs and features - only for Mozilla and cousins.

Quoted 4 lines

For example on my system there was already a "nautilus" process but "Places -> Home Folder" still took ~2 seconds to display anything, and ~8 seconds to completely render the window and icons. On Windows this takes much less than a second.

Hmm, what happens on the click:
- The click is transported via X, TCP/IP to the application.
- The app decides what to do and generates anew window and content.
- If swapped out, swap it in.
- Load the home directory and what else is needed for displaying it (Icons, etc.) from the disk.
- Load these images into the X server.

Id a completely new progrma is started, you must load it from disk, wait for the shared linker, let it initialize everything and *then* it is actually usable (and I hate that default OO.org feature that it puts the window in foreground after startup at least three times until the document is loaded).

If you have a memory hog like firefox with a large page loaded then lots of RAM are occupied anyways and no one except firefox can do anything about it (without swapping out and this is also slow). And I have just to switch tabs to hear my disk working.

Ths point is: You have to analyze *where* the apps spend that much time (independent of being idle wehile waiting for disk I/O or busy moving MB of graphic data around). It doesn't make that much sense to improve the (e.g.) 2% in the kernel by 50% since that would bring next to nothing.

Bernd

Signature · 3 lines
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services
#27 lore raw
In reply to Lee Revell
Quoted 46 lines · Lee Revell
Quoted 38 lines · Bernd Petrovitsch
Quoted 30 lines · Lee Revell
Quoted 29 lines · Oliver Neukum

Am Montag, 9. Januar 2006 17:04 schrieb Lee Revell:

Quoted 27 lines · Oliver Neukum
Quoted 15 lines

Am Montag, 9. Januar 2006 16:15 schrieb Lee Revell:

Quoted 14 lines · Oliver Neukum
Quoted 13 lines

Am Montag, 9. Januar 2006 15:18 schrieb Robert Hancock:

Quoted 11 lines
Quoted 6 lines · Yaroslav Rastrigin

Well, I could find more or less reasonable explanation of this behaviour - different VM policies of two OSes and strangely strong and persistent belief "Free RAM is a wasted RAM" among kernel devs. Free RAM is not a wasted RAM, its a memory waiting to be used ! Whenever it is needed by apps I'm launching or working with.

There is no different VM policy here, Windows behaves quite similarly. It does not leave memory around unused, it uses it for disk cache.

Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

That doesn't mean that the rate of eviction is the same. Is it possible that read-ahead is not aggressive enough?

Enough for what? What is the exact problem you are trying to solve?

Quicker application startup.

Why do you look to the kernel first? The obvious explanation is that Linux desktop apps are more bloated than their Windows counterparts.

Quoted 6 lines
Quoted 2 lines

It is the most efficient place. An improvement to the kernel will improve all starting times.

I think you'll get at most a 10% or 20% speedup by improving the kernel, while some of these apps (think Nautilus vs Windows Explorer) will need to be 1000% faster to seem reasonable to a Windows user.

Quoted 6 lines

That's easy: Just start nautilus, OOorg, Firefox, a java-vm and GNOME/KDE infrastructure at login time in the background (*eg* and mlockall() the more important ones so that the are surely in RAM) and "starting the app" is only a small program connecting to the respective process to get a fork() there (e.g. like the "-remote" parameter in the Mozilla family).

Quoted 7 lines

Have you tried this? I suspect it still takes at least twice as long as on windows.

For example on my system there was already a "nautilus" process but "Places -> Home Folder" still took ~2 seconds to display anything, and ~8 seconds to completely render the window and icons. On Windows this takes much less than a second.

Sounds like a broken configuration to me. Of course the usual array of hardware specs, configuration, filesystem, free RAM, etc. all play into this, but no KDE application, including the originally cited Kate, takes longer than 1s to start on this machine (1.6GHz P-M, 2MB L2, 400MHz FSB, 1GB PC2700).

Hell kfm is probably a hell of a lot more bloated than Nautilus and it's pretty fast to start first time (1-2s), and cached it's pretty much instantaneous (I'd say less than 400ms). Fast enough, no?

Sounds like the kernel is plenty fast.

Signature · 6 lines
Cheers,
Alistair.

'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
#28 lore raw
Quoted 10 lines · Alistair John Strachan

Sounds like a broken configuration to me. Of course the usual array of hardware specs, configuration, filesystem, free RAM, etc. all play into this, but no KDE application, including the originally cited Kate, takes longer than 1s to start on this machine (1.6GHz P-M, 2MB L2, 400MHz FSB, 1GB PC2700).

Hell kfm is probably a hell of a lot more bloated than Nautilus and it's pretty fast to start first time (1-2s), and cached it's pretty much instantaneous (I'd say less than 400ms). Fast enough, no?

I don't think it's a broken configuration, just a slow machine (600MHz VIA C3). Windows XP screams compared to Linux on this thing.

Lee

#29 lore raw

...

Quoted 8 lines
Quoted 4 lines

Hell kfm is probably a hell of a lot more bloated than Nautilus and it's pretty fast to start first time (1-2s), and cached it's pretty much instantaneous (I'd say less than 400ms). Fast enough, no?

I don't think it's a broken configuration, just a slow machine (600MHz VIA C3). Windows XP screams compared to Linux on this thing.

Guys... Apples and oranges and stuff.

My mother is running KDE on Linux now because (among other things) windows explorer was unbearably slow for displaying folders with image thumbnails (very large images and lots of them).

Changing from an older 433MHz Celeron with too little memory to a 2.6 GHz P4 with a gig of memory was not enough. We tried quite a few things, but I ended up giving KDE on Linux (Debian, not that it matters) a try.

I don't know Nautilus and I don't care - but I can say that there are definitely situations in which KDE on Linux seriously and thoroughly kicks MS butt both when it comes to simple usability and availability of "good" software, and not least when it comes to the part of usability we call "performance". Getting the job done in time - and if something takes a while to process, being able to do it in the background and letting the user use the computer meanwhile.

This is not a kernel thing. There is proper desktop software out there - go use it already :)

My 0.02 Euro, for what it's worth,

Signature · 1 line
 / jakob
#30 lore raw
Quoted 28 lines · Jakob Oestergaard

...

Quoted 8 lines
Quoted 4 lines

Hell kfm is probably a hell of a lot more bloated than Nautilus and it's pretty fast to start first time (1-2s), and cached it's pretty much instantaneous (I'd say less than 400ms). Fast enough, no?

I don't think it's a broken configuration, just a slow machine (600MHz VIA C3). Windows XP screams compared to Linux on this thing.

Guys... Apples and oranges and stuff.

My mother is running KDE on Linux now because (among other things) windows explorer was unbearably slow for displaying folders with image thumbnails (very large images and lots of them).

Changing from an older 433MHz Celeron with too little memory to a 2.6 GHz P4 with a gig of memory was not enough. We tried quite a few things, but I ended up giving KDE on Linux (Debian, not that it matters) a try.

I don't know Nautilus and I don't care - but I can say that there are definitely situations in which KDE on Linux seriously and thoroughly kicks MS butt both when it comes to simple usability and availability of "good" software, and not least when it comes to the part of usability we call "performance". Getting the job done in time - and if something takes a while to process, being able to do it in the background and letting the user use the computer meanwhile.

Quoted 5 lines

This is not a kernel thing. There is proper desktop software out there - go use it already :)

My 0.02 Euro, for what it's worth,

I have been using an 800MHz VIA C3 based box (256MB RAM) at work a while back, running Slackware Linux 10.2 with XFCE as the desktop and it's very usable - quite snappy infact. Even KDE runs resonably well on that box once you turn off some of the eyecandy. I have no idea how the box would run Win XP, but it's certainly quite fine as a Linux workstation IMHO.

--
Jesper Juhl <[email protected]>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html