[GitHub] [logging-log4j2] JoshRosen commented on pull request #329: ThrowableProxy pre-warms its cache using the detected stack

[GitBox <gi...@apache.org>]

JoshRosen commented on PR #329:
URL: https://github.com/apache/logging-log4j2/pull/329#issuecomment-1144474002

   > Looking at this again, I think I should extract the predicate for classes which can't be loaded to a separate change. It should be generally helpful because the cost of a failed class load is very high. While I don't think it solves the problem, it may reduce the magnitude.
   
   +1; I think that fix would be very helpful.
   
   Apache Spark is upgrading to Log4J 2 in its 3.3 release and during testing I spotted performance problems due to unloadable classes in error stacktraces. Because of this performance issue, I am proposing to change Spark
   s default Log4J configuration to specify an explicit `%ex` formatter so we don't use the extended exception information: https://github.com/apache/spark/pull/36747
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org