Skip to content

N
nexdpi
Commit 5dd8418e authored by Stefy Lanza (nextime / spora )'s avatar Stefy Lanza (nextime / spora )
Browse files
Options

Update README.md

parent 5e519d70
Hide whitespace changes
Inline Side-by-side
Showing with 6 additions and 2 deletions
README.md
View file @ 5dd8418e
...@@ -28,8 +28,8 @@ and then apply your limitation there. ...@@ -28,8 +28,8 @@ and then apply your limitation there.
This is CRAP and a pain in the ass for performances, don't use it! This is CRAP and a pain in the ass for performances, don't use it!
### NOTE On Linux Kernel and HyperThreading ### NOTE On Linux Kernel, HyperThreading and ksoftirq
Apparently when you do anything more complex that just a couple of static routes Apparently when you do anything more complex that just a couple of static routes
and some NAT, hyperthreading enable on the CPU cores cause a noticeable loss in and some NAT, hyperthreading enable on the CPU cores cause a noticeable loss in
performances. If your machine has HT enabled, disable it either from the BIOS performances. If your machine has HT enabled, disable it either from the BIOS
...@@ -42,6 +42,10 @@ machine load goes way too high to maintain a proper throughput. ...@@ -42,6 +42,10 @@ machine load goes way too high to maintain a proper throughput.
Installing a PREEMPT RT kernel solved the issue in an excellent manner. Installing a PREEMPT RT kernel solved the issue in an excellent manner.
ksoftirq continue to consume a LOT of resources, so, limiting it by lowering the
priority of the thread can help too: in the rc.local there is a line to do it.
Many other optimization can be done on the network stack, but using the proper Many other optimization can be done on the network stack, but using the proper
kernel is a good start! kernel is a good start!
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment