Ready Boost...how do I shut it off.

[Guest]

I have a sandisk Cruzer Micro USB drive and mistakenly allowed Windows to
allocate all of the drive for Ready Boost. I would like to either turn Ready
Boost off or find out how to reconfigure it to use less of the drive.

 

[Richard Urban]

Right click on the drive and go to properties. You will see a tab for
ReadyBoost.

--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

 

[Justin]

I have a sandisk Cruzer Micro USB drive and mistakenly allowed Windows to
allocate all of the drive for Ready Boost. I would like to either turn
Ready
Boost off or find out how to reconfigure it to use less of the drive.

Just FYI..... No one's mentioned it "yet" however I've seen people suggest
to just turn off the ReadyBoost service, system wide, if it's not needed.
This is actually not recommend as the ReadyBoost service does more then just
run ReadyBoost:

http://www.microsoft.com/technet/technetmag/issues/2007/03/VistaKernel/

 

[Tiberius]

So these are the things you read each night before you do your vistaboy
prayer?

that article should be studied on how to make a pile of crap look good, by
using tech jargon...

Perhaps with vista 64 bit and greater than 4 gb of ram, it will show some
improvement compared to xp with the same bits and ram... unfortunately I
don't
have a 64 bit with 8 gb ram to test it on to be sure...

but for the 32 bit vista is sluggish as a prehistoric gigantic snail that
has been fossilized compared to XP.

 

[BigK]

but for the 32 bit vista is sluggish as a prehistoric gigantic snail that
has been fossilized compared to XP.

Depends on your system. I have a Dell 9300 laptop with a 1.7 ghz Pentium M
and 2 GB of ram with a 5400 speed HD and it is at least as fast as XP and
for some things it is faster and others a little slower.

 

[AJR]

To "turn off" ReadyBoost, which is utilized (it's a cache) whether or not
you have an external device, you must turn of Page filing - not a good idea.

 

[Richard Urban]

WHAT?

--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

 

[DanS]

Just FYI..... No one's mentioned it "yet" however I've seen people
suggest to just turn off the ReadyBoost service, system wide, if it's
not needed. This is actually not recommend as the ReadyBoost service
does more then just run ReadyBoost:

http://www.microsoft.com/technet/technetmag/issues/2007/03/VistaKernel/

Since I have a very low reading comprehension level, I failed to see in
that article where it gave any mention of any side effects of turning off
ReadyBoost that affect anything else other than ReadyBoost.

Can you show me where it says that ?

 

[Justin]

Since I have a very low reading comprehension level, I failed to see in
that article where it gave any mention of any side effects of turning off
ReadyBoost that affect anything else other than ReadyBoost.

Can you show me where it says that ?

While I didn't mention anything about "side effects", here you go:

Windows Vista uses the same boot-time prefetching as Windows XP did if the
system has less than 512MB of memory, but if the system has 700MB or more of
RAM, it uses an in-RAM cache to optimize the boot process. The size of the
cache depends on the total RAM available, but is large enough to create a
reasonable cache and yet allow the system the memory it needs to boot
smoothly.

After every boot, the ReadyBoost service (the same service that implements
the ReadyBoost feature just described) uses idle CPU time to calculate a
boot-time caching plan for the next boot. It analyzes file trace information
from the five previous boots and identifies which files were accessed and
where they are located on disk. It stores the processed traces in
%SystemRoot%\Prefetch\Readyboot as .fx files and saves the caching plan
under HKLM\System\CurrentControlSet\Services\Ecache\Parameters in REG_BINARY
values named for internal disk volumes they refer to.

The cache is implemented by the same device driver that implements
ReadyBoost caching (Ecache.sys), but the cache's population is guided by the
ReadyBoost service as the system boots. While the boot cache is compressed
like the ReadyBoost cache, another difference between ReadyBoost and
ReadyBoot cache management is that while in ReadyBoot mode, other than the
ReadyBoost service's updates, the cache doesn't change to reflect data
that's read or written during the boot. The ReadyBoost service deletes the
cache 90 seconds after the start of the boot, or if other memory demands
warrant it, and records the cache's statistics in
HKLM\System\CurrentControlSet\Services\Ecache\Parameters\ReadyBootStats, as
shown in Figure 2. Microsoft performance tests show that ReadyBoot provides
performance improvements of about 20 percent over the legacy Windows XP
prefetcher.


More specifically:
"After every boot, the ReadyBoost service (the same service that implements
the ReadyBoost feature just described) uses idle CPU time to calculate a
boot-time caching plan for the next boot."

Thus, as I mentioned, "ReadyBoost service does more then just run
ReadyBoost"...... it also helps with ReadyBoot and prefetch in general.

 

[DanS]

While I didn't mention anything about "side effects", here you go:

Windows Vista uses the same boot-time prefetching as Windows XP did if
the system has less than 512MB of memory, but if the system has 700MB
or more of RAM, it uses an in-RAM cache to optimize the boot process.
The size of the cache depends on the total RAM available, but is large
enough to create a reasonable cache and yet allow the system the
memory it needs to boot smoothly.

After every boot, the ReadyBoost service (the same service that
implements the ReadyBoost feature just described) uses idle CPU time
to calculate a boot-time caching plan for the next boot. It analyzes
file trace information from the five previous boots and identifies
which files were accessed and where they are located on disk. It
stores the processed traces in %SystemRoot%\Prefetch\Readyboot as .fx
files and saves the caching plan under
HKLM\System\CurrentControlSet\Services\Ecache\Parameters in REG_BINARY
values named for internal disk volumes they refer to.

The cache is implemented by the same device driver that implements
ReadyBoost caching (Ecache.sys), but the cache's population is guided
by the ReadyBoost service as the system boots. While the boot cache is
compressed like the ReadyBoost cache, another difference between
ReadyBoost and ReadyBoot cache management is that while in ReadyBoot
mode, other than the ReadyBoost service's updates, the cache doesn't
change to reflect data that's read or written during the boot. The
ReadyBoost service deletes the cache 90 seconds after the start of the
boot, or if other memory demands warrant it, and records the cache's
statistics in
HKLM\System\CurrentControlSet\Services\Ecache\Parameters\ReadyBootStats
, as shown in Figure 2. Microsoft performance tests show that
ReadyBoot provides performance improvements of about 20 percent over
the legacy Windows XP prefetcher.


More specifically:
"After every boot, the ReadyBoost service (the same service that
implements the ReadyBoost feature just described) uses idle CPU time
to calculate a boot-time caching plan for the next boot."

Thus, as I mentioned, "ReadyBoost service does more then just run
ReadyBoost"...... it also helps with ReadyBoot and prefetch in
general.

Hmmmm. Don't know why I didn't didn't pick up on that.