> > Given that this is a performance-based feature, has there been any > profiling > done to: > 1) make sure that when disabled, performance is the same as before this > was > When dissabled, the only additional overhead are a few extra checks of the global variable $::perfmon (just like adding a few more debug statements). I can't measure any cpu load of this. There is a little bit more memory as a data structure is set up at startup for each item monitored. But other than this you should not notice it...!
> > 2) track how much (if any) performance drop may be due to performance > monitoring > when enabled. > I have monitored cpu load and time to log and can't notice any significant difference when logging. The critical performance related ones incur less penalty if the log is at the beginning of the list of buckets anyway (as log walks an array of buckets to decide which counter to increment). So in summary, yes I've profiled and not measured anything significant. -- Triode _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
