Mick Murphy

Readboost was NOT designed for systems with large amounts of RAM; simple as
that!

"Mike Brannigan" wrote:

>
> "carl feredeck" <carlferedeck@wizzmail.com> wrote in message
> news:46a09119@newsgate.x-privat.org...
> > Experience shows that readyboost does nil for computers with lots of ram.
> > Some people here even reported that it slowed their high end computer
> > down!
> >
>
> Even a PC with a lot of RAM will flush unused entries from cache when an
> application exit. Say for example you were doing some work in a word
> processor package.
> If you subsequently reopen the application and open the document you were
> working on this will be draw from the ReadyBoost cache significantly faster
> then from the hard drive. That is a performance boost even for a system with
> a lot of memory.
> I run systems with 4 and 8GB of RAM and there is still performance to be
> gained by using ReadyBoost.
> On laptop systems I un with 2GB of memory a 2 or 4GB memory stick again
> improves overall performance for day to day use.
>
> > YES readyboost also has a bug noted to be fixed in the SP1... but that
> > will be around the end of the year!
> >
>
> So? There are a number of outstanding bugs in the OS that re being
> addressed with the monthly patches and will also be in SP1. This does not
> mean Ready Boost should not be used.
> (If you mean 939008 then this is not even that big a deal)
>
> > Basically readyboost is a bad idea and a "patch" technology to go around
> > actually writing the vista code better leaner faster and smarter.
> >
>
> Not at all - it is actually an enhancement as hard drive technology and
> performance is being out stripped by solid state "drive" technology :
> ReadyDrive goes on to use the similar technology for Hybrid drives which are
> actually a patch again to slow spinning hard drive technology by
> incorporating flash drive memory into the drive.
>
> > Basic MS logic: Lets bloat vista to smithereens, don't waste time actually
> > thinking, and then lets add a readyboost to make everyone happy.
> >
>
> Again incorrect - this is helping the performance of the system until
> everyone can afford to switch to solid state drives of sufficient capacity
> etc.
>
> > WHAT A DISGRACE! You have been brainwashed and you love it!
> >
>
> No brainwashing here - it is you with your ill informed and ill conceived
> arguments that cannot see the real reasoning behind this technology or where
> it can and should be used.
>
> --
>
> Mike Brannigan
> "carl feredeck" <carlferedeck@wizzmail.com> wrote in message
> news:46a09119@newsgate.x-privat.org...
> > Experience shows that readyboost does nil for computers with lots of ram.
> > Some people here even reported that it slowed their high end computer
> > down!
> >
> > YES readyboost also has a bug noted to be fixed in the SP1... but that
> > will be around the end of the year!
> >
> > Basically readyboost is a bad idea and a "patch" technology to go around
> > actually writing the vista code better leaner faster and smarter.
> >
> > Basic MS logic: Lets bloat vista to smithereens, don't waste time actually
> > thinking, and then lets add a readyboost to make everyone happy.
> >
> > WHAT A DISGRACE! You have been brainwashed and you love it!
> >
> > "Mike Brannigan" <Mike.Brannigan@localhost> wrote in message
> > news:6D4F4E6C-67EB-4586-B6C2-6BCF29A34D0B@microsoft.com...
> >> "Jurij" <jurijvi@hotmail.com> wrote in message
> >> news:E6D45015-A73E-4650-8702-EFA8E97A26BD@microsoft.com...
> >>> Hello all,
> >>>
> >>> I was intrigued by the Readyboost feature, but I presume it's more
> >>> effective on
> >>> "resource limited" systems?
> >>>
> >>> Regards
> >>
> >> No - ReadyBoost helps the performance of all systems as acting as a
> >> faster write through caching area to the hard drive.
> >> So even on systems with plenty of memory where there is any writing to
> >> disk and then potentially reading that data back in (after it may have
> >> been flushed from memory) then the use of the ReadyBoost cache is faster
> >> then the access to disk.
> >>
> >>
> >> --
> >>
> >> Mike Brannigan
> >
> >
>