perf(logging): Optimize the performance of log collection

[zongmingzhi]

• Adjust the serialization timing of the request body and response body to avoid unnecessary string operations.
• Perform string conversion only after confirming the need to record logs to reduce resource consumption.

Make sure that:

• You have read the contribution guidelines.
• You submit test cases (unit or integration tests) that back your changes.
• Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

[Aias00]

hi, Thanks for your contribution. Have you done any comparisons of time consumption/performance? If you have any relevant comparison results, could you please share them?

[zongmingzhi]

hi, Thanks for your contribution. Have you done any comparisons of time consumption/performance? If you have any relevant comparison results, could you please share them?

you can conduct simulation tests by yourself. Regarding the problems encountered online, when the concurrency is extremely high, performing the writer.output(); method on data that does not need to be stored leads to frequent fullgc collections, and eventually directly results in an out-of-memory (OOM) error. This optimization has been implemented to resolve the online issues.

[Aias00]

hi, Thanks for your contribution. Have you done any comparisons of time consumption/performance? If you have any relevant comparison results, could you please share them?

you can conduct simulation tests by yourself. Regarding the problems encountered online, when the concurrency is extremely high, performing the writer.output(); method on data that does not need to be stored leads to frequent fullgc collections, and eventually directly results in an out-of-memory (OOM) error. This optimization has been implemented to resolve the online issues.

i know what u mean. I just want to say, if there is a comparison, it is better

[zongmingzhi]

hi, Thanks for your contribution. Have you done any comparisons of time consumption/performance? If you have any relevant comparison results, could you please share them?

you can conduct simulation tests by yourself. Regarding the problems encountered online, when the concurrency is extremely high, performing the writer.output(); method on data that does not need to be stored leads to frequent fullgc collections, and eventually directly results in an out-of-memory (OOM) error. This optimization has been implemented to resolve the online issues.

i know what u mean. I just want to say, if there is a comparison, it is better

thank you for your recognition