> Averaging over three trials on an unloaded system, I got 21.0 seconds
> with stats_command_string off, 27.7 with it on, or about 32% overhead.
>
> My conclusion is that stats_command_string overhead is non-negligible
> for simple commands. So I stand by my previous opinion that it should
> not be turned on without the DBA taking explicit action to turn it on.
> Do you want it on in every future benchmark, for example?
How about with the stats_collector on? ie. Recording block and row level
stats?
Chris
