Now ScheduledExecutorService is in use and there is no default implementation, which allows to execute metrics updates in the same thread they took place. Meantime, it seems to be bad that generation of slices, event handling and expiration will be handled in the same thread.
It's suggested to introduce such implementation (or change MetricRegistry constructors to support same thread execution) considering the point about still handling other events in a different thread.
Such feature could be useful for
- testing
- use cases when context switching should avoided
Now ScheduledExecutorService is in use and there is no default implementation, which allows to execute metrics updates in the same thread they took place. Meantime, it seems to be bad that generation of slices, event handling and expiration will be handled in the same thread.
It's suggested to introduce such implementation (or change MetricRegistry constructors to support same thread execution) considering the point about still handling other events in a different thread.
Such feature could be useful for