> Performance testing > > On the performance front, life is always a bit more tricky -- performance > testing is a subtle art. However, the most clear lessons are that (a) > testing with diverse workloads and diverse environments is extremely > important, (b) you should do multiple runs and use ministat(1) to analyze > results, and (c) that you want to compare apples with apples -- use the > same hardware/configuration wherever possible. Watch out for annoying nits > such as partition layout affecting I/O throughput for two different > installs on the same disk. > > Pick something you think is important to you: bytes/sec over TCP on > loopback, web hits/sec, NFS ops/sec, disk I/O transactions/sec, and do some > comparison between 7.2 and 8.0. If you find improvement -- great! If you > find a regression, please start a thread on current_at_ to help get it > diagnosed. And if you want help doing performance measurement for a > particular workload that isn't well studied, send some e-mail to > performance_at_ to ask for advice on how best to measure it. what happened to the performance tracking project? that would ease finding performance regressions...Received on Wed Aug 12 2009 - 11:02:04 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:53 UTC