I have a program that I usually run on a Win7 PC but occasionally run on a Win10 PC. The program reads about 2.1GB of data into storage from an SSD drive. On my Win7 system this read takes about 26 seconds. On the Win10 system it takes 4 minutes.

The two PCs have different configurations, but neither is s slouch:
Win7 x64 Pro Intel i7-4771, 3.50Ghz, 16GB RAM
Win10 x64 Pro Intel i7-930, 2.80GHz, 6GB RAM

The performance characteristics of the SSDs are different, but not enough to cause the performance difference. The average read transfer rate is 373.8 MB/sec on the Win 7 drive vs. 230.5 MB/sec on the Win 10 drive. (I don't know the blocksize used in the speed test, but I don't know the blocksize of the data files either.)

The RAM size is an obvious big difference between the two boxes, but once the data files are loaded I'm using just a little over 4GB on both systems so I'm not running out of storage.

I see a huge behavioral difference when viewing the loading using Process Explorer. On the Win 7 box there is a big burst of I/O and cycle use for those 26 seconds. On the Win 10 box there are short bursts of activity (about 5, as I recall) with very long pauses in between. It's almost as though program's I/O was being throttled, but I don't think that's the case. One of the bursts activity (the 2nd or 3rd) is always much longer than the others - 4 or 5 times longer. The amount of activity does not seem to (directly) cause the pauses. The program reads data from 5 different sub-directories and probably does some processing in between those blocks of reads, but the program's cpu usage is high during the bursts of reads and drops way off in between bursts. It's not like it's CPU-bound during those pauses.

Are there any incorrectly set tuning options in Win10 that might cause this kind of behavior? I can't imagine what they would be or I would have already tweaked them. Or other data I need to collect that might point to the problem?