NCQ and the low memory crunch (Virtual Mem test).
When an application requests more memory than available physically, You have:
(1) Windows trying to page-out dlls,
(2) Windows filling the Virtual Memory "file" with whatever the app wants, and
(3) The app reading and writing to disk (What alse would the app need the memory for but reading/processing/writing a big data set?)
(4) Other apps taking turns to be swapped in/out
Any application might become a HD multitasking nightmare.
So what?, so everybody has a lot of memory, right?
So I thought until I started wroking with letter sized, 24-bit scans. Or when I opened Outlook express and I got 4 newsgroups with 14,000 posts each, or when I had Excel and Word docs open with dynamic links between them; (In these examples, it is not the application itself, but data set size the app works with.
Also, most people have many programs running in the background (Kazaa, Gator, Antivirus, Firewall). Even 512MB on WinXP might not be enough.
I was just wondering if NCQ could boost performace when a computer becomes unresponsive when available physical memory becomes low.
I think this fact might explain some of the results obtained so far (Not the data being written in/out but all the VM/paging activity when multiple apps are running).
Cheers Eugene, this is a great site.