here is what i think.
paging does so in very small portions , run a test of the flash disk writing and reading in random 4k sizes , most of them choke , but then so does a hard drive especially random.
run the same random 4k test on the hard drive.
what they do not say, is when you require paging MOST, it might be in 4k sections, but they did not cover having to page out a LOT at one time, while that would be small chunks, it could still be somewhat sequential, depending .
if ever paging was occuring at the Same time that the hard drive was being needed heavily. any different disk item might speed it up some.
if you load the worlds biggest picture into a photo program, and it sucks up all your memory and something from the memory gets pushed to paging.
The hard drive being active during the same task or a different task would make paging to it quite slow. this is why they normally recommend that the paging file ON the hard disk be in the same area as the data , the reduced head jump distance to get there. (situational)
It is most preffered that paging would be on seperate hard disk item that will NOT be doing anything when paging is occuring.
sometimes USB access can require more cpu, or clog up the communications going on behind the scenes, when doing your tests, note the CPU use, and general speed feel of the operations of the computer. higher cpu use, and clogged i/o from something that isnt as fast as an internal could negate the postive effect of the more random access.
and speaking of random, flash is not
it is Block, that is why it doesnt do that much better than HD on random, and why sequential is still faster on flash.
you have 4 gig, not many things will even allocate a virtual of that size. and the minor paging that occurs putting some unused system stuff in is very small.
---------------------------------------------------------------------------------
sorry if this is side tracked
http://windows.microsoft.com/en-US/windows7/products/features/readyboost
i dont know readyboost, but other than not having a dependance on the flash, it is paging. cache style, if it is not found in the flash then it jumps to the disk
http://blogs.msdn.com/b/tomarcher/archive/2006/06/02/615199.aspx
Ok if the paging has to be backed up on the disk, for this, then it must write to the disk (and the flash), so reads would be all cute and fast, but writes would be slow.
.