Is readyboost only useful for slow or low-memory systems?


Recommended Posts

True and not true .. It is true that all applications use virtual memory however this is mainly to garrantee all apps get enough RAM as the system may not have enough RAM to run everything at the same time. You can quickly test your own theory by turning off the page file (the official Microsoft name for it).

Please stop trying to sound like you know what you're talking about. I didn't say anything about apps and the above statement is as incorrect as your first. And FYI, you CANNOT disable the pagefile, you can only disable your ability to manage it. If you "turn off" the pagefile the OS will continue to page when and where it likes and you will never know it. Clearly the paging will be less efficient (and less utilized) which is why many systems will slow down significantly when the pf is disabled.

The subject of pagefiles has been done to death and pagefile threads invariably become contentious - in no small part because there are always plenty of people who like to sound intelligent on the subject but who are simply spouting nonsense.

One thing to note about readyboost: it can be useful if you hibernate your machine. If you have 4GB memory and a 4GB readyboost stick, it will put the hibernation file on the stick which can dramatically improve resume times.

This seems like a really stupid thing to do. Readyboost was made because flash drives don't have the pesky seek time problem that hard drives too. When you tell a hard drive to read or write a file, it has to move the hard drive heads to the proper position to read them. Flash memory doesn't have to do this, so if you're dealing with lots of small bits of data or very small files, flash drives are faster. This is the basis for Readyboost.

However, for continuous reads, like for example reading a large, singe fairly un-fragmented 4GB file back into memory, the read speeds of a hard drive should be much faster, and then you don't have to worry about not having the flash drive in the USB port when you resume from hibernate.

I don't currently have a vista machine to verify what you're saying her, but are you SURE that it's true?

And, as others have said, the readyboost service also controlls the readyboot service. As a result, it shouldn't be disabled. Unless, of course, you want slower boot times and no boot optimization.

wrong. absolutely wrong. disabling the service will never slow your boot times

the only thing disabling the service does it make it so the OS can't use an external drive to help your computer boot faster. it only prevents you from gaining the benefit of a readyboost device.

there is a very big difference between the two. if you take a default installation with the service enabled but no readyboost device plugged in and compare the speeds to a default installation with the readyboost service disabled, there will be absolutely NO difference in boot speed

the way you said it makes it sound like readyboost helps all computers boot faster whether they have an readyboost device or not. it only gives you the opportunity to take advantage of an external drive. disabling it is not a negative, you just don't get to take advantage of the positive

Edited by PermaSt0ne
wrong. absolutely wrong. disabling the service will never slow your boot times

the only thing disabling the service does it make it so the OS can't use an external drive to help your computer boot faster. it only prevents you from gaining the benefit of a readyboost device.

there is a very big difference between the two. if you take a default installation with the service enabled but no readyboost device plugged in and compare the speeds to a default installation with the readyboost service disabled, there will be absolutely NO difference in boot speed

the way you said it makes it sound like readyboost helps all computers boot faster whether they have an readyboost device or not. it only gives you the opportunity to take advantage of an external drive. disabling it is not a negative, you just don't get to take advantage of the positive

Readyboot is controlled by the readyboost service, but readyboot has NOTHING to do with an external drive, it uses RAM to speed up your boot times, disabling it WILL slow down bot times.

When a Windows system boots, a large number of files need to be read intomemory and processed. Typically, the files which need to be called upon boot depend on which services and startup programs the user requires to start the system up. This process can be quite inefficient since multiple portions of the same file may be accessed at different times during bootup. To reduce this inefficiency, the system can cache data that is frequently called upon during the boot process. Practically, code and data accessed during boot are traced by the system (ReadyBoost in this case) and the information is recorded as a cache file. ReadyBoot is, incidentally, implemented by the ReadyBoost service described earlier. ReadyBoost will continue monitoring the system for 90 seconds after start of the boot, or until 30 seconds after the shell has started, or until 60 seconds after all services have been initialised, whichever elapses first. ReadyBoost uses idle CPU time to calculate a caching plan for the next boot based on historical data it has collected as trace information from the previous boot (typically information pertaining to which files were accessed and where they are located on disk). 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.

Readyboost is not designed to be used on systems with more than 2GB RAM.

I've heard people on the Readyboost team talking about using flash drives on computers with up to 2GB RAM, but not more.

Personally, I wouldn't use it on a computer with more than 1GB RAM. I used it on my old laptop for a while, and it didn't help at all. The computer had 1GB RAM.

Readyboost is not designed to be used on systems with more than 2GB RAM.

I've heard people on the Readyboost team talking about using flash drives on computers with up to 2GB RAM, but not more.

Personally, I wouldn't use it on a computer with more than 1GB RAM. I used it on my old laptop for a while, and it didn't help at all. The computer had 1GB RAM.

It really depends on how you use your system. Don't assume everyone uses their system just as you would.

It really depends on how you use your system. Don't assume everyone uses their system just as you would.

It's more an issue of design. The feature is designed to provide a performance gain to computers with low amounts of RAM. The Readyboost team (the people at Microsoft who designed and built the feature) have said that Readyboost was designed for computers with between 512MB RAM and 2GB RAM. Common sense dictates that the more RAM you have, the less noticable a Readyboost cache would be.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!