Skip to content
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.

Tune / finalize the queue's batch and timing parameters #58

Open
Tracked by #16
faec opened this issue Jun 15, 2022 · 2 comments
Open
Tracked by #16

Tune / finalize the queue's batch and timing parameters #58

faec opened this issue Jun 15, 2022 · 2 comments
Assignees
Labels

Comments

@faec
Copy link
Contributor

faec commented Jun 15, 2022

Right now the shipper's internal Beats memory queue uses fixed defaults for its initialization parameters (batch minimum event count and timeout). These are placeholders to bootstrap the shipper, and should be replaced once things are fleshed out enough to run a comparison of the options. This may involve removing those parameters entirely as we rework internal batch handling, but if not, we should decide on a baseline we're happy with and expose configuration hooks if appropriate.

@jlind23
Copy link
Contributor

jlind23 commented Apr 4, 2023

@faec @leehinman this issue hasn't been update for a while, is it still relevant? If yes, we should probably add it to one of our upcoming sprints

@leehinman
Copy link
Contributor

yes, very relevant

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants