Ruby flush file buffer

It's running as a daemonset so one fluentd pod per node. Looking at the limits of cloudwatch logs , I think this is our bottleneck. Skip to content. Star New issue. Jump to bottom. What is a recommended file buffer configuration? Copy link. Thanks for the reply repeatedly I'm not familiar with cloudwatch logs's import performance. Am I expecting too much? I'm gonna close this since I'm pretty sure now it's not a config problem. Sign up for free to join this conversation on GitHub. Already have an account?

Sign in to comment. Improve this answer. Steve Midgley Steve Midgley 2, 1 1 gold badge 17 17 silver badges 20 20 bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown.

The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related Hot Network Questions. As we saw previously, passing the path to File. Also, after asking for file. Calling size on the file instance has a documented side effect. That explains where our string went after writing it!

Flushing the buffer pushes its contents to the operating system.