I was thinking of covering this first with a multi threaded unit test to verify no concurrency issues and to give an idea of maximum throughput, since a centralised counter working off logging API markers could be used anywhere.
I will do before after testing as well. Ian On 26 February 2013 17:55, Carsten Ziegeler <[email protected]> wrote: > Just a general comment especially on statistics, whatever we do, we > carefully need to check the performance impact. Over the past years, > I've seen too many approaches where a simple statistics like "number > of incoming requests" was a real bottleneck under load (I think one of > our first implementations in Sling engine had a similar problem). So > while such an information is interesting and important it shouldn't > bring down the server or reduce the performance significantly. Doing > some benchmarking before and after should do the trick. > > Carsten > -- > Carsten Ziegeler > [email protected]
