View Revisions: Issue #6687
| Summary | 0006687: Ready queues for more efficient push/pulls | ||
|---|---|---|---|
| Revision | 2025-01-02 15:12 by elong | ||
| Description | Keep a list of queues that are ready with changes to push or pull, so the service only needs to open communication and query changes for those queues. This makes the system more efficient when there are multiple channel queues in use. During a pull of the default queue, a list of ready queues is returned as a HTTP header, letting pull service know other queues that should be pulled. Push service also uses the list of ready queues to filter which queues it should query for changes. | ||
| Revision | 2025-01-02 15:23 by elong | ||
| Description | Keep a list of queues that are ready with changes to push or pull, so the service only needs to open communication and query changes for those queues. This makes the system more efficient when there are multiple channel queues in use. During a pull of the default queue, a list of ready queues is returned as a HTTP header, letting pull service know other queues that should be pulled. Push service also uses the list of ready queues to filter which queues it should query for changes. Parameters control this feature and hold long the list of ready queues should be cached. sync.use.ready.queues=true cache.ready.queue.time.ms=5000 |
||