Make Vector aware of available memory
### A note for the community <!-- Please keep this note for the community --> * Please vote on this issue by adding a π [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * If you are interested in working on this issue or have submitted a pull request, please leave a comment <!-- Thank you for keeping this note for the community --> ### Use Cases We have had discussions floating around this in various issues, but I couldn't find a reference issue for it so creating this one. Users have had issues in running Vector in memory constrained environments where it'd be better for Vector to apply back-pressure than increase memory usage when it is close to its cap, thus avoiding an OOM kill. ### Attempted Solutions _No response_ ### Proposal Vector is "memory capacity aware" and applies back-pressure rather than allocating when it is at risk of being OOM killed. ### References * https://github.com/vectordotdev/vrl/issues/82 * https://github.com/vectordotdev/vector/issues/11770#issuecomment-1068853439 * https://github.com/vectordotdev/vector/issues/17123 ### Version vector 0.20.0 (x86_64-apple-darwin 2a706a3 2022-02-10)
Posted by jszwedko on Mar 22, 2022, 8:37 PM
Tags
Related issues
- [Meta] Feedback on granular control over Copilot changes
- unexpected status 401 Unauthorized issue
- [MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
- [CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
- Video stops playing after some minutes
- [MODEL] Claude verbose code comments by default β ignores instructions to stop.
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
github (Software)
[Meta] Feedback on granular control over Copilot changes
unexpected status 401 Unauthorized issue
[MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
[CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
Video stops playing after some minutes
[MODEL] Claude verbose code comments by default β ignores instructions to stop.
Scope Codex VS Code chats to the current workspace/project
Update on "Co-authored-by: Copilot" in commit messages
Make Vector aware of available memory
### A note for the community <!-- Please keep this note for the community --> * Please vote on this issue by adding a π [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * If you are interested in working on this issue or have submitted a pull request, please leave a comment <!-- Thank you for keeping this note for the community --> ### Use Cases We have had discussions floating around this in various issues, but I couldn't find a reference issue for it so creating this one. Users have had issues in running Vector in memory constrained environments where it'd be better for Vector to apply back-pressure than increase memory usage when it is close to its cap, thus avoiding an OOM kill. ### Attempted Solutions _No response_ ### Proposal Vector is "memory capacity aware" and applies back-pressure rather than allocating when it is at risk of being OOM killed. ### References * https://github.com/vectordotdev/vrl/issues/82 * https://github.com/vectordotdev/vector/issues/11770#issuecomment-1068853439 * https://github.com/vectordotdev/vector/issues/17123 ### Version vector 0.20.0 (x86_64-apple-darwin 2a706a3 2022-02-10)
Comments (0)
No comments yet. Start the discussion.