Quote: "The program you're referring to is the MPL3D Solar System, right? Does it do a lot of hard disk file access?"
Yes you are right about the program, but it doesn't really access the hard disk that much.
Heaviest stuff is preloaded at the start. Backdraw of this is that it eats somewhat a lot of memory, let's say around 1Gb of Ram. I don't really know how much video ram is consumed.
I think that the bottleneck is a RAM <-> VRAM swapping. Since the netbook shares physically this memory, it performs faster.
This is specially noticeable with HDR and full screen shaders.
I don't know why, but the netbook doesn't drops performance with HDR, while desktop cards use to halve FPS.
This all makes me think that DBPro is not loading the textures and other stuff into the VRAM, but into RAM. Then it has a performance drop when swapping. Textures should be loaded into RAM only if VRAM has exhausted.
GTX 295 has a huge 1GB VRAM, but it makes no difference even with the lowest texture size.
On it's side the netbook (Dell Latitude E6520) has 8GB of shared memory, and HD3000 probably can only access 1GB, but the swapping is faster.
Anyway, there should be no memory swapping with low res textures, so I think that there must be something wrong with the way DBPro is handling the loading. There have been issues of this kind in the past.
Oh and I also tried different nVidia drivers, and XP/W7. No difference.
Dunno, I think performance is being lost by DBPRo itself at some point, when dealing with the hardware.
Maybe because DX9 is not supported natively any more?