You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: administration/performance.md
+10-9Lines changed: 10 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,9 +2,9 @@
2
2
3
3
Fluent Bit is designed for high performance and minimal resource usage. Depending on your use case, you can optimize further using specific configuration options to achieve faster performance or reduce resource consumption.
4
4
5
-
## Reading Files with Tail
5
+
## Reading files with `tail`
6
6
7
-
The `Tail` input plugin is used to read data from files on the filesystem. By default, it uses a small memory buffer of `32KB` per monitored file. While this is sufficient for most generic use cases and helps keep memory usage low when monitoring many files, there are scenarios where you may want to increase performance by using more memory.
7
+
The `Tail` input plugin is used to read data from files on the filesystem. By default, it uses a small memory buffer of `32KB` per monitored file. While this is sufficient for most generic use cases and helps keep memory usage low when monitoring many files, there are scenarios where you might want to increase performance by using more memory.
8
8
9
9
If your files are typically larger than `32KB`, consider increasing the buffer size to speed up file reading. For example, you can experiment with a buffer size of `128KB`:
10
10
@@ -19,17 +19,18 @@ pipeline:
19
19
20
20
By increasing the buffer size, Fluent Bit will make fewer system calls (read(2)) to read the data, reducing CPU usage and improving performance.
21
21
22
-
## Fluent Bit and SIMD for JSON Encoding
22
+
## Fluent Bit and SIMD for JSON encoding
23
23
24
-
Starting in Fluent Bit v3.2, performance improvements have been introduced for JSON encoding. Plugins that convert logs from Fluent Bit's internal binary representation to JSON can now do so up to 30% faster using SIMD (Single Instruction, Multiple Data) optimizations.
24
+
Starting in Fluent Bit v3.2, performance improvements have been introduced for JSON encoding. Plugins that convert logs from the Fluent Bit internal binary representation
25
+
to JSON can now do so up to 30% faster using Single Instruction, Multiple Data (SIMD) optimizations.
25
26
26
-
### Enabling SIMD Support
27
+
### Enabling SIMD support
27
28
28
29
Ensure that your Fluent Bit binary is built with SIMD support. This feature is available for architectures such as x86_64, amd64, aarch64, and arm64. As of now, SIMD is only enabled by default in Fluent Bit container images.
29
30
30
31
You can check if SIMD is enabled by looking for the following log entry when Fluent Bit starts:
@@ -38,15 +39,15 @@ You can check if SIMD is enabled by looking for the following log entry when Flu
38
39
[2024/11/10 22:25:53] [ info] [sp] stream processor started
39
40
```
40
41
41
-
Look for the simd entry, which will indicate the SIMD support type, such as SSE2, NEON, or none.
42
+
Look for the `simd` entry, which will indicate the SIMD support type, such as `SSE2`, `NEON`, or `none`.
42
43
43
-
If your Fluent Bit binary was not built with SIMD enabled and you are using a supported platform, you can build Fluent Bit from source using the CMake option `-DFLB_SIMD=On`.
44
+
If your Fluent Bit binary wasn't built with SIMD enabled and you are using a supported platform, you can build Fluent Bit from source using the CMake option `-DFLB_SIMD=On`.
44
45
45
46
## Run input plugins in threaded mode
46
47
47
48
By default, most of input plugins runs in the same system thread than the main event loop, however by configuration you can instruct them to run in a separate thread which will allow you to take advantage of other CPU cores in your system.
48
49
49
-
To run an input plugin in threaded mode, just add `threaded: true` as in the example below:
50
+
To run an input plugin in threaded mode, add `threaded: true` as in the following example:
0 commit comments