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
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,8 +21,8 @@ By increasing the buffer size, Fluent Bit will make fewer system calls (read(2))
21
21
22
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 the Fluent Bit internal binary representation
25
-
to JSON can now do so up to 30% faster using Single Instruction, Multiple Data (SIMD) optimizations.
24
+
The release of Fluent Bit v4.1.0 introduced new performance improvements for JSON encoding using Single Instruction, Multiple Data (SIMD). Plugins that convert logs from the Fluent Bit internal binary representation
25
+
to JSON can now do so 2.5 times (read) faster. Powered by the [`yyjson` project](https://github.com/ibireme/yyjson).
26
26
27
27
### Enabling SIMD support
28
28
@@ -41,11 +41,11 @@ You can check if SIMD is enabled by looking for the following log entry when Flu
41
41
42
42
Look for the `simd` entry, which will indicate the SIMD support type, such as `SSE2`, `NEON`, or `none`.
43
43
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
+
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`.
45
45
46
46
## Run input plugins in threaded mode
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
+
By default, most input plugins run 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.
49
49
50
50
To run an input plugin in threaded mode, add `threaded: true` as in the following example:
0 commit comments