Hi Bertrand, On 16/08/16 13:41, "Bertrand Delacretaz" <[email protected]> wrote:
>With the current SLING-5965 patch, getValue() takes more time the >more jobs are present. The alternative might be to just store the N >oldest job starting times. By default we have 2 thread pools (schedulers) and invoking getCurrentlyExecutingJobs on each of them returns only those really running - which are capped by the thread pools. So I don't think this is a performance issue. >Creating load while retrieving metrics looks risky to me in general as >it's when your system is in trouble that you might request those >metrics the most. Agreed - if there is indeed load. As I see it however (s.above) that's not the case. And calculating something in the background all the time, vs only when it's needed seems less performant to me. >2) Does the metrics library by default make all values available via >JMX as well? That I don't know, couldn't find it at least. Cheers, Stefan
