-
Notifications
You must be signed in to change notification settings - Fork 479
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
[Request] Enable point batching by default #138
Comments
We will leave the decision to the developer, as he understands exactly how to act on the data. |
Writing many small requests is a common performance issue that new users run into. Enabling batching by default will eliminate these issues for new users. Please reconsider changing the defaults. |
And what should be sensible defaults for amount, time, and so forth |
I think the following would be sensible defaults.
|
Ok, but if someone wants different settings, what would be the workflow ? stop the already running batchprocessor and create a new one with the desired settings. |
@jackzampolin agree with @majst01, every developer should set their batch parameter. if provide batch used hard code parameters, it may cause issue not easy to be found. So I also think this issue should be closed. WDTY? |
As i already said, this is the wrong idea. |
InfluxDB is significantly more performant when points are written in batches. Making the default behavior of the client point batching should help increase performance for people unfamiliar with InfluxDB.
@majst01, Please consider making the following setting enabled by default:
The text was updated successfully, but these errors were encountered: