Closed mstemm closed 3 years ago
My only concern is the memory footprint of the event batches. The default reusable event batch will allocate a memory buffer of size DefaultBatchSize * DefaultEvtSize
, which until now was about ~32MBs. With this change, every source plugin would use ~128MBs of memory by default, which I think is a bit excessive.
Should we also decrease DefaultBatchSize
to 64 or 128? Other than that, this looks fine to me!
My only concern is the memory footprint of the event batches. The default reusable event batch will allocate a memory buffer of size
DefaultBatchSize * DefaultEvtSize
, which until now was about ~32MBs. With this change, every source plugin would use ~132MBs of memory by default, which I think is a bit excessive.Should we also decrease
DefaultBatchSize
to 64 or 128? Other than that, this looks fine to me!
I agree. My vote goes to decrease DefaultBatchSize
to 128 (so we will get the same memory footprint, ie. 128 x 256k = ~32MB). Although this choice is a bit conservative, we can reserve to perform an accurate benchmark and then fine-tune the defaults again.
Moreover, IMHO it is worth highlighting more in the documentation that these parameters can be easily configured by the plugin author.
Okay, I decreased the number of events and kept the event size at 256k.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leogr, mstemm
The full list of commands accepted by this bot can be found here.
The pull request process is described here
LGTM label has been added.
Plugin events are no longer capped at 64k, and we think 64k might be too small for some plugins, so change the default to 256k.
Signed-off-by: Mark Stemm mark.stemm@gmail.com
What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area plugin-sdk
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: