: example scenario during testing: during a test run - the test harness will : fire requests at request handler (partItemDescSearch) and all numbers look : fine. then after the test harness is done - the metric : avgRequestsPerSecond does not immediately drop to 0. instead - it appears : as if JMX is somehow averaging this metric and gradually trending it : downward toward 0. : : continual checking of this metric (in the JMX tree - see screen shot) shows : the number trending downward instead of a hard stop at 0. : : is this behavior - just the way jmx works?
It's nothing special about JMX, it's just the way RequestHandlerBase computes this number -- it's the average number of requests per second that this handler has seen over it's entire lifetime -- ie: from the moment the SOlrCore was created/started until now. it is quite simply... (numRequests*1000) / (currentTimeMillis()-handlerStart) If you want an average over a finer granularity of time then that you can have your JMX client sample the numRequests stat from the hander at some interval (ie: record the value every minute, subtract the last value from the current value, divide by 60 and that will tell you the average number of reuqests per second, sampled per minute. -Hoss