Skip to content

Commit b7e6203

Browse files
authored
Updated performance doc page with v4.1 SMID parsing improvements. Fixes #2079. (#2127)
Updated performance doc page with v4.1 SMID parsing improvements. Fixes #2079. (#2127) Signed-off-by: Eric D. Schabell <[email protected]>
1 parent b7aad6e commit b7e6203

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

administration/performance.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,8 +21,8 @@ By increasing the buffer size, Fluent Bit will make fewer system calls (read(2))
2121
2222
## Fluent Bit and SIMD for JSON encoding
2323
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).
2626

2727
### Enabling SIMD support
2828

@@ -41,11 +41,11 @@ You can check if SIMD is enabled by looking for the following log entry when Flu
4141

4242
Look for the `simd` entry, which will indicate the SIMD support type, such as `SSE2`, `NEON`, or `none`.
4343

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`.
4545

4646
## Run input plugins in threaded mode
4747

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.
4949

5050
To run an input plugin in threaded mode, add `threaded: true` as in the following example:
5151

0 commit comments

Comments
 (0)