You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proposal:
According to the docs, WriteApi supports batching. If I understand correctly, there is something like an internal queue to send data to server in batches. An application is actively writes data, but I cannot control from my code if sending is fast enough and data are not infinitely collected in memory. It would be very useful to control the current size of the queue and set it's max size.
Current behavior:
Cannot find how to control and limit writing to DB server.
Desired behavior:
Be able to setup and control how data is written.
Alternatives considered:
Without the requested function, I have to implement my own queue and add new data by WriteApiAsync.
Use case:
Industrial monitoring systems generate a lot of data (we develop SCADA). And it's important to clearly understand if our service is able to send all data or not, and avoid using too much memory.
Thank you for your work.
The text was updated successfully, but these errors were encountered:
2mik
changed the title
Limit and control of writing queue
Limiting and controlling a write queue
Mar 5, 2023
Proposal:
According to the docs, WriteApi supports batching. If I understand correctly, there is something like an internal queue to send data to server in batches. An application is actively writes data, but I cannot control from my code if sending is fast enough and data are not infinitely collected in memory. It would be very useful to control the current size of the queue and set it's max size.
Current behavior:
Cannot find how to control and limit writing to DB server.
Desired behavior:
Be able to setup and control how data is written.
Alternatives considered:
Without the requested function, I have to implement my own queue and add new data by WriteApiAsync.
Use case:
Industrial monitoring systems generate a lot of data (we develop SCADA). And it's important to clearly understand if our service is able to send all data or not, and avoid using too much memory.
Thank you for your work.
The text was updated successfully, but these errors were encountered: