A very large configuration -- using a lot of disk devices (several thousands devices seen on the machine) can see the iostat and vmstat commands to take a lot of time on Solaris 10.
For example, a configuration with 7700 disks seen on the machine can take more than 16 hours to run the following command on a T2000 running Solaris 10 (before Update 4) - eating 100% of a CPU:
iostat -xnCz -Td 60 61
With the new algorithms provided by S10 Update 4 (fixing for example 6402814 -- that should be included in the kernel update 120011-03/120012-03), the same command is running for a little bit more than 2 hours also eating 100% of a CPU (90% user time, 5% system).
--> This is still considered too long !