Documentation ¶
Overview ¶
worker-pool-bottleneck implements a http service that demonstrates a worker pool bottleneck. In particular the service simulates an application that has a queue processing pipeline that consists of:
1. ConsumeMessageWorker: Pulls messages from a queue. 2. DecodeMessageWorker: Decodes messages. 3. LLMMessageWorker: Makes a long-latency call. 4. PublishMessageWorker: Publishes messages.
The LLMMessageWorker is the bottleneck in the pipeline because it doesn't have enough workers to keep up with the other workers. This causes the ConsumeMessageWorker and DecodeMessageWorker to block on send operations.
The primary use case is to take screenshots of the timeline feature.
Click to show internal directories.
Click to hide internal directories.