Linked by Thom Holwerda on Mon 11th May 2009 20:43 UTC
Windows SuperFetch is a technology in Windows Vista and onwards that is often misunderstood. I decided to delve into this technology to see what it is all about, and to dispel some of the myths surrounding this feature.
Thread beginning with comment 362962
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by kaiwai
by lemur2 on Tue 12th May 2009 07:15 UTC in reply to "Comment by kaiwai"
lemur2
Member since:
2007-02-17

I've never liked the idea of when an operating system vendor tries to work around inefficiencies in a system by claiming that automation through guessing what the end user requires loading (before they need it) will improve performance overall. I don't like it because it is based on a series of assumptions that fall over in the real world - what happens in the lab doesn't always translate into he real world.


If you crafted it carefully, pre-loading can work. Think of the OS sitting there idle, having loaded the OS, window manager and desktop, with nothing yet to do because the user has yet to press the "start" button. The machine has been keeping track of "libraries accessed, ranked by frequency" and it just knows that in almost every session some libraries, such as perhaps a HTML renderer, vector graphic renderer and a directory lister dlls are almost always used in user sessions but are not loaded yet.

May as well use the time, hey, until the user hits the start button? We are going to get lucky a good percentage of the time and have some stuff pre-loaded that will be needed later, and even if not ... well the system would have been idle otherwise.

As soon as the user hits the start button ... all bets are off ... we will need the system to be responsive.

It could work ... as long as it was carefully crafted.

Reply Parent Score: 3

RE[2]: Comment by kaiwai
by kaiwai on Tue 12th May 2009 08:31 in reply to "RE: Comment by kaiwai"
kaiwai Member since:
2005-07-06

And thus the hate brigade on OSNews.com out at in full force moderating down those whom they don't agree with - and fail to enter into some discourse.

If you crafted it carefully, pre-loading can work. Think of the OS sitting there idle, having loaded the OS, window manager and desktop, with nothing yet to do because the user has yet to press the "start" button. The machine has been keeping track of "libraries accessed, ranked by frequency" and it just knows that in almost every session some libraries, such as perhaps a HTML renderer, vector graphic renderer and a directory lister dlls are almost always used in user sessions but are not loaded yet.

May as well use the time, hey, until the user hits the start button? We are going to get lucky a good percentage of the time and have some stuff pre-loaded that will be needed later, and even if not ... well the system would have been idle otherwise.

As soon as the user hits the start button ... all bets are off ... we will need the system to be responsive.

It could work ... as long as it was carefully crafted.


I don't want my computer constantly 'working' behind the scenes. I want my computer, when it isn't doing something, I want it to go into a deep state so my battery life is maximised to its full potential. I don't want my system bogged down either because the operating system company thinks that they know what I want before I do - don't second guess me because every time you'll fail to do so.

In regards to the larger operating system; I would sooner sacrifice some 'speed' for the sake of more stability, security and reliability. 2 seconds there, 5 seconds there - its nothing in the grand scheme of things. It is nothing in the grand scheme of things when you compare it to the time wasted because of problems that cause down time. What software vendors, be they Microsoft, Apple or what have you, need to look at the 'reducing time lost' holistically rather than simply focusing on 'how fast does it load' and 'how fast does it boot'. They need to focus on the big time wasters rather than a couple of seconds here and there.

Reply Parent Score: 2