Command latency metrics is collected on connection or server level. The client can collect latency metrics during while dispatching commands. Latency collector requires LatencyUtils to be on your class path. ![]() Command latency collection is enabled by default and can be disabled by setting commandLatencyPublisherOptions(…) to DefaultEventPublisherOptions.disabled(). The options allow configuring the percentiles, level of metrics (per connection or server) and whether the metrics are cumulative or reset after obtaining these. If you wish to do so, make sure that your events implement the Event marker interface. Events are published using a RxJava subject and the default implementation drops events on backpressure. Events are about connection state changes, metrics, and more. ![]() The event bus system is used to transport events from the client to subscribers. A provided EventExecutorGroup is not managed by the client and needs to be shut down once you do not longer need the resources. A provided EventLoopGroupProvider is not managed by the client and needs to be shut down once you do not longer need the resources.įor those who want to reuse existing netty infrastructure or the total control over the thread pools can provide an existing EventExecutorGroup to the Client resources. EventLoopGroups are obtained and managed by an EventLoopGroupProvider. Nameįor those who want to reuse existing netty infrastructure or the total control over the thread pools, the EventLoopGroupProvider API provides a way to do so. Values for the advanced options are listed in the table below and should not be changed unless there is a truly good reason to do so. A pool with fewer threads can cause undefined behavior. Every thread represents an internal event loop where all computation tasks are run. The number defaults to the number of available processors that the runtime returns (which, as a well-known fact, sometimes does not represent the actual number of processors). The number of threads in the computation thread pool. The number does not reflect the actual number of I/O threads because the client requires different thread pools for Network (NIO) and Unix Domain Socket (EPoll) connections. ![]() Every thread represents an internal event loop where all I/O tasks are run. The number of threads in the I/O thread pools. The basic configuration options are listed in the table below: Name
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |