-
Currently requests are packed and pushed into a Node.js Socket `stream.Writable`. This works as long as
- the amount of data generated is low,
- there is enough idle time in the event queue and/…
-
### Description
It would be nice to provide backpressure on handle metrics pushes to the Serve controller so that the controller does not become overloaded.
Relevant code is around these locatio…
-
Hi!
I found some references about backpressure and rxjava on other implementations: https://github.com/salesforce/reactive-grpc#back-pressure
I was reading all your doc but I can not found if g…
-
Here https://tokio.rs/tokio/tutorial/channels#backpressure-and-bounded-channels backpressure is mentioned in the title but the concept is not explained.
-
### Component(s)
receiver/filelog, receiver/journald
### Is your feature request related to a problem? Please describe.
This feature request is based on the FluentBit feature surrounding buffering …
-
### Environment
SaaS (https://sentry.io/)
### Steps to Reproduce
Over the last 30 days, we've experienced ~265 instances where backpressure has been marked as unhealthy due to a connection timeout …
-
Currently ws-rs seems to just queue up all messages, accumulating all data in memory. If I feed to much data, it fails with `Unable to send signal on event loop`.
Is there a blocking version of `ws…
-
The current definition of the `ReadableStreamTee` abstract operation includes an inherent flaw when it comes to backpressure signaling ... specifically, there isn't any. Whether `stream.[[controller]]…
-
Motivation:
I want to do some rate limiting and just fail the single task, eg when combined with `mapAsync`.
Currently seems I can't observe the backpressure.
`onBackpressure` is only been call…
-
Currently our system relies on the following invariant to hold in order to run steadily:
```
avg barrier latency < barrier injection interval
```
To ensure the above invariant, currently we have…