Skip to content
Discussion options

You must be logged in to vote

Well, after "some" digging I finally found out that the problem was not related to Nebula at all. A simple flood ping to another server in the same network would also stall randomly for a few seconds, and even pings to localhost every now and then. I discovered that audit logging was the culprit. Its buffers would fill up with messages and temporarily block the system call (sendto) that was causing the log messages. Now that is fixed I can achieve a stable 1Gbit/sec to another host.

I am still looking to maximize performance though. specifically by tuning the read_buffer and write_buffer sizes like you mentioned. Would I also need to tune net.core.rmem_max and net.core.wmem_max for that p…

Replies: 2 comments 5 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
5 replies
@JackDoan
Comment options

@jblt-sidn
Comment options

Answer selected by JackDoan
@JackDoan
Comment options

@jblt-sidn
Comment options

@JackDoan
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants