Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in
Toggle navigation
N
nexdpi
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
sysadmin
nexdpi
Commits
5dd8418e
Commit
5dd8418e
authored
Apr 25, 2021
by
Stefy Lanza (nextime / spora )
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update README.md
parent
5e519d70
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
2 deletions
+6
-2
README.md
README.md
+6
-2
No files found.
README.md
View file @
5dd8418e
...
...
@@ -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!
### 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
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
...
...
@@ -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.
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
kernel is a good start!
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment