Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.3
-
None
-
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T08:41:47-08:00)
Maven home: E:\Java\apache-maven-3.3.9\bin\..
Java version: 1.7.0_79, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_79\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T08:41:47-08:00) Maven home: E:\Java\apache-maven-3.3.9\bin\.. Java version: 1.7.0_79, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.7.0_79\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
Description
Over in Apache Log4j-land, we are working on a GC-free logging epic.
We try hard to generate as few objects as possible. Right now, we create one CSVPrinter per logging event to create a CSV line for that event.
In order to get the best memory profile and performance, this ticket proposes to refactor the CSVPrinter and CSVFormat objects to allow a subset of print operations directly from the CSVFormat object.
I tested this patch with the Log4j Git master and it works.
Attachments
Issue Links
- is required by
-
LOG4J2-1385 (GC) CSV layouts should not create a new CSVPrinter for each log event
- Closed