Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance Discussion #200

Open
poy opened this issue Aug 30, 2018 · 1 comment
Open

Performance Discussion #200

poy opened this issue Aug 30, 2018 · 1 comment

Comments

@poy
Copy link

poy commented Aug 30, 2018

I am curious about improving performance for splunk ingestion. We have had many customers use this product but run into problems with splunk putting back pressure on the nozzle. We have deduced this to be the cause by observing the nozzle's diode dropping data.

Has the option to write into splunk via batching been explored? In most systems (and therefore I would assume splunk as well), this is the first step to making ingestion faster.

@shinji62
Copy link
Contributor

No back pressure on nozzle, as it will throw away logs if the buffer reach a certain limit.
It's just normal behaviour as Splunk could not ingest logs fast enough.

Same as doppler / Loggregator not having back pressure implementing the same diode concept/code.

Not I did'nt check yet the options of using batch ingestion.

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

No branches or pull requests

2 participants