Too much Windows Vista cache, a bad ting? Well, apparently yes, through Excessive Cached Write I/O and Excessive Cached Read I/O. As you probably know by now, cache is connected with boosting the performance of data accessing processes that target sluggish storage media. In an ideal scenario, the data or the code pages would be completely located within the system memory. The speed at which data is accessed, in the physical RAM, exceeds by far that of similar processes that involve a hard disk, by approximately 1 million times. But, because of the usually limited amount of RAM, the operating system will have to deal with system cache. (more…)

algorithm, hard disk, memory manager, msdn, operating system, physical memory, physical ram, processes, storage media, system cache, system memory, system performance, vista, Windows

Windows XP contains several tweakable memory settings in the registry, one of which is the DisablePagingExecutive registry key. This controls whether the operating system will transfer its essential driver and kernel files to the ‘virtual memory’ (the page file on the hard disk). It defaults to allowing this.

Obviously, transferring portions of the system to hard drive memory can considerably slow things down, and it appears that Windows XP does this periodically, whether or not the system is actually low on physical memory (RAM).

If you have 256MB of system memory or more, try this registry tweak to force Windows to keep its operating data in main memory: (more…)

drive memory, hkey local machine, main memory, memory management, memory ram, memory settings, open regedit, physical memory, registry tweak, system memory, virtual memory, Windows, windows xp, xp

Windows Vista “out of memory” errors are intimately connected with the way the operating system manages virtual address space. On Microsoft’s latest operating system, applications have their very own private virtual address space. You must understand that there is no correlation between the virtual address space available to a certain program and the total volume of physical memory installed on the computer. On 32-bit platforms, applications are generally limited under a 2 GB boundary as the maximum size of the virtual address space. In this context, the “out of memory” errors in Windows Vista are generated by applications that have eaten up all the virtual address space allocated to them.

“Every memory allocation, file mapping, or library that is loaded by an application consumes space in this virtual address space. When the application consumes all its virtual address space, any additional such operations fail. Although all applications should be coded to handle memory allocation failures, many applications do not recover correctly from such failures. Therefore, the programs may become unstable or stop responding after they recover from such failures”, Microsoft informed. (more…)

latest operating system, memory allocation, memory copy, memory errors,…

Just because Windows Vista is such a resource hog, the operating system features the Windows Experience Index, a rating system designed to measure the capability of the computer’s hardware configuration in order to assess the overall performance of the machine through a numeric base score. The algorithm for determining a base score ranging from 1.0 to 5.9 is directly connected with the processor, physical memory (RAM), graphics, gaming graphics and the primary hard disk. However, there are a few contexts in which the Windows Experience Index, the mechanism at the basis of the system rating will present and erroneous score for the hardware configuration.

This is a problem observed following the commercial release of the operating system back in January 2007. (more…)

commercial release, Hardware, hardware configuration, hardware configurations, hard disk, memory ram, microsoft, operating system, physical memory, ram graphics, random access memory, resource hog, video card, vista, Windows, windows experience