On 2/2/12 21:59 , Niclas Hedhman wrote:
So, I have made some initial work on the Metrics SPI. 1. Created the SPI, based on the Metrics I showed a few days ago, so I don't have to re-invent it all again. 2. Made a "Yammer" implementation of the SPI. 3. Added "Counter" to UnitOfWork management, so one can easily detect UoW leaks. 4. Added "Timer" to UnitOfWork management. so one can get uow/sec and timing how long they take etc etc.For point 4, the following data is captured; UnitOfWork Timer: count = 36725 mean rate = 6109.15 calls/s 1-minute rate = 5221.40 calls/s 5-minute rate = 5221.40 calls/s 15-minute rate = 5221.40 calls/s min = 0.02ms max = 198.49ms mean = 0.13ms stddev = 1.07ms median = 0.09ms 75%<= 0.15ms 95%<= 0.28ms 98%<= 0.32ms 99%<= 0.39ms 99.9%<= 4.75ms for a small test that create 20000 empty entities and then read them all again. Now, the question is more; What metrics do we want from the Qi4j Runtime?? Meanwhile, I will continue to make a library that allows you to attach metrics concerns to any composite via this mechanism. Another question; Should I just push this to 'develop' or keep it in a feature branch?
Looks useful enough to go into develop I think. /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
