thanks for the reply ... meanwhile i've been also on the phone with marnix to find out there is even more in the game ...
are you using a software raid or some hardware raid controller (if the latter, which model) and is there a special reason you formated the raid-volume intended to be read from as journaled (though this should not affect read-access at all)?
swap-file on special volume ... does this volume reside on a seperate disk or just on a partition (eg. on the system drive)?
the *CPU usage* you're referring to above relates to *threading* IMO (one process is using only one thread instead of many ... had to get some more background-info to comment on that, but we could think of it as possible reason though file access is a seperate beast).
the *testing program* to load data would also have to mark the loaded data as *not to be paged out* what is an interesting idea but beyond my resources ... the *loading gap* after the first sequence is strange anyway.
thanks for the offer with iChat but i'm working from home this week where i don't have a mac at my hands currently ...
what made me avoid SSDs so far is the fact i noticed strange latency spikes (with read-access) on several models but i'm going to repeat my tests with an intel X25-M postville generation-2 next week ... what also looks interesting is the OWC SandForce series ... we had to find out its caching behaviour though ...
and remember: only a CRAY can run an endless loop in just three seconds.