What you describe is how I undertook the monitoring, although I re-booted occasionally to clear the system cache.

I should have perhaps explained what I was trying to demonstrate in post #237. I wanted to show the maximum MB/s speeds that occurred on the device when undertaking typical tasks within a typical environment.

I captured the data Xfer statistics only to show that the maximum observed MB/s speeds were based on a reasonable amount of data being generated during the observation period.

The data Xfer totals are not necessarily derived solely from the task I indicated. Background OS tasks and cache movements would have had an impact. i.e. a read on the device could have been instigated before the monitoring period started.

Excluding file copying the MB's speeds are surprising low, although all of the tasks require processing time, so it should not be that surprising I guess.

With regards to system cache I've noticed that although I don't stress out the SSD, Cacheman 7 can improve the fast IOP count on both the system and the device. With a single device using Cacheman 7 I can achieve a higher fast IOP count than what I could with a Raid 0. (And it's a lot cheaper ).

TBH it is system cache that I find more interesting now in terms of looking for performance improvement with SSD. (Napalm (if you read this thread) it's taken me a long time but I'm getting there now )

I don't know how to test or prove it, but I would bet that something like Cacheman 7 that was designed specifically for SSD could really help to improve SSD performance. I say this as system cache has presumably been developed to mask the slow speed of a HDD rather than take advantage of the speed of a SSD.