The problem is that they cannot be interpreted by the end user and even if they could here is no clear corresponding lever to tweak at this time. It makes sense to leave them in but with a default threshold of 0, such that they must be enabled, by a knowledgeable user, with a limit that makes sense for a given application environment.
2009/12/2 Fredrik Jonson <fred...@jonson.org> > Gary Tully wrote: > > > Those log messages are developer debug aids that were added early on in > the > > dev cycle and possibly should now be removed. > > If those messages can be interpreted by end user why not leave them in? > Right > now I agree that they might be of little use, because we haven't got any > yard > stick to measure against. It could become useful if someone could say, > "well > anything below 500 ms is nothing to worry" - or - "well, once you go above > five > seconds you really need to consider the configuration and the hardware". > > I understand that it all depends on the load, even so lets start somewhere. > As I've seen mentioned that anything below 500 ms will be filtered ouy in > the > future, can we assume that's a "safe" level? And if so, where is a first > rough > upper bound where you would start to monitor the situation? 3 s? 5? 10? 30? > > Thanks > -- > Fredrik Jonson > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
